The problem with most cover letter examples online is that they're written for nobody in particular, which teaches you to write letters for nobody in particular. Every example on this page is built around a specific, invented applicant in a specific situation — a named person, a named company, a real constraint — with annotations explaining why each paragraph earns its place. Copy the moves, not the sentences. All applicants and companies here are fictional; the situations are the twelve we see most often.
If you want the underlying theory first, our pillar guide on how to write a cover letter explains the hook-proof-fit-close structure these examples all share. This page is the structure in action.
How to adapt an example without producing a template clone
Before the examples, three rules for using them:
- Steal the skeleton, not the skin. The reusable part of any example is its sequence of moves — what each paragraph is doing. The sentences themselves must be rebuilt from your own facts.
- Run the swap test. After adapting, replace the company name with a competitor's. Every sentence that survives unchanged is a sentence a recruiter has read hundreds of times.
- Keep the ratio. Notice that every strong example below spends more words on proof than on enthusiasm. When people adapt examples, they tend to keep the enthusiasm and trim the proof. Do the opposite.
If you'd rather work from guided prompts than finished letters, our prompt-based cover letter template is built for exactly that.
Standard application letter, annotated
Situation: experienced payroll specialist applying to a posted role at a mid-size company. No referral, no complications — the baseline case.
Dear Mr. Aldana,
I've run payroll for workforces of 300 to 1,100 employees across three states, and the thing I'm proudest of is boring: four consecutive years without a single missed or incorrect pay run. I'm applying for the Senior Payroll Specialist role at Hartwell Manufacturing because your posting reads like it was written by someone who knows exactly how hard boring is to achieve.
At Corvex Staffing, I inherited a payroll process that generated 30–40 employee tickets per cycle. I rebuilt the pre-processing checklist, moved timesheet validation earlier in the week, and created a one-page exception report my manager could act on before — not after — payday. Tickets dropped below five per cycle within four months, and the checklist became standard across two sister offices.
Your posting emphasizes the upcoming transition to Workday. I've been an end user through one full payroll system migration and served as the payroll team's testing lead for parallel runs, so I know where migrations actually break: not in the software, but in the edge cases nobody documented. I keep a running list of ours from last time.
I'd be glad to talk through how Hartwell is planning the transition. Thank you for your consideration.
Sincerely, Renata Voss
Why it works, line by line: The hook makes a virtue of unglamorous work — "proudest of is boring" — which is both memorable and precisely calibrated to payroll, where reliability is the product. The proof paragraph has a baseline (30–40 tickets), actions, and an endpoint (under five). The fit paragraph responds to a specific detail in the posting and closes with a concrete, slightly unusual credential ("I keep a running list"). Nothing in this letter could be sent to another company unedited.
Career change and no-experience letters, annotated
Career change: restaurant general manager moving into HR coordination.
Dear Hiring Team,
For six years I ran a 45-person restaurant, which means for six years I did HR without the title: hiring about 30 people a year, handling scheduling conflicts, coaching first-time supervisors, and navigating two workers' comp claims. I'm now moving that work to the center of my career, and the HR Coordinator role at Lumen Health is where I'd like to do it.
The example I'd offer: our turnover was the worst in our franchise group when I took over. I rebuilt onboarding from a two-hour shadow shift into a structured first week with written checkpoints, and started conducting exit conversations personally. Within a year, we had the best retention of the group's nine locations. I didn't have HR software or an HR budget — I had the problems, and I solved them with process.
I'm aware I'm asking you to bet on translated experience. To shorten the odds, I completed my aPHR certification in March and have been volunteering with a local nonprofit's hiring committee since January. What I bring that a traditional candidate may not: I've personally lived every consequence of bad hiring, thin onboarding, and unclear policy.
I'd welcome a conversation. Thank you for your time.
Kind regards, Marcus Ellery
The key move: the second-to-last paragraph names the objection ("translated experience") before the reader can, then answers it with two concrete mitigations. Career-change letters that pretend the pivot is invisible read as naive; letters that address it head-on read as self-aware. Pair this letter with a resume built the same way — our career change resume guide shows the matching document.
For applicants with no work history at all, the structure shifts from "translating experience" to "substituting evidence" — coursework, projects, and volunteering carry the proof paragraph. We've dedicated a full guide with two annotated letters to writing a cover letter with no experience.
Referral and internal-promotion letters, annotated
Referral letter — the opening is the whole trick:
Dear Ms. Ibarra,
Tomás Reyes on your platform team suggested I apply for this role — we worked together for three years at Northgate, where I was the analyst he called when the numbers didn't add up. He thought your team's work on churn modeling would fit how I like to work: deep in the data, close to the decision.
Annotation: The referrer's name is in the first five words, because a recognized name buys more attention than any crafted sentence. But note the follow-through — the letter immediately establishes what the referrer knows about the applicant's work, which converts the referral from name-dropping into evidence. The remaining paragraphs proceed as a standard letter; a referral changes the opening, not the burden of proof.
Internal promotion letter — different problem entirely:
Dear Selection Committee,
In two years as a support engineer at Vanterra, I've closed about 2,900 tickets — and filed 41 product bug reports, 11 of which shipped as fixes. That second number is why I'm applying for the Associate Product Manager opening: I've been doing the listening half of product management from the support queue, and I'd like to do the whole job.
You have my performance reviews, so I'll add what they don't capture. Last fall I noticed a pattern across dozens of tickets — customers misreading the billing page in the same way — and wrote a one-page proposal for a redesign. Product adopted it in Q1, and tickets on that page dropped by roughly half. Nobody asked me to do this. That's the kind of PM I'd be.
I know internal candidates can seem like the easy choice; I'd rather be the right one. I've asked my manager, Dee Okonkwo, to speak to my readiness, and she's glad to.
Respectfully, Ahn Tran
Annotation: Internal letters can't rely on introduction — the reader may already know you — so this one reframes known facts ("you have my performance reviews, so I'll add what they don't capture"). The unprompted-initiative story is the strongest possible evidence for a support-to-product move, and pre-arranging the manager's endorsement removes the reader's main logistical worry.
Cold outreach and speculative letters, annotated
When there's no posting, the letter must do an extra job: define the role it's proposing.
Dear Mr. Castellanos,
Marrow Bakery has grown from one location to four in under three years, and based on your hiring pages, everyone you employ makes or sells bread. This letter is a bet that the operational load — vendors, scheduling, permits, payroll — is landing on you, and that it's starting to hurt.
I spent five years as operations manager for a three-location coffee roaster in a similar growth phase. I took over vendor management (cutting ingredient costs 12% through consolidated ordering), built the scheduling system that ended weekly staffing fires, and handled the permitting for both new locations. The owners went back to roasting. That's the outcome I sell.
If I'm wrong about the pain point, this letter costs you thirty seconds. If I'm right, I'd love fifteen minutes to show you what the first ninety days could look like.
Best regards, Simone Adjei
Annotation: The letter names a plausible pain, offers directly relevant proof, and — critically — makes the ask tiny ("fifteen minutes"). Speculative letters fail when they ask the reader to invent a job; this one arrives with the job already sketched. Send letters like this sparingly and only where your research supports the bet.
Short-form letters for application form text boxes
Many applications now offer a 100–200 word "why do you want to work here?" box instead of a letter upload. Compress to hook and proof; cut the close entirely:
I've spent four years doing B2B customer success in logistics — most recently keeping a 94% renewal rate across 60 mid-market accounts at Freightline. Kestrel's posting stood out because it emphasizes owning renewals end to end, which is exactly the scope I have now and want to keep. The work I'm best at: turning at-risk accounts around (12 saves last year, tracked) and building QBR processes that customers actually attend. I'd bring both on day one.
That's 78 words carrying a metric, a specific reason, and two concrete capabilities. In a text box, every sentence must be load-bearing.
The anatomy all twelve share
Across every situation on this page, the same skeleton repeats: a hook that pairs a credential with a specific reason for this company, one proof story with a baseline and an outcome, a fit paragraph that responds to something real, and a short close. What changes is emphasis — referrals frontload the name, career changers frontload the translation, internal candidates frontload the reframe, cold letters frontload the pain point. Diagnose your situation, pick the matching emphasis, and build on the skeleton with your own facts.
Frequently asked questions
Can I just copy one of these examples and change the names?
You can, but it will underperform, and not because anyone will trace it to this page. The details that make these letters work — ticket counts, retention numbers, the billing-page story — are what persuade, and those can't be copied because they aren't yours. An adapted skeleton with your real evidence beats a polished letter built on someone else's.
Which example should I use if my situation is mixed — say, a career change with a referral?
Stack the moves in priority order: referral first (the name in sentence one), then the career-change translation in the proof and fit paragraphs. When moves conflict for space, the referral opening wins because it's the highest-value single sentence available to any applicant.
Do these letters work for email applications?
Yes, with light reformatting: the letter body becomes the email body, you drop the postal header block, and the subject line does part of the hook's work ("Referred by Tomás Reyes — Senior Analyst application"). Keep it just as short.
How different should my letter be for each application?
The hook and fit paragraphs should be genuinely specific to each company. Your proof story can repeat across applications with minor tuning — a good story is an asset, not a liability. Budget about twenty minutes per letter once your core stories are written.
Turn the example into your application
Once your letter makes its argument, your resume has to back it up under a skimming read. Paste yours into Workplacea's free resume checker to see how it parses and whether the achievements your letter references actually stand out on the page — the letter and resume should read like two halves of one case.