Cover Letter Examples: Structure You Can Reuse

A cover letter is not a second resume. It explains why this company and this role, in about half a page. MineResume’s cover letter templates keep contact details aligned with your resume.

Four-part structure

• Greeting: hiring manager name if you have it, otherwise “Hiring team”.
• Opening: the role and one sentence of fit.
• Proof: one story or project that matches the posting.
• Close: availability and a clear ask to interview.

Example opening (career switch)

I am applying for the customer success associate role. For two years I supported retail clients on the shop floor; I want to bring that same follow-through to a product that already has written playbooks and a ticketing tool.

Example opening (new graduate)

I am a 2026 B.Com graduate applying for the junior accountant posting. My internship closed month-end entries in Tally and reconciled two vendor ledgers — work I can continue on day one.

Avoid

• Repeating every bullet from the resume.
• Generic praise (“your esteemed organization”) with no product or team mentioned.
• Letters longer than one page.

Write it after the resume, not before

The letter is easier once the resume already has one good story. Steal that story and add why this company. Do not open with your name and the phrase “I am writing to apply.” They know. Open with the role and a concrete match.

Example, operations: “I am applying for the logistics coordinator role. At my last job I scheduled 40 vendor pickups a week in a shared sheet and called the two carriers who missed slots. I want to do that work inside a team that already uses a TMS instead of a spreadsheet.” That is specific enough to survive a skim.

When you can skip the letter

If the portal says letter optional and you have nothing extra to say, skip it rather than pasting ChatGPT praise. If they require a letter, keep it under 350 words. Match the same header details as the resume so the two files look like a set. MineResume’s cover letter templates exist for that pairing.

The three-part body, built line by line

A letter body has exactly three jobs, and they're not the three paragraphs school taught you. Paragraph one is the hook: the role, and the single most relevant true sentence about you — not 'I am writing to apply,' which is a fax-machine habit. Paragraph two is the bridge: one story from your resume retold with the company's problem in it, usually three or four sentences with a number somewhere. Paragraph three is the door: what happens next, stated without begging — 'happy to walk through how the refund-tag audit worked in practice' beats 'I would be honored to be considered' every time. Three paragraphs, no fourth. If you find yourself writing a paragraph about your childhood interest in the industry, that's the hook paragraph failing, not a missing section.

Here's the bridge paragraph, fully assembled, for a support person applying to a logistics coordinator role: 'At ABC Distributors I ran the returns queue for eleven retailer accounts — roughly 30 cases a week between pickup scheduling and credit notes. Half our delays were carrier-side, so I started a Friday call log naming the two carriers who missed slots; our ops manager used it to renegotiate the pickup window. I know your posting says TMS experience; I did the same job in a shared sheet, and I want to do it inside a system that has one.' Read it again and count what it proves: volume, initiative, an artifact someone used, and an honest answer to the requirement you lack. That's the entire formula — the story, the number, the gap handled without apology.

Research that takes ten minutes, not ten hours

'Why this company' fails when it's flattery ('your innovative solutions resonated with me') and works when it's a specific you noticed. Ten minutes is enough: read the about page, one recent news item or product update, and the LinkedIn posts from the team's actual people if you can find them. Then write one sentence of observation, not praise — 'I saw you opened the Pune fulfillment center in March; that's exactly the kind of new-network phase where coordinator work gets messy' — and move on. One true observed sentence beats a paragraph of compliments because it proves you looked, and looking is the thing flattery can't fake. If after ten minutes you genuinely can't find anything specific? Use the role itself — 'the job description says this team is replacing spreadsheets with a TMS, and I've lived that migration once' is company-specific enough through the req alone.

Three variations that trip people up

• Referral: the name goes in the first sentence, not buried at the bottom — 'Priya from your ops team suggested I apply' changes who reads the rest of the letter, and skips a queue.
• Career change: one plain clause on the switch, then straight to proof-of-work in the new field — the letter explains motivation in two sentences the resume has no room for, and that's its superpower for switchers.
• Fresher: write about the specific team's problem you studied for, not your coursework — 'your support docs mention the onboarding flow; I rebuilt a campus version and logged where students got stuck' is a fresher letter that gets answered.

Formatting, delivery, and the closing line

Same header as the resume, same font, one page obviously. If an email application, the letter body goes in the email itself, not attached twice — recruiters forward text, not files — with the resume attached and named properly. The sign-off is 'Regards, Name,' full stop; no 'thank you for your valuable time,' which is the last gasp of the template era. Then the honest check before sending: would you recognize yourself in this letter from a year ago? If any sentence could be pasted into anyone's application to any company, delete it and take the word count down. A 180-word letter where every sentence belongs only to you beats 400 words of anyone-could-have-written-this.

Three complete letters you can steal the shape from

Shapes beat advice, so here are three full skeletons with the anatomy labeled. The fresher letter (support role): hook — 'I'm applying for the junior support position; during my BSc I ran the computer-lab help desk for 60 students a week, logging recurring printer and login issues in a shared sheet'; bridge — one story with a number and the gap named honestly ('your posting wants Zendesk; I worked in a ticket queue during my internship at [clinic] and learned the discipline of updating the ticket even when the fix was someone else's job'); door — 'I'd be glad to walk through the help-desk log with you.' The career-change letter (teacher to edtech content designer): hook names the switch in one clause and immediately points at proof — 'six years of designing CBSE history units from scratch is curriculum design by another name'; bridge is the artifact letter — 'I built the department's assessment rubric that replaced essay-marking disputes; here's how it worked'; door offers the portfolio. The referral letter: first sentence is the name, second is the overlap, and the whole thing is 120 words because Priya from ops already told them you're worth reading — the letter's only job is to not be weird. Each of these is under 300 words. Every version of this that runs longer than a screen is a version where the writer stopped trusting one story to carry, and added three more and a paragraph about the company's values. The letter is one story well told; anything else on the page is you nervously clearing your throat in writing.

The email version, because the letter is usually the email now

When a human receives your application by email — referral, direct to a manager, a recruiter who asked for your file — the letter and the email are the same object, and email physics apply. The subject line carries the whole open rate: 'Data analyst application — 3 yrs SQL + retail reporting — Nikita Rao' gets opened; 'Resume' gets delayed into the pile; a bare forwarded 'FW:' chain gets lost. The body is the letter with the salutation stripped — greeting, hook, bridge, door, name and phone under a plain signature, no image logo, no quote from a poem. Attachment named per the file-name rule, and say it's attached in one clause because a surprising number of emails claim a file that isn't there. Paste a plain-text copy below the signature only when the recipient is famous enough to read on a plane — otherwise it doubles the length for no benefit. Then the timing truth: an email sent Sunday evening reads as an inbox zero problem; sent Tuesday to Thursday morning it reads as correspondence. And the follow-up on the same thread, one line, after ten working days is allowed once and ages badly twice — the difference between persistent and pestering is arithmetic, not attitude. What email physics never forgive: a wrong name. If you're writing to a person, check their name on the company page or LinkedIn headline — 'Dear Sir/Madam' addressed to someone whose signature said 'Ananya' for forty emails is a one-way ticket to the archive.