Somewhere between "nobody reads cover letters anymore" and "always write one" is the truth: cover letters get read in some situations and ignored in others, and you can usually tell which situation you're in before you apply. Once you know that — and stop treating the letter as a formal essay instead of a short, specific pitch — you can write a good one in about ten minutes.
Here's when a cover letter actually matters in 2026, a structure that takes minutes instead of an evening, a complete worked example, and how to use AI without sounding templated.
When cover letters get read — and when they don't
Whether your letter gets read depends mostly on who is screening and how many applications they're facing. A few patterns hold up consistently:
Letters tend to get read when…
- The company is small. At a 15-person startup or a local firm, the hiring manager is often the first reader — fewer applications, more skin in the game, and a genuine question ("why us?") that a resume can't answer.
- You're changing careers or have an unusual path. If your resume raises a question — a gap, a pivot from teaching to sales, a relocation — the letter is your only chance to answer it before someone draws their own conclusion.
- You have a referral or named contact. When someone passes your application along, the letter is what gets forwarded — and skimmed to judge whether the referral was a favour or a real endorsement.
- The posting asks a specific question or says the letter is required. Some teams use it deliberately as a filter for effort and writing ability.
Letters tend to get skipped when…
- The role gets hundreds of applicants. A recruiter triaging a high-volume req filters resumes by keywords and titles first — the letter rarely enters the picture. (That's a resume problem; see our guide to resume keywords.)
- The application flow buries it. If the letter is an optional upload on screen four of an ATS form, it may never surface in the recruiter's view at all.
- You're a textbook fit. When the resume already answers every question the role asks, the letter adds little — and a generic one can only subtract.
Why "optional" sometimes isn't
Plenty of postings mark the cover letter optional. Read that carefully: optional means not required to submit, not not considered if submitted. For high-volume roles it's genuinely skippable. But for smaller companies, career changers, and anyone whose resume needs context, "optional" is quietly a free move — most applicants won't bother, so a sharp, specific letter is one of the few places you can differentiate without inflating anything. If you're in one of the "gets read" situations above and the field exists, fill it.
Write the letter when a human is likely to read it early (small company, referral, career change, "required") or when your resume needs context. Skip it — or send a short three-line version — when you're one of hundreds applying to a high-volume req through an ATS portal. Spend the saved time tailoring your resume instead.
The 10-minute structure
A cover letter that works is not an essay about you. It's a short argument that you understand the company's problem and have already solved something like it. Three parts, well under one page:
1. Open with a hook tied to their actual problem (2 minutes)
Skip "I am writing to apply for…" — they know. Every job posting is a problem statement in disguise: a support team drowning in tickets, a product expanding into a new market, a finance function that's outgrown spreadsheets. Name that problem in your own words and connect yourself to it in one or two sentences.
2. One or two proof paragraphs mapped to the job description (5 minutes)
Pick the two requirements from the posting that matter most — usually the ones listed first, repeated, or bolded — and give one concrete, past-tense example for each. Situation, what you did, what changed. Numbers if you have them; specifics either way. Don't summarize your whole career: the letter's job is to make them open the resume wanting to confirm what they just read.
3. Close with intent (3 minutes)
Say plainly that you want this role at this company and why — one honest reason, not flattery. Then make the next step easy: you're available to talk, here's how to reach you. One direct sentence beats "I look forward to hearing from you at your earliest convenience."
A complete worked example
Here's the structure applied to a realistic posting: a Customer Success Manager role at "Driftline," a fictional 40-person SaaS company whose posting emphasizes reducing self-serve churn and building onboarding from scratch.
Dear Maya,
Driftline's posting says the quiet part out loud: self-serve customers sign up easily and leave just as easily, and nobody owns the space in between. That's the exact gap I spent the last two years closing at a similar-stage SaaS company, and it's why this role caught my attention.
At Northbeam Software, I inherited a self-serve segment with no onboarding beyond a welcome email. I built a 14-day onboarding sequence — in-app checklists, a usage-triggered check-in call, and a "first value" milestone we tracked per account — and 90-day retention in that segment improved by roughly a third over two quarters. I didn't have an enablement team; I wrote the emails, recorded the walkthroughs, and revised them based on where customers actually got stuck.
The posting also asks for someone comfortable being the voice of the customer internally. Every month I turned churn interviews into a one-page brief for product and engineering; two of those briefs became shipped features, including an export tool that closed our most common cancellation reason.
I want to do this again at Driftline specifically because you're at the stage where these systems get built rather than inherited — that's the work I'm best at. I'd welcome a conversation; I'm reachable at the email and number above any weekday.
Best regards,
Sam Okafor
Notice what it doesn't do: it doesn't restate the resume, it doesn't praise the company's "innovative culture," and it fits on half a page. Each paragraph maps to something the posting explicitly asked for.
What gets letters skipped (or held against you)
- Restating the resume. If every sentence is a bullet point rewritten in prose, the reader learns nothing and stops. The letter should add context the resume can't carry.
- "I am writing to apply for the position of…" Opening with the obvious signals a template — and templates get skimmed at best.
- Generic flattery. "Your innovative, fast-paced company" could describe anyone. If you can't name something specific — a product, a market move, the problem in the posting — say less about them and more about the work.
- Length. Anything over one page is a request for the reader's time you haven't earned yet. Three to four short paragraphs is the ceiling; half a page is often better.
- The wrong company name. It happens more than you'd think with copy-paste letters, and it's an instant pass at most companies.
Using AI without sounding templated
AI-drafted cover letters are everywhere now, and hiring managers have developed an ear for them: confident-but-empty openings, "excited to leverage my skills" phrasing, suspiciously smooth paragraphs with no concrete detail. The problem isn't using AI — it's submitting the first draft.
Two rules keep an AI-assisted letter sounding like you:
- Always do an editing pass. Read the draft aloud and cut every sentence you wouldn't say in a conversation. Rewrite the opening in your own words — it's the line most likely to sound machine-made and the most likely to be read.
- Add specifics only you know. An AI working from a generic prompt can't know that your onboarding sequence was triggered by usage data, or that your churn brief became a shipped feature. Those details are your fingerprint; a letter without them is interchangeable with a thousand others. Use AI for structure and speed — feed it your real experience and the actual posting, then make the result unmistakably yours.
A good letter pairs well with a good follow-up. If you haven't heard back in a week or so, here's how to write a follow-up email after an application that nudges without nagging.