Start with the question everyone actually has: does anyone read these? Honest answer, sometimes. Plenty of applications are decided on the resume alone, and plenty of recruiters skip straight past the letter. But the cases where it is read are not random, and they are the cases that matter most to you: small companies, hiring managers reading directly, anyone whose resume raises a question, and every career change.
So the useful framing is not whether to write one. It is that a cover letter is cheap insurance against exactly the situations where your resume alone will not carry you, and it is worthless when it repeats the resume in prose. This guide is about the difference.
The one job a cover letter can do
A resume is a structured record. It is very good at what, when and how much, and it is structurally incapable of explaining why. Why you are leaving a field you spent six years in. Why a company should care that you have done this specific thing before. Why the gap. Why this job, out of the hundreds you could have applied to.
Every good cover letter answers a why question. Every bad one answers a what question the resume already answered better, in a less scannable format.
That gives you a test before you write a word. Ask what this letter will say that the resume cannot. If you have no answer, either you do not need the letter, or you have not yet found the thing worth saying.
The structural test
If your cover letter would still make sense with a different company's name pasted in, it is not a cover letter. It is a personal statement, and it is doing nothing for this application.
Four paragraphs, and what each is for
The structure below is not the only one that works, but it is short, it is hard to get wrong, and each part has a clear job.
Paragraph one: the hook
Two or three sentences establishing who you are and why this specific role. Not "I am writing to apply for the position of", which spends your best sentence telling the reader something they already know from the subject line.
Weak: I am writing to express my interest in the Senior Analyst position at Acme, which I found on your careers page.
Better: I spent the last three years turning a support ticket backlog into the dataset our product team planned against. Your posting describes wanting the same thing built for onboarding, which is the part of this job I would take even without the title.
Paragraph two: one story, told properly
This is where most letters go wrong, by summarising the whole resume. Do the opposite. Pick the single piece of experience closest to what this job needs and tell it as a short story: the situation, what you did, what changed.
One story told with specifics is more persuasive than five achievements listed without them, because a story is checkable. It gives the interviewer their first question, and it demonstrates the thing itself rather than claiming it.
Paragraph three: why this company
The hardest paragraph, and the one most often filled with flattery. "I have long admired your commitment to innovation" says nothing and is transparently recyclable.
Real research is narrower than people expect. Read the last two things the company shipped, or the engineering blog, or the pricing page, or the founder's last three posts. Then say something only a person who did that could say: a view about a decision they made, a connection to a problem you have solved, a question about where a product is heading.
Twenty minutes of this is enough, and it is the twenty minutes that separates an application from a submission.
Paragraph four: close without grovelling
One or two sentences. Say you would welcome the conversation, name anything practical they need to know, stop. "Thank you for considering my application, I would be grateful for the opportunity" is three sentences of deference where one sentence of confidence belongs.
Length, format and where it goes
Half a page. Between 200 and 350 words. Nobody has ever complained that a cover letter was too short, and a full page of prose from a stranger is a thing people skim rather than read.
If the application has a text box, paste it in as plain text and forget the letterhead. If it wants an attachment, match the resume's typeface so the pair look like one application. If you are emailing a person directly, the letter is the email body. Do not attach a formal letter to an email that says "please see attached", which asks the reader to open a file to learn something you could have told them in the message.
Address it to a person where you can find one, and to the team where you cannot: "Dear Data Platform team" beats "To Whom It May Concern", which reads like a form letter because it is the salutation form letters use.
The three situations where it does the most work
- A career change. Your resume shows the old field and leaves the reader to do the translation. The letter is where you do it for them, by naming what transfers and why. This is the case where a letter most often decides the outcome.
- A gap or an unusual path. A resume can label a gap. Only a letter can give it a sentence of context and move on, which is far better than leaving a reader to invent one.
- A role you are slightly underqualified for. If the posting wants six years and you have four, the resume argues against you on its own. The letter is where the closest piece of evidence gets its own paragraph.
What happens to it on the other end
Knowing roughly how a letter travels explains several of the rules above. It is uploaded with the resume and attached to your record in the applicant tracking system, where it sits as a second document. Nobody reads it during the first pass, because the first pass is a recruiter working through a queue on the resume alone.
It gets opened at the second stage, and typically for one of two reasons. Either your resume was a clear yes and someone is now deciding between you and three other clear yeses, or your resume raised a question and somebody is checking whether the letter answers it. Both are exactly the moments a cover letter is built for, and both explain why a generic letter is a wasted opportunity rather than a neutral one: it is being read precisely when a distinguishing detail would have counted.
The third thing that happens is the one people forget. In the hiring conversation, somebody has to advocate for you out loud to colleagues who have not read your file. A letter containing one vivid, specific story hands them the sentence they will use. A letter of adjectives hands them nothing, and they will summarise you as "looks fine on paper", which is not what gets an interview scheduled.
When to skip it
If the application does not ask for one and you have nothing to say that the resume does not already say, skip it and spend the time tailoring the resume instead. A perfunctory letter is not neutral; it is a piece of writing you have submitted, and a reader will judge the writing. Fifteen minutes producing something generic is worse than not writing one at all.
On using AI to draft it
A language model will happily produce a competent, fluent, entirely generic cover letter in four seconds, and recruiters now read a great many of them. Fluency is no longer evidence of effort, which means the parts of the letter that AI cannot invent are worth more than they used to be, not less.
Those parts are the specific story in paragraph two and the researched observation in paragraph three. Use a model to fix your structure, tighten a clumsy sentence or cut a letter from 500 words to 300. Do not use it to supply the content, because the content is the only part that was ever doing the work.
Before you send it
- Company name correct, everywhere, including the file name.
- No sentence that would survive being pasted into another application.
- At least one specific, checkable claim.
- Read aloud, because clumsy sentences announce themselves the moment you hear them.
- Under 350 words.
Start from a letter that already works
Worked examples by role, each annotated with what the letter is doing and why, so you can see the structure before you write your own.
See cover letter examples