Cover letters fail when they read like generic manifestos (“I am passionate about innovation”). They win when they read like memos: short, specific, evidence-backed, and easy to forward.
This guide gives you Hook-Proof-Fit-Ask (named framework), an about 250-word example, and clear rules for when not to send one. Pair with LinkedIn outreach, referrals, resume truth in ATS format, and keyword alignment in resume keywords.
Hook-Proof-Fit-Ask (block timing)
- Hook (2–3 sentences): cite a specific artifact—launch, blog post, tech talk, reliability story—not “culture.”
- Proof (4–6 sentences): two tight wins with metrics/tools; mirror JD language where truthful.
- Fit (2–3 sentences): map your proof to their scope (first 90 days language).
- Ask (1 sentence): one next step—for example, offering to share a short design doc or proposing a 15-minute intro call.
Total target: 220–280 words for most roles.
Full example (about 250 words) — adapt, do not photocopy
Hook: I’ve been following Acme’s shift from quarterly releases to continuous delivery—especially your write-up on using feature flags to de-risk payments rollouts.
Proof: At Contoso, I owned the checkout read path in Go on Kubernetes. We cut p95 latency 34% by reshaping hot keys in Redis and tightening pool sizing; incidents dropped from ~3/month to zero over two quarters. I also partnered with PM and design on a progressive rollout playbook that became the default for revenue surfaces.
Fit: Acme’s Senior Backend role emphasizes SLOs, gRPC services, and cross-team incident hygiene—exactly the environment where I do my best work. I’m excited about the scope to harden APIs that touch real money at your scale.
Ask: If helpful, I can share a one-page architecture note on how I’d approach on-call readiness in the first 60 days—thank you for considering my application.
Notice: no “To whom it may concern,” no adjective soup, one ask.
Block-by-block alternatives
Hook alternatives: customer quote (public), changelog line, conference talk, OSS issue you contributed to.
Proof alternatives: reliability, security, cost savings, velocity, customer satisfaction—pick two, not six.
Fit alternatives: tie to team charter language from the JD; avoid guessing internal politics.
Ask alternatives: keep one ask max.
When to skip cover letters
Skip (or send a 3-sentence note) when:
- The portal forbids long text or strips formatting.
- The posting explicitly says resume only.
- You have no specific artifact—better silence than generic.
Do this instead: invest in resume tailoring + referral path—complete guide.
Voice checks (anti-AI)
Read aloud. Delete half the adjectives. If you would not say a sentence on a phone screen, do not write it.
Bad letter dissection (what went wrong)
“I am a highly motivated self-starter who thrives in fast-paced environments…”
Problems: no artifact, no proof, no scope, no ask. Recipients cannot forward this to a hiring manager without embarrassment.
Career switcher Hook variant
“I’m moving from support engineering to technical writing—your public API docs set a bar I’ve been reverse-engineering while helping customers integrate. Two shipped runbooks I wrote cut integration tickets ~22% QoQ…”
Proof anchors the pivot; Fit explains documentation systems you will strengthen.
Length by channel
- Email to HM: 200–280 words.
- Portal text box: 120–180 words—tighten Hook and Proof.
- Referral forward: 5-sentence blurb—see referrals.
Proof you can paste from your resume (mapping exercise)
Take two bullets from your resume. Rewrite them in cover letter voice (past tense, fewer acronyms). That is your Proof block—do not invent new wins in the letter; the letter compresses truth already on the resume.
Tone calibration by company archetype
- Big tech: crisp, metric-heavy, fewer adjectives.
- Startup: show ownership and ambiguity tolerance—still keep metrics.
- Regulated industries: mention compliance touchpoints you actually handled.
Soft CTA
Draft variants with AI cover letter generator, then edit ruthlessly. Track which letter earned which screen on JobTrackfy—features.
FAQ
Should I repeat my resume?
No—compress into two proofs max.
How do I find the hiring manager?
Sometimes in posting; otherwise address team/role—never fake a name.
Do typos matter?
Yes—proofread out loud.
Should I mention visa needs?
Follow posting instructions; be honest.
Can I use the same letter?
Never without rewriting Hook+Fit.
How do I mention referrals?
“If a mutual contact suggested I apply” in the Hook—only if true.
Should I mention salary?
Usually no in first letter—follow their process.
How do I mention DEI authentically?
Only if you have lived relevant experience; avoid performative statements.
What if the posting is in another language?
Match the posting language with a native speaker review if possible.
How do I mention side projects?
One sentence with link—only if JD-relevant.
Do hiring managers read letters?
Sometimes; assume skim—put strongest proof early.
How does this tie to ATS?
Humans still read letters; keep resume as canonical keyword surface—resume keywords · ATS format.
Should I mention a referral in the Hook?
Only if true—see referrals guide.
Proofreading swap (15 minutes)
Trade letters with one peer: mark only unclear sentences and missing numbers. Do not rewrite each other’s voice—clarity only.
One-line P.S. rule (optional)
If the portal allows a P.S., add one line that references something you did not repeat above—often a link to a public artifact. Never use a P.S. to sneak in salary demands.
Hook-Proof-Fit-Ask is a container for respect: short, specific, forwardable. Ship the letter when it is true, tight, and easy to forward—not when it is perfect. Speed without lies wins. Then measure replies, not ego.