How to Write a Cover Letter That Actually Gets Read (3 Templates)

If your cover letter opens with "I am a passionate engineer with X years of experience...", the recruiter has stopped reading. Most cover letters are paragraph-form CVs. Redundant with the resume already attached, generic enough to apply anywhere, and skipped on first scan.

The cover letters that actually get read share three properties: they open with something specific to the company, they prove one concrete result, and they end with a clear ask. This post lays out the framework and gives you three templates you can adapt in five minutes per application.

The three-paragraph template

Paragraph 1. The hook (2 sentences). Open with something specific. A recent product launch, a blog post by an engineer there, a talk by the founder, a public release-note thread. Show in one sentence that you know who they are. Don't say "I came across your job posting". The recruiter already knows where you found it.

Paragraph 2. The proof (3–5 sentences). One concrete result from your past work that maps directly onto the role. Numbers help: "shipped a payments integration that reduced fraud loss by 40% and cut chargebacks by half". Avoid summarising your CV. The recruiter will read it. Pick the single most relevant accomplishment and go deep on it.

Paragraph 3. The close (2 sentences). A one-line "why you" plus a one-line ask. Example: "Happy to walk through any of this on a call. I'm available next week from Tuesday onwards."

That's it. 200–300 words total. Anything longer reduces read-through rate.

Template 1. Senior engineering role

Hi Sarah,

I read Anita's blog post last week on how you cut p99 latency on the payments service from 1.2s to 180ms by moving the rate limiter into Envoy. Particularly liked the section on the canary rollout. The role for a Senior Backend Engineer on the platform team caught my eye because that's the kind of work I'd want to do next.

At [previous company], I led the migration of our checkout API from a Rails monolith to three Go services running behind Envoy. The cutover took 11 weeks, ran a dual-write phase for 3 of them, and shipped without a customer-visible incident; p99 dropped from 850ms to 220ms and the team's on-call alert volume fell by ~60%. I'd be happy to walk through the design tradeoffs on a call.

I'm available next week from Wednesday afternoon onwards. CV attached.

Best,
. Alex

Template 2. Product manager role

Hi James,

Your latest changelog post about cutting the number of pricing plans from 12 to 3 made me grin. I went through the same exercise at [previous company] last year and got a lot of internal pushback before the data won. Saw the Senior PM role on the growth team is open and wanted to throw my hat in.

I owned the activation funnel at [previous company] for two years. The headline result was lifting paid conversion from 4.1% to 7.8% over four quarters by killing two onboarding steps and shipping a "paid trial" variant that only required a credit card after the second meaningful action. The decision tree got smaller, the data got cleaner, and the team got faster. I'd be glad to talk through how I'd approach the equivalent question on your funnel.

Calendar's open Tuesday and Wednesday next week. CV attached.

Best,
. Sam

Template 3. Career switcher (industry change)

Hi Priya,

I've been following your fintech-from-scratch series on the company blog. The post on shipping the first compliance pipeline in three weeks was the one that pushed me to apply. I'm coming from a logistics background but the systems-design problem you're solving (high-volume, regulated, latency-sensitive) is exactly what I worked on for the last four years.

At [previous company] I owned the routing platform that handled 8M shipment events per day across 14 carriers. The most relevant piece is probably the reconciliation system. We ran a continuous double-entry ledger against carrier APIs to catch dropped events within 60s, which cut customer disputes by 70%. Compliance and fintech reconciliation isn't identical, but the pattern is.

I'd love to talk about whether the skills transfer the way I think they do. Available all next week. CV attached.

Best,
. Jordan

What to never include

• "To whom it may concern". Find the hiring manager's name on LinkedIn. The "Posted by" sidebar on the LinkedIn job often shows the recruiter, and "People → Engineering at [company]" usually surfaces the team lead.
• The same opening line as your last 10 letters. Recruiters at popular companies see the same templates over and over. Even one company-specific sentence stands out.
• A summary of your CV. Pick one accomplishment and go deep. The full CV is attached.
• "Please find attached...": corporate filler. Just say "CV attached" or skip it.
• Salary expectations unless explicitly asked. Anchoring early always loses.

The 5-minute tailoring rule

A cover letter takes ~5 minutes to tailor properly: 2 minutes finding a specific hook, 2 minutes picking the right past accomplishment, 1 minute writing the close. That's worth doing for the 20% of applications you actually care about (the ones at companies you'd join). For the other 80%, skip the cover letter or paste a generic one. It won't materially hurt your chances.

The companies most worth tailoring for are usually small-to-medium scale-ups (50–500 employees) where the recruiter is also doing sourcing, people ops, and EA work. They have less time per CV, so a strong cover letter has more relative impact. At big enterprises, recruiters often skip cover letters entirely.

When to skip the cover letter entirely

• If the application form has a "Cover letter (optional)" field and you're applying to 30+ roles a week, skip it for the bulk and do tailored ones for the 5 you'd most want to win.
• If you have a strong referral, the referral does the same job as a cover letter (and better). Skip and let the referral message do the work.
• If the role is on LinkedIn Easy Apply with no cover letter slot, just apply. LinkedIn drops most uploaded cover letters anyway.

The point of a cover letter isn't to add information, it's to compress the recruiter's mental model of you to one paragraph. Done well, a cover letter saves the recruiter time. Done badly, it costs them time. If yours doesn't save time, don't send it.