How to Negotiate Your Salary with Confidence
The conversation waiting at the end of a successful application — worth preparing before you need it.
Read the guide →
Most cover letters fail in the first sentence, and for the same reason: they use the most-read line in the document to announce that the writer is applying for a job, which the reader already knows. This guide rebuilds the letter around what a hiring manager is actually scanning for — evidence that you understood the role and can do the difficult part of it. Five short sessions: what the letter is for, how to mine a job ad for the three requirements that matter, a four-paragraph structure you can refill forever, opening lines that could only have been written for this job, and a ten-minute tailoring routine.
What you'll be able to do: In five short sessions, write a cover letter a hiring manager finishes — and a structure you can refill for every application after it.
Outcome: "I can say in one sentence what my letter has to do that my CV cannot."
Take the last cover letter you sent — or any sample you can find — and delete every sentence that only repeats something already visible on the CV. Look at what survives. Usually it's two or three lines, and those lines are the only real letter in there.
A CV lists what you have done. The letter explains why that matters for this job, at this company, now. Hiring managers skim it for one thing: evidence that you understood the role and can handle the part of it they're actually worried about. Anything that restates the CV in prose is spent space. Half a page, 200–300 words, four short paragraphs — longer letters don't get read further, they get read less.
Weak: "I am writing to apply for the position of Operations Coordinator as advertised on your website. I have five years of experience in operations and believe I would be a good fit for your team." Three lines, and every fact in them is already on the CV. Strong: "You're hiring an Operations Coordinator to get a warehouse move done without pausing shipments. I ran exactly that move for a 40-person distributor last year — we lost half a day, not the two weeks everyone predicted." Identical length. The second tells the reader you read the ad, identified the hard part, and have done it before — which is the entire job of the document.
Outcome: "I can pull the three requirements that actually drive the hiring decision out of any job ad."
Paste the job ad into a document and highlight every sentence describing a problem or a responsibility. Ignore everything about culture, benefits, and being a fast-paced team — none of it tells you what the job is.
Job ads are written by committee and list far more than matters. Three signals separate the real requirements from the noise: what appears in the first third of the ad, what gets repeated in different words, and what the job title itself promises. A requirement buried at the bottom of a twelve-item list — "familiarity with Jira a plus" — is decoration. Pick the top three and build the letter around them. A letter that answers all twelve bullets in turn reads like a form and proves nothing.
The first third mentions response times twice in different words — "faster first replies" and "cut our backlog" — so that's real and it's the priority. The title says Lead, so managing people is real even though it appears only once. Bullet nine asks for Zendesk experience, but tools are learnable and belong on the CV, not in the letter. The three that matter: reducing first-reply time, running a small team, and owning a queue end-to-end. Everything else in that ad is context. The letter now has a target, and one paragraph of evidence aimed at the first item will do more than a paragraph mentioning all three.
Outcome: "I have a structure I can refill for any application in under an hour."
Write four headings on a blank page: Hook, Proof, Fit, Ask. You'll fill them in that order, which means you never again start a letter from an empty page.
Hook (2–3 sentences): name the problem the role exists to solve and claim you've solved it. Proof (3–5 sentences): one concrete story with a number in it, aimed at requirement number one from Chapter 2. Fit (2–3 sentences): why this company specifically — something true that you could not have written about a competitor. Ask (1–2 sentences): a plain request for a conversation with your availability. No "I look forward to hearing from you at your earliest convenience."
Hook: names the backlog problem from the ad and claims a fix. Proof: "At my current employer the queue averaged 31 hours to first reply. I re-triaged by issue type instead of arrival order and set a two-hour target on the two most common types; within six weeks the average was four hours, with the same five people." One story, one number, aimed squarely at requirement one. Fit: refers to a specific product change the company shipped recently and what it implies for their support mix — impossible to write without having looked. Ask: "I'd like twenty minutes to walk you through how I'd triage your current queue — I'm free most afternoons this week." Total: 260 words.
Outcome: "My first sentence says something only someone who read the ad could have written."
Write your current opening line, then write underneath it: "Could someone applying for a different job at a different company have written this?" If the answer is yes, it isn't an opening line — it's a throat-clear.
Roughly nine in ten letters open with "I am writing to apply for the position of X as advertised on Y." It isn't wrong, it's empty: it spends your most-read sentence telling the reader something they already know. Three openings that work — name their problem, lead with your most relevant number, or open with a specific observation about their product or market. All three prove you did work before you wrote, which is the only thing the opening has to achieve.
Problem-first: "Your ad says first replies currently take over a day. That's usually a triage problem rather than a headcount problem — and I've fixed it before." Number-first: "I cut a support queue's first-reply time from 31 hours to four, without adding a single person." Observation-first: "Since you launched self-serve onboarding in March, your support mix has probably shifted from setup questions to billing ones — which needs a different queue structure, not more agents." Each one is impossible to recycle for another company, and each one earns the second sentence, which is all an opening has to do.
Outcome: "I can adapt my letter to a new job in ten minutes without it reading like a template."
Take your draft and cut it by twenty percent without removing a paragraph. Every letter survives this and most improve, because the first thing to go is always throat-clearing.
The Proof paragraph is the reusable part: own two or three stories and rotate whichever fits. Hook and Fit get rewritten for every application — those are the two paragraphs a reader judges for whether the letter was written for them. Before sending, three checks: the company name appears and is spelled correctly (the most common fatal error in the entire process), nothing in the letter contradicts the CV, and the file is a PDF named FirstnameLastname-CoverLetter-Company.pdf rather than 'cover letter final v3.docx'.
The support-queue Proof paragraph carries over word for word — it's true for both applications. The Hook changes, because the second ad emphasises churn rather than backlog, so the problem named changes with it. The Fit paragraph is rewritten from scratch: the first referenced a product launch, the second references the company's expansion into a new market. Elapsed time: eleven minutes. The two letters share a paragraph, but they read as separately written — because the two paragraphs that signal effort are both new, and those are the two the reader actually weighs.
The complete guide — all 5 chapters, every checklist and exercise — as a clean, printable PDF. No email required.
A one-page cheat sheet of the method, a 75-minute workshop script to run it live with someone else, and 12 affirmations and reflections to keep nearby.
Every guide on this site is produced with the Self-Directed Learning Framework: instead of an article that explains a topic at you, the framework turns it into a structure you work through — each chapter with one outcome, a starting action under twelve minutes, the minimum you actually need to know, a worked example, a checklist, and exercises. It starts from three questions:
Topic: Writing a cover letter that actually gets read and gets interviews.
Outcome wanted: Have a finished letter for a real application, plus a reusable structure I can adapt in ten minutes — within five days.
Starting point: Some background — comfortable writing, but the letters feel generic and never seem to make a difference.
The prompt framework behind it is public: see the C.R.A.F.T. prompt framework, including the exact prompt that generated this library.
The conversation waiting at the end of a successful application — worth preparing before you need it.
Read the guide →Free, self-paced guides across everyday, professional and academic topics.
See all guides