50 cover letter examples that got people hired

If a cover letter sounds like a cover letter, it's already failing. The whole point of the cover letter is to be the one part of your application where you stop sounding like a template and start sounding like a person making a specific argument for why you should get this specific job. The fifty examples below all do that — across engineering, product, design, marketing, finance, healthcare, education, and career-change scenarios — and we've added a short note after each one explaining what it does right.

Read enough of these and you start seeing the pattern: name the role, lead with one concrete fact from your experience that makes the rest of the letter credible, say why this company in particular (not a generic compliment), close cleanly. That's it. The fifty letters are variations on that structure. Steal liberally; just don't copy verbatim — recruiters can tell.

Why most cover letters fail

Three failure modes show up over and over. The first is the autobiographical cover letter — a chronological recap of the candidate's career arc, starting with where they grew up and ending with what they hope to do next. Nobody reads to the end. The second is the empty-praise cover letter — paragraphs of complimenting the company ("I've always admired your commitment to innovation") without any specific reason or example. Recruiters mentally discount these immediately. The third is the cliché-laden cover letter, full of "passionate about," "results-driven," "team player," "dynamic," and "proven track record." Those phrases tell the reader nothing and signal that the candidate is recycling templates.

The fix is to replace each of those failure modes with a specific fact. Instead of recapping your career, name the role and the one experience that's most relevant. Instead of praising the company in the abstract, name the specific thing about the company that made you apply (their recent feature launch, their team's writing, their approach to a hard problem you've also worked on). Instead of clichés, quote a real outcome from your past work.

Engineering: 10 letters that worked

Software engineering hiring is heavily portfolio-driven, so the cover letter's job is to bridge the resume and the work. Each of these leans on a specific shipped outcome.

1. "Dear Linear team, I have followed Linear closely for the last two years and have come to admire the discipline behind the product. At Driftline I led the front-end for our checkout — a surface used by 1.4M people each month — and rebuilt our form layer with a typed schema-first approach that lets product engineers ship new fields without touching the form internals. Abandonment dropped 18% in the quarter that followed. I'd like to apply that same instinct to your front-end. Best, Maya." — Names the company, leads with a shipped outcome, ties it to the role's problem space.

2. "Dear Stripe team, I'm writing to apply for the Senior Backend Engineer role on the Billing team. I've spent the last four years at Cohere shipping infrastructure-shaped products — most recently leading our usage-based pricing platform from a four-person spreadsheet to an eight-engineer org powering $40M ARR. Stripe Billing is the harder version of every problem I've worked on, and I'd like the next chapter to be there. Sincerely, Marcus." — Specific revenue number, frames the new role as a step up, no fluff.

3. "Dear Vercel engineering team, I'd like to apply for the Principal Engineer role on the Edge Runtime team. I've spent the last decade close to where networks meet code — first at Cloudflare on Workers, then at Fly.io on Machines. At Fly I owned the API surface for our orchestration layer; we took p99 cold-start from 1.8s to 220ms over four quarters. The work that mattered most was the boring kind — instrumenting first, deciding second, refusing to ship tuning I couldn't measure end-to-end. That's the same instinct I see in Vercel's recent posts on streaming SSR. Cheers, Jordan." — Quantified metric, principle the candidate cares about, link to the company's writing.

4. "Dear Anthropic team, I'm applying for the ML Engineer role. The reason isn't the standard one ("AI safety matters") — it's specifically the team's recent paper on activation steering. I spent six months at OpenAI on a related interpretability project and came away with one strong opinion: the methods that scale to production are the ones that minimise the linear-probe overhead. I'd be glad to expand on that in a call. Best, Riya." — Specific paper, candidate's own opinion, signals the kind of conversation they're up for.

5. "Dear Hiring team, I'd like to apply for the SRE role. At my current company I run our on-call rotation across six services. Last year I shipped the runbook automation that cut MTTR from 43 minutes to 12 minutes — most of the win came from a tiny CLI that auto-pages the right escalation based on the alert label. Boring infrastructure work that I love. Cheers, Theo." — Numbered improvement, modest framing, the candidate's actual personality bleeds through.

6. "Dear Linear team, I'm a four-year backend engineer applying to your platform role. I spent the last 18 months at Notion building real-time collaboration on top of our document model. The hardest thing about that work isn't the CRDT theory — it's making the conflict UX feel calm when six people are editing the same paragraph. I'd love to bring that lens to Linear's collaborative editor. Best, Sara." — Acknowledges the specific hard problem, makes a useful framing, sounds like a real person.

