The 5-Part AI Cover Letter Playbook (with prompt templates)

The 5-part structure that actually works

Cover letters fail in one of two ways: they describe the candidate (generic, recycled, ignored) or they describe the company back at them (creepy, sycophantic, ignored). The structure that works is the one that connects you to them. Five parts, ~300 words total.

1. The hook (1–2 sentences). One specific, concrete thing about the company that you noticed and that informs your interest. Not “I love your mission.” Something like: “Your recent decision to open-source the embeddings cache is exactly the kind of trade-off — short-term moat for long-term ecosystem — that I find rare in B2B SaaS.”
2. The bridge (2–3 sentences). Why you specifically care about that or are well-positioned to contribute to it. This is where your unique combination of experience matters.
3. The proof (1 short paragraph). One specific story — past role or project — that demonstrates the most relevant skill in the JD. Numbers, not adjectives.
4. The question (1 sentence). A genuine, specific question for the team. This is what gets you a callback from senior people; it signals you've thought about the role beyond the JD.
5. The close (1 sentence). Plain, no flourishes. “I'd love to talk through how I could contribute. Available any afternoon next week.”

AI prompts that produce useful first drafts

The pattern that works: give the AI your achievements + the JD + the structure + a tone constraint. Don't ask for “a cover letter for [company].” You'll get a Wikipedia entry written in the second person.

Prompt 1 — Initial draft

You are helping me draft a cover letter for a job application.

Job description:
[paste full JD]

My resume (most relevant parts):
[paste 5–6 bullets and any relevant projects]

One specific, recent, public thing I noticed about the company (not from their About page):
[your hook research — 1–3 sentences]

Write a 300-word cover letter in 5 paragraphs:
1. Open with the specific thing I noticed above (don't restate generically — engage with it).
2. Bridge to why I care about that or am positioned to contribute.
3. One paragraph of proof — pick the single most relevant achievement from my resume and tell it as a 4-sentence story with numbers.
4. One genuine question for the team.
5. A plain closer with availability.

Tone: warm, direct, no jargon, no superlatives. Read like a person, not a press release.
Do NOT invent facts. If you need information you don't have, leave a [bracket] for me to fill in.

Prompt 2 — Tightening pass

Take this cover letter and:
1. Cut every adjective that doesn't make a claim concrete.
2. Replace every passive verb with an active one.
3. Remove the word “I” from the start of any sentence where it's possible.
4. Make sure no sentence is longer than 20 words.

Return only the revised letter.

[paste your current draft]

The 4-pass human edit

AI drafts are a starting point. They need a 5-minute human edit to not read like every other letter. Four passes, in this order:

1. Voice pass. Read the letter aloud. Anything that you would never actually say — replace with your own phrasing.
2. Specificity pass. Underline every adjective. If it's vague (“exciting,” “innovative,” “dynamic”), replace it with a fact.
3. Self-erase pass. Count how many sentences start with “I.” Anything over 2 — rewrite.
4. One-claim pass. Each paragraph should make exactly one point. If it makes two, split it. If it makes none, cut it.

Format and length rules

• Length: 280–340 words. Below 250 reads thin; above 400 reads padded.
• Salutation: Use the hiring manager's name if you can find it. “Hi [First Name],” outperforms “Dear Sir/Madam” by every measure.
• Format: Body of the email, not an attachment. If the application requires an upload, paste as plain PDF with name, email, and date at the top.
• Signature: First name, last name, phone, link to resume or LinkedIn. Nothing else.

Common traps to avoid

• “I am applying for the [Role Title] position at [Company Name].” — every recruiter's autocomplete brain skips this sentence. Delete it.
• Quoting the company's mission statement back at them. They wrote it. They know.
• Long lists of skills duplicated from your resume. The letter is for the story behind the skills.
• Apologizing for anything — gaps, career changes, lack of a specific skill. State, don't apologize.
• Sentences over 25 words. Cut them.

The 'genuine question' part — why it works

We've watched dozens of users get callbacks specifically because of the question paragraph. It works for two reasons. First, it signals you've read past the JD and into how the role actually works. Second, it gives the hiring manager an easy reply — they don't have to evaluate you, they can just answer the question, and now you're in a conversation. Examples that work:

• “How does the team currently split feature work between the platform group and the product squads — is there a queue, or do squads own their migrations end-to-end?”
• “I noticed the JD lists both Redshift and ClickHouse. Curious which workloads landed on which, and whether the split has changed since the migration last year.”