The 4-paragraph developer cover letter that actually gets read (under 200 words, with a full example)

Most developer cover letters are never read, and the ones that are read are usually read for the wrong reason: the hiring manager is looking for a reason to say no. That is not cynicism, it is what happens when one person has 300 applications and a job to do. So the letter has one goal: survive the first two sentences and give the reader a reason to open the CV with interest instead of suspicion.

Here is the structure that does that. It is four short paragraphs, under 200 words, and it takes about 25 minutes per application once you have done it twice.

Paragraph 1: their problem, your proof (2 sentences)

Do not open with "I am writing to express my interest in the position of...". The reader knows what you are writing about. Open with the thing the company is trying to do, taken from the posting, and the single thing in your history that proves you can do it.

You are hiring a backend developer to move Payflow's ledger from batch to streaming. I did that at Fintra in 2025: the settlement service went from a nightly job to Kafka-driven processing, with latency down from hours to under two minutes.

Two sentences. The reader now knows you read the posting and that you are not a random applicant. That is already more than 80% of letters achieve.

If you are a junior and do not have a professional proof, use a project, and be specific: "I built a full-stack e-commerce app with Stripe Checkout and 38 tests; the hardest part was merging guest and logged-in carts, which I solved server-side."

Paragraph 2: three matches (bullets are fine)

Take the three most important requirements in the posting and answer each one with a fact. Not "I am proficient in TypeScript" but "TypeScript daily for two years; migrated a 40k-line JavaScript codebase to strict mode."

• Kafka in production: three services, ~40k events/day, exactly-once processing.
• PostgreSQL performance: cut the reconciliation query from 12 s to 300 ms with a partial index and a rewrite.
• Small teams: I was one of two backend developers; I am used to owning things end to end.

The point of bullets is that the reader can check the three boxes in ten seconds. Pick requirements from the posting, in their order. If you only match two of three, say so honestly and explain how you would close the gap; it reads far better than padding.

Paragraph 3: why them, in one honest sentence

One sentence, and only if it is true. "I have followed your engineering blog since the post on idempotent webhooks" is good. "I am passionate about your mission to revolutionize payments" is noise. If you have no real reason, skip this paragraph; nothing is lost.

Paragraph 4: the ask (1-2 sentences)

Say what you would like to happen next and offer something concrete.

I would be glad to walk you through the migration plan I used, including what I would do differently today. My CV is attached; I am available for a call any weekday after 4 pm CET.

Sign with your name, city and a link to your GitHub or portfolio. No "Sincerely yours" theatre.

What to leave out

• Your life story, how you got into programming, what you studied unless it is directly relevant.
• Anything that repeats the CV verbatim. The letter is the argument; the CV is the evidence.
• Adjectives about yourself: passionate, motivated, hard-working, detail-oriented. Every one of these is a sentence the reader skips.
• Apologies ("although I do not have professional experience..."). State what you have; let them decide.

A junior example, complete

Hi Andrea,

Nortwind is looking for a junior frontend developer to help ship the new dashboard in React. My final bootcamp project is a React dashboard: eight chart views on a live API, with loading and error states for every one of them, and Lighthouse at 96. Live: nortdash.example · repo on GitHub.

From the posting:

• React with hooks and TypeScript: both projects on my CV, strict mode on.
• Working with designers: I built the dashboard from Figma files with a designer from the bootcamp; two rounds of review.
• Testing: 40 tests with Jest and Testing Library; CI on every push.

I have used your product for a year as a customer and have a short list of small UI things I noticed, if that is ever useful.

I would be glad to walk you through the dashboard code. CV attached; available for a call any afternoon.

Marc Puig · Barcelona · github.com/…

168 words. It gets read.

Checklist before sending

1. First sentence names their problem; second sentence gives your proof.
2. Three matches, each with a fact, in the posting's order.
3. One honest "why them", or none.
4. A concrete offer and your availability.
5. Under 200 words, zero adjectives about yourself.

If you want one written for a specific posting, that is what I do at DevCV Rewrite: a tailored cover letter is 9 EUR, a full CV rewrite 19 EUR, both delivered within 24 hours with a 14-day refund. There are before/after samples so you can see the format first.