cover-letter-writer

Overview

Most cover letters are ignored because they restate the resume. A good one does three things in under 300 words: shows you understand what the company needs, connects one or two proof points from your history to that need, and sounds like a human being. This skill drafts cover letters anchored to a specific posting, with a voice that matches the company's culture.

When to use

• A job posting explicitly requests a cover letter

• • Applying to startups, nonprofits, or creative roles where the letter carries weight

• Career pivots where the resume alone doesn't explain the "why"

• Cold outreach to hiring managers or founders

• Referral-based applications where you want to name the connection gracefully

Core concepts

• • • The 3-paragraph structure. Paragraph 1: the hook — which role, why this company specifically (one concrete reason). Paragraph 2: the proof — 1-2 achievements mapped to the posting's top requirements. Paragraph 3: the close — enthusiasm, logistics, call to action.
• • • Mirror, don't parrot. Use the posting's vocabulary for skills and problems, but in your own sentences. This signals fit without sounding like a keyword list.
• • • One story beats three claims. A single vivid example ("cut churn 18% at a Series B SaaS") is more persuasive than "I am results-driven, collaborative, and innovative."
• • • Voice calibration. A fintech bank and a game studio want different tones. Read the posting and the company's public writing, then match formality — slightly warmer than the posting, never colder.
• • • The referral line. If referred, say so in the first two sentences: "Jane Park suggested I apply" — it's the highest-signal sentence a letter can contain.
• • • Brevity is respect. Hiring managers skim. 250 words that get read beat 600 words that get closed.

Practical workflow

1. 1. 1. Gather inputs. Job posting (required), the candidate's tailored resume or key achievements, any connection to the company (referral, customer, prior interaction), and the hiring manager's name if known.
2. 2. 2. Extract the top 3 needs. From the posting, identify the 2-3 problems this hire must solve. The letter's proof paragraph maps directly to these.
3. 3. 3. Find the hook. What's genuinely interesting about this company to this candidate? A product they use, a technical decision they admire, a market they know. Generic flattery ("industry leader") is worse than no hook.
4. 4. 4. Draft tight. Three short paragraphs, active voice, first person. Name the role and requisition if applicable. Keep sentences under 20 words.
5. 5. 5. Insert proof, not promises. Each claim about ability gets evidence: a metric, a project, a decision. "I led X, resulting in Y" — never "I believe I would excel at X."
6. 6. 6. Close cleanly. One sentence of genuine enthusiasm, one line on availability/next steps, professional sign-off with contact details.
7. 7. 7. Tone check. Read it aloud. If it sounds like a template with names swapped in, rewrite the hook and proof until it sounds like a person who did homework.

Common pitfalls

• • • Summarizing the resume. If the letter just narrates the work history, it adds zero information. It should add context the resume can't: motivation, fit, trajectory.
• • • Starting with "I am writing to apply for..." Dead on arrival. Open with the specific reason this role at this company, or the referral.
• • • Apologizing for gaps or pivots. Frame transitions as deliberate ("after five years in support, I moved into success to own outcomes end-to-end") — never defensive.
• • • Over-formatting. No tables, no headers with graphics, no unusual fonts. A clean letter in the same font as the resume.
• • • Sending the same letter everywhere. Recruiters can smell a mail merge. One customized paragraph per company is the minimum viable effort.
• • • Forgetting the attachment basics. PDF named "FirstName-LastName-Cover-Letter.pdf", and if pasted into a form, strip formatting that breaks in plain text.