The Four-Paragraph Cover Letter

The blank page is most of the difficulty. Give the page a shape and the writing takes ten minutes.

Here’s a four-paragraph structure where each paragraph has exactly one job. It works for almost any advertised role, it produces something around 300 words, and once you’ve used it twice you’ll stop needing to think about it.

The shape

Paragraph 1 — The hook. What you’re applying for and the single most relevant thing about you. Two sentences.

Paragraph 2 — The match. One specific requirement from the posting, and the concrete experience that maps to it. Three or four sentences. This is the paragraph that does the work.

Paragraph 3 — The extra. Something the resume can’t convey: context, a trade-off you navigated, a second angle. Two or three sentences.

Paragraph 4 — The close. A genuine question or observation, and a simple sign-off. Two sentences.

Four paragraphs, around 300 words, no filler.

A complete example

Hypothetical, for a posting seeking an operations analyst at a logistics company, where the description emphasised consolidating reporting across regional teams and “bringing order to fragmented data.”

Dear Priya,

I’m applying for the Operations Analyst role. The posting’s line about consolidating reporting across the regional teams is close to what I spent most of last year doing at Northwind, so I wanted to write rather than just submit the form.

At Northwind we had three regional operations teams each producing their own weekly numbers, and none of them agreed. I ended up owning the consolidation. The technical part — pulling everything into one Postgres warehouse and building the weekly view — took about six weeks. The other four months were spent getting the three teams to agree on a shared definition of a completed delivery, because each region had a slightly different one and every reconciliation failure traced back to that. We now run one weekly report that all three regions accept, and the monthly close went from four days to one.

The thing I’d flag from that experience: the hard part was almost never the data modelling. It was that people had reasonable, incompatible reasons for measuring things their own way, and the consolidation only stuck because we resolved that first rather than imposing a schema and hoping. I’d approach yours the same way.

One thing I’d want to understand early is whether your regional teams currently have their own analysts, since that changes whether this is a build job or a coordination job — mostly it’s been both, in my experience. Happy to talk whenever suits.

Best, Sam Okafor

That’s 290 words. Look at what it does: names the specific requirement, gives a concrete story with a real outcome, offers a genuine insight about the work, and asks a question that demonstrates the writer has thought about how the role actually operates.

And notice what it doesn’t do. No admiration for the company’s mission. No claim to be a great fit. No restating of the resume. No “I am writing to express my strong interest.”

Paragraph by paragraph

1. The hook

Two sentences. Say what you’re applying for, then say the one most relevant thing.

Weak: I am writing to express my strong interest in the Operations Analyst position I saw advertised on your careers page. With over six years of experience in analytics and a proven track record of delivering results, I believe I would be an excellent addition to your team.

Better: I’m applying for the Operations Analyst role. The posting’s line about consolidating reporting across the regional teams is close to what I spent most of last year doing at Northwind.

The second version is shorter and contains actual information. More on this in openings — the general rule is that your first sentence should be one only you could write.

2. The match

The most important paragraph. Pick one requirement from the posting — the one you’re strongest on, or the one that seems central — and tell the story of having done it.

Tell it as a story, not a summary. What was the situation, what did you do, what happened. Include one or two real specifics: three teams, six weeks, four days to one. Specifics are what make it credible; use numbers you’d be comfortable explaining in an interview.

Resist covering three requirements. One told properly beats three listed.

3. The extra

This is where the letter earns its place, and it’s the paragraph people leave out.

Say something about the work that shows judgement. The thing that turned out to be hard. The trade-off. The mistake you’d avoid next time. In the example, it’s the hard part was never the data modelling, it was that people had reasonable incompatible reasons for measuring differently.

That sentence tells the reader you’ve genuinely done this rather than been near it. It’s the difference between a candidate who can describe a project and one who’s learned something from it.

If you truly have nothing to put here, a second relevant experience works. But look harder first — there’s usually something.

4. The close

A genuine question about the role, and a plain sign-off.

The question does two jobs: it proves you engaged with the role as a real job rather than a posting, and it gives the reader something easy to reply to. Make it real. If you don’t have a question, an observation about the problem works instead.

Weak: Thank you for considering my application. I look forward to the opportunity to discuss how my skills and experience can contribute to your team’s success.

Better: One thing I’d want to understand early is whether your regional teams currently have their own analysts, since that changes whether this is a build job or a coordination job. Happy to talk whenever suits.

Practicalities

Address a person if you can find one. “Dear Priya” or “Dear Ms Raman” — either register is fine; match the company’s apparent formality. If you genuinely can’t find a name, “Hello” or “Dear Hiring Team” beats “To Whom It May Concern,” which reads like 1985.

Match the reader’s formality, roughly. A startup and a law firm warrant different registers. Neither warrants stiffness.

One page, always. 250–350 words. If it’s longer, paragraph two is probably covering three requirements instead of one.

In an email body, cut to three paragraphs and about 180 words. Merge two and three. Nobody scrolls.

Reuse the shape, not the text

The structure is reusable. The content isn’t.

Paragraph two changes completely for every application, because it’s anchored to a specific requirement in a specific posting. Paragraphs one and four change substantially. Paragraph three sometimes survives between similar roles.

If you find yourself sending the same letter with the company name swapped, you’ve kept the wrong part. The company name isn’t what makes it specific — the paragraph about their actual problem is.