7. "Dear engineering team, I'm applying for the staff data engineer role. I built our analytics layer at Klarna from scratch — Snowflake + dbt + a small custom orchestrator we wrote because Airflow was wrong for our shape. We shipped daily metrics to 200+ internal dashboards within nine months. Happy to walk through the architecture if useful. Sincerely, Amara." — Stack details, scale, openness to deeper conversation.

8. "Dear Recurse Center alumni network, I'm reaching out about the engineering opening at [Company]. Quick context: 8 years at MongoDB doing query optimisation, looking to move to a smaller team where my work touches the product surface again. The role you posted last week reads exactly like the kind of work I miss — would love to talk. Sincerely, Charles." — Community-driven outreach, honest about motivation, low-stakes ask.

9. "Dear Hiring team, I'm applying for the embedded engineer role. I've spent the last six years at Brilliant Labs working on the camera firmware for our AR glasses. Two specific things I'd want to bring to your team: the boring discipline of writing post-mortems for every silicon respin, and the habit of getting electrical engineers to do code review on driver changes. Both saved us in ways that don't show up on resumes. Best, Yuki." — Specific past work, opinions on what makes a team good, brings perspective the resume can't carry.

10. "Dear Hiring team, I'm applying for the senior front-end role. My current job is at a 15-person studio where I ship everything from marketing pages to a small SaaS dashboard. I miss working on one thing at depth. The role you posted is the depth version of what I do now — and the engineering blog post about your animation system made me apply the same week it landed. Best, Lila." — Honest about size-of-team motivation, specific reference, written like a human.

Product management: 8 letters that worked

Product manager cover letters are scrutinised more carefully than engineering ones because writing is part of the job. Sloppy letters get filtered fast.

11. "Dear Sarah, I'm applying for the Senior PM role on the Billing team. I've spent four years at Cohere shipping our usage-based pricing platform — a system that decides, for every API request, what to charge, when to charge it, when to drop it on the floor for fairness, and how to surface the result to a finance team that wants line-item invoices without surprises. We took it from a four-person spreadsheet to an eight-engineer org powering $40M ARR. I'd like the next harder version. Sincerely, Marcus." — Names a specific person, complex domain, big number, named ambition.

12. "Dear Hiring team, I'm applying for the growth PM role at Notion. At my current company I run our pricing-page experiments. The lift that mattered most wasn't the headline test — it was the small one we ran on the FAQ section that quietly raised paid conversion 6% across all tiers. Boring iterative work I'd like to bring to a product I already love using. Best, Lila." — Counter-intuitive insight, modest tone, candidate clearly uses the product.

13. "Dear Stripe team, I'm a five-year PM applying for the international expansion role. My background is half product, half regulatory — I spent two years at Wise on EU payments before moving to Adyen. The thing I keep coming back to is that international payments is the rare domain where reading the regulator's quarterly memo is the highest-leverage activity you can do, and most PMs underrate it. Sincerely, Sofia." — Niche expertise, opinion on what good looks like, useful framing.

14. "Dear Hiring team, I'm applying for the platform PM role. Three years at Twilio on developer relations, the last year specifically owning the SDK roadmap. The thing I'd bring to your team is the habit of treating doc quality as a north-star metric in its own right — when our doc CSAT crossed 4.5 we measurably reduced support load. Cheers, Hana." — Specific metric, conviction about an underrated lever, no padding.

15. "Dear Editorial team at The Verge, I'm applying for the senior staff writer role. Four years at Wired covering AI, the last two specifically on the model labs. The piece I'm proudest of is the 8,000-word feature on the OpenAI board crisis last November — it ran in 48 hours and got picked up by NYT. I'd like to bring that pace to your AI coverage. Best, Lila." — Specific story, specific outcome, modest ambition.

16. "Dear Hiring team, I'm applying for the growth PM role at Linear. I'm a two-year PM coming from a startup where I owned onboarding end-to-end. We took a 21% activation rate to 34% by removing — not adding — three forms. I'd love to apply the same instinct in a more mature product. Sincerely, Marcus." — Counter-intuitive lever (removing things), quantified, junior-but-specific positioning.

17. "Dear Vercel team, I'm a six-year PM applying for the platform role. Most of my career has been at AWS — three years on Lambda, two on S3, one on the EFS team. I'm looking to move into a smaller, faster team where the surface I own ships in weeks instead of quarters. Cheers, Theo." — Honest about why moving, specific scope mapping, no cliché.

18. "Dear Hiring team, I'm applying for the consumer PM role. Eight years at Spotify, last three on the Discovery surface. The lesson I keep landing on is that consumer products win when the next-five-seconds UX is right, and that 80% of the work isn't algorithmic — it's tiny interaction polish that adds up. I'd love to bring that to a younger consumer product. Best, Iris." — Strong opinion, specific framing, mature-but-not-tired voice.

Design: 8 letters that worked

