How to Write a Cover Letter, Paragraph by Paragraph
A cover letter is four short paragraphs: what you are applying for and why you are credible, why this company, the evidence that backs you up, and a plain close. Write it for one posting, keep it to a page, and make every sentence something you could only say about this job.
What the letter is actually for
Your resume is a table of evidence. It lists what you did and where, in the order it happened. What it cannot do is connect that history to this particular opening, because a resume is written once and sent many times.
The letter is the one place you make that connection in plain sentences. It answers three questions a hiring manager has while skimming: why is this person applying here, what could they do on day one, and would they be easy to work with. Everything else is decoration.
Assume it gets read fast, in a batch with many others. That is a reason to be specific early, not a reason to be loud. Specificity is the only thing that survives skimming.
The twenty minutes before you write
Most bad cover letters are preparation failures. Do this first and the letter takes fifteen minutes instead of two hours.
- Read the posting twice. On the second pass, mark the requirements that appear first, appear twice, or are described in unusual detail. Those are the real ones; the rest is boilerplate.
- Write down three true things you have done that map to those requirements. Not adjectives. Situations, with what changed because you were there.
- Find one concrete fact about the company that relates to the work. A product change, a new market, how the team is organised, something in the posting that suggests why the role exists now.
- Note the terminology the posting uses. If they say "customer success" and you say "account management", use their phrase. Screening software filters on the posting's own vocabulary, and people match faster when the words line up.
- Look for the hiring manager's name. A few minutes on the company site or the ad itself is worth it. If you cannot find it confidently, do not guess.
That fourth step is where people lose points quietly. SwiftCover shows which of a posting's keywords are missing from your documents, but a highlighter does the same job.
The four-paragraph anatomy
Paragraph 1: the opening
State the role, then give one concrete reason you are credible for it. No "I am writing to express my interest". No autobiography. The opening exists to buy you the second paragraph, and the strongest ones pair the role with the thing you have most obviously done before. We go deeper on that sentence in cover letter opening lines.
Paragraph 2: why this company
This is the paragraph most people skip, and the one that separates a real application from a mail-merge. You are answering: of all the places hiring for this, why here.
Good material: how the team is organised, a product decision you have an opinion about, a problem the posting implies they are having that you have handled. Bad material: the founding year, the mission statement, flattery anyone could write.
Paragraph 3: why you, with evidence
Two proof points, each tied to something the posting asked for. A proof point has a situation, an action, and a result you can defend in an interview. If you cannot say what changed, it is a duty, not an achievement.
| Duty (weak) | Proof point (strong) |
|---|---|
| Responsible for customer onboarding. | Rewrote kickoff into a two-call structure with a written success plan, and time to first value dropped by about a month. |
| Excellent communication skills. | Ran the weekly cross-team status note that replaced three standing meetings. |
Paragraph 4: the close
Short. Say what you want to talk about, handle any obvious logistics, thank them, stop. Do not promise to follow up on a specific date unless you will.
A complete worked example
Here is a full letter for a mid-level Customer Success Manager role at a fictional healthcare software company. The applicant, the company, and every number are invented for the example. Yours have to be true.
Dear Priya Raghavan,
I'm applying for the Customer Success Manager role on the Enterprise team. For the past four years at Coastal Systems I've owned mid-market healthcare accounts, which meant spending most of my time on the two things your posting leads with: onboarding customers who bought before they were ready, and starting renewal conversations early enough for them to matter.
The part that made me apply is that Verano has put implementation and ongoing ownership on the same team. I've worked the other way. A separate services group handed accounts over at go-live, and a good share of the first ninety days went into the customer re-explaining what they had already told someone else. Owning a customer from contract through renewal is the change I would have argued for where I am now.
Two things from my current job map to what you listed. On onboarding, I rebuilt our kickoff into two calls with a written success plan the customer signs off on, and average time to first value on new mid-market accounts went from about eleven weeks to seven. On renewals, I run a quarterly review that surfaces risk two quarters out instead of thirty days out; three accounts our forecast had written off renewed because of it. The flags behind that review come from usage dashboards I built myself.
I'd like to talk about how the enterprise segment differs from what I've been running, particularly multi-site rollouts, which I've done twice and want to get better at. My resume is attached, and I'm free for a call most afternoons over the next two weeks.
Thank you for reading,
Maya Osei
That is under 300 words including the greeting and sign-off, and nothing in it could be pasted into an application for a different company.
What each paragraph is doing
The opening does two jobs in one sentence
It names the role, so whoever is sorting applications knows where to file it, and it establishes the applicant as someone who has already done the core work. The clause after the colon is the real move: instead of claiming to be a strong fit, it restates the posting's own priorities and quietly says "that is my week already".
The second paragraph proves the letter was written for this job
It picks one structural fact about the company, then explains why it matters using the applicant's own experience of the alternative. That is the part worth stealing. Research alone reads as homework, and homework is easy to fake. Research plus a first-hand opinion reads as judgement, which is what a hiring manager is shopping for. It also stays out of trouble: no claimed inside knowledge, no criticism of the current employer.
The third paragraph is evidence, in the posting's order
Onboarding first, renewals second, because that is the order the posting used. Each point names a mechanism, not just an outcome: two calls with a written success plan, a quarterly review that surfaces risk two quarters out. Mechanisms make results believable, and they hand the interviewer an obvious question.
The close names a gap on purpose
Multi-site rollouts are admitted as the thin part, framed as something to get better at. This is not humility for its own sake. A letter with no edges reads as a brochure, and being upfront about one weak area makes the strong claims more credible.
If a sentence in your letter would still be true for a different company, cut it or make it specific.
Length, format, and sending it
Aim for 250 to 400 words on one page. Three or four paragraphs, no headings, no bullet lists unless a short list genuinely reads faster. We go into the trade-offs in how long a cover letter should be.
- Address a person by name if you found one, otherwise "Dear Hiring Manager". Never a guessed name.
- Send PDF unless the posting asks for something else, so your formatting survives.
- Name the file so a stranger can file it: your name, "cover letter", the company.
- If you apply by email, put the letter in the body as well as attaching it.
- Match the fonts and header of your resume so the two look like one application.
- Read it aloud once. Anything you stumble over, a reader will stumble over too.
Reusing structure is fine; reusing sentences is not
Keep a skeleton holding your two or three best proof points, written out properly. For each application, rewrite paragraph two from scratch and re-order paragraph three to match the posting. Ten minutes a letter rather than an hour, with the parts that must be specific still specific.
The final edit pass
Read the draft once, looking only for these:
- Adjectives doing a noun's job. "Passionate", "detail-oriented", "results-driven". Delete them and see whether the sentence still says anything. If not, replace it with what you did.
- Sentences about your feelings. "I was excited to see" and "I have always admired" cost a line each and prove nothing. One is survivable; three is a pattern.
- Anything the resume already says. Repeating job titles in prose wastes the only page where you get to explain them.
- Claims you could not defend. If a number would be awkward to explain in an interview, cut it. Overstating gets found out at exactly the wrong moment.
- The company name, everywhere. Check it twice.
The mail-merge slip
The error that undoes a good letter is the wrong company name, left in from the last application. It reads worse than a typo, because it proves the letter was not written for anyone. Before sending, search the file for the previous employer's name. More near-misses are collected in common cover letter mistakes.
If you would rather start from a draft than a blank page, SwiftCover on the web produces a tailored first version from a posting in about thirty seconds, and everything it writes is editable. Either way, the last pass has to be yours. You are the only one who knows which proof points you can defend.

