How to write a cover letter, in the order that actually works

1. Read the posting twice, with a pen

   First pass: what is the job. Second pass: what is the problem. The second pass is where letters come from. Look for the sentence that reads like a complaint — "our team is drowning in support tickets", "we need someone who can own the roadmap without hand-holding", "the last person left and took the process knowledge with them".

   Underline two things: the requirement mentioned twice (that's the real one), and any specific tool, metric or process named. Those are your hooks.

2. Pick one proof, not three

   Three achievements in 300 words means each gets ninety words of setup. One achievement gets a proper story: what was broken, what you did, what changed. Readers remember stories and forget lists.

   Choose the item that is closest to the underlined requirement — not the most impressive item in your history. A small, exactly-relevant proof beats a large, adjacent one.

   • With numbers: "cut time-to-value from 21 days to 9 across 300 accounts"
   • Without numbers: "rewrote the setup guide after watching eight customers fail at the same step, then watched eight more"
   • Early career: "ran the society's account from 900 to 4,100 followers in four months, on $340"

3. Name the gap yourself

   Every application has a weak point. If you don't name it, the reader fills in the worst version. One sentence, plain words, followed immediately by the adjacent evidence.

   Works: "I don't have a banking background; what I have is eighteen months explaining charges to people having a bad week."
   Fails: "While I may not possess every qualification listed, I am confident that my diverse skill set..." — that sentence is longer, vaguer, and reads as a dodge.

4. Write the opening last

   You can't write a good opening until you know what the letter proves. Draft the middle first, then write a first line that points at it. The opening only has to do two things: name the role, and make the reader want the next sentence.

   Two reliable shapes:

   • Answer the posting: "Your posting says the first ninety days are mostly about explaining a denied loan to someone already upset. That's the part of my last two years I'd point to first."
   • State the case plainly: "I want the support lead job at Northwind, and here is the shortest honest case for it: I cut our ticket backlog by two thirds in a quarter without adding headcount."

   Avoid: "I am writing to express my interest in the advertised position." It is true, it is grammatical, and it tells the reader nothing they didn't already know.

5. Make the ask specific

   The last paragraph is a request, not a summary. Never restate the letter — the reader just read it. Ask for one concrete thing, in one sentence, and then stop writing.

   "I'd welcome the chance to walk through the sample and hear how your team reviews a draft" is an ask. "I look forward to hearing from you" is a formality that requests nothing.

6. Cut the adjectives

   Search your draft for: passionate, dedicated, detail-oriented, dynamic, innovative, results-driven, team player, hard-working, excellent communication skills. Delete each one and see whether the sentence still means something. Usually it means the same thing, faster.

   Then check for sentences that would survive having the company name swapped for a competitor's. Those are the sentences that make a letter generic, and they are almost always the ones you were most pleased with.

7. Format it so it gets parsed

   One page, 11–12pt, standard margins, no header images, no text boxes, no tables. Export to PDF unless the portal asks for Word. Full specifics are on the format page — including the file-naming convention that keeps your file findable in a recruiter's downloads folder.

8. Read it out loud once

   Not silently. Out loud. You will hear three things: sentences that run out of breath, words you would never say to a person, and the exact spot where you started padding. Fix those three and stop editing — further passes make a letter worse, not better.

Next: see the annotated examples, grab a template, or draft one from your own evidence.