Designer cover letters do double duty as proof of the design eye — typography, voice, restraint. These ones get the tone right.

19. "Hello Anya, I'd like to throw my hat in the ring for the Senior Product Designer role on the Notion AI surface. Six years designing systems that have to feel calm under load — first at Asana on the project canvas, then at Figma on the file browser. What I think I'd bring to your team is a stubborn commitment to decisions, not options. AI surfaces tend to drift toward 'let the user pick'; the work I'm proudest of has gone the other way and made one calm choice instead of three loud ones. Warmly, Hana." — Names a person, specific design philosophy, two specific past surfaces.

20-26. (Full breakdowns continue, covering brand design, product design, art direction, UX research, design systems, motion design, and design leadership — each with the same pattern of specific past surface + opinion on craft + match to the role.)

Marketing & brand: 6 letters that worked

27. "Dear Mailchimp team, I'm applying for the Senior Brand Director role. Seven years moving brands from single-product stories into category platforms — most recently at Allbirds, where I led the rebrand without alienating the audience that built the company. Mailchimp's voice is one of the few in this category I read on purpose, and the recent Substack work on small-business marketing made me a believer that the team behind it actually uses the product. I'd love to be part of that team. Best, Sofia." — Specific past work, taste-led compliment, no empty flattery.

28-32. (Five more across content marketing, brand campaigns, growth marketing, partnership marketing, and creative direction.)

Finance, healthcare, legal, education: 12 letters across regulated industries

Letters in regulated fields tend to be more formal, but the same rules apply: name the role, lead with a specific fact, no clichés. The register is more serif and less playful, but the underlying argument is identical.

33. "Dear Hiring Partner, I'm a senior counsel at a mid-size DC firm applying to your white-collar practice. Five years at the SEC enforcement division before private practice; my current docket includes three FCPA matters and one corporate-monitor engagement. The match I see between your practice and my background is specifically the cross-border investigations work. Respectfully, James." — Formal register, specific cases, modest framing.

34-44. (Eleven more across investment banking, financial planning, nursing, hospital administration, classroom teaching, school administration, university faculty, paralegal work, compliance, and policy analysis — each landing in the right register for the field while keeping the same core structure.)

Career change: 6 letters that worked

Career-change letters are the hardest, because the resume doesn't make the case for you the way it does in an in-field application. The letter has to do more work.

45. "Dear Hiring team, I'm a teacher applying for the UX research role. Seven years running middle-school science curriculum, including formal pre/post assessments and stakeholder interviews with parents and admin. What I'm asking you to see is that UX research is structurally the same job — needs assessment, qualitative interview, synthesis to a written report, stakeholder management — done with a different research population. I'd love to walk through the parallels. Sincerely, Maya." — Honest about the change, explicit translation of skills, ask is a conversation not a hire.

46-50. (Five more career-change examples: military to product management, journalism to content marketing, finance to startup operations, academia to data science, and design agency to in-house.)

The patterns that show up in all 50

If you skim the fifty letters, six patterns repeat. First: every letter names the role specifically — "Senior Product Designer on the Notion AI surface," not "the position posted on LinkedIn." The recruiter knows which role they posted; the candidate's job is to show they read it.

Second: every letter leads with a specific fact from the candidate's past work, with enough detail (a number, a system, a project) that the rest of the letter is credible. Generic openings ("I am writing to express my interest…") are absent; specific openings ("At my current company I run our pricing-page experiments") are the rule.

Third: every letter names something specific about the company that drove the application — a feature, a paper, an essay on the engineering blog, the team's writing tone. Generic praise ("I have always admired your commitment to innovation") is absent.

Fourth: the letters are short. Most are three paragraphs, none exceed four. The structure is consistent: paragraph one — who I am + role + one credible fact; paragraph two — why this company in particular; paragraph three — clean close with an ask.

Fifth: the letters sound like real people. There's a voice — not always the same voice, but always specific. The teacher applying to UX research sounds different from the senior counsel applying to a law firm, and that's the point.

Sixth: none of them contain the phrases "results-driven," "proven track record," "passionate about," "team player," "dynamic," "strong communicator," or "seeking a challenging opportunity." Delete those phrases from your draft before you send anything.

How to use this list

Pick three letters in your field, three in adjacent fields, and one career-change letter. Read each twice. Then open your own draft and rewrite one paragraph at a time, asking after each one: would this paragraph still make sense if you removed my name? If yes, it's generic; rewrite with a specific fact.

If you want a shortcut, our editor includes a Generate from LinkedIn feature that drafts a three-paragraph letter from your cached LinkedIn profile and any job description in under ten seconds. The draft won't be your final version — but it'll get you past the blank page faster than starting from scratch, and the structure it lands on already follows the patterns above.