Cover Letter Writing
Parent: Writing and Documentation · Published reference · snapshot 2026-09-08 · skill career-and-formal-writing/references/cover-letter-writing.md
↓ Facts as markdownall context files
The cover letter is a narrative artifact — a focused, one-page argument for why this human should be in this role at this company. Customization per application is non-negotiable.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Overview
- The cover letter is a narrative artifact - a focused, one-page argument for why this human should be in this role at this company. Customization per application is non-negotiable. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#overview]
1. The three-part skeleton
- Why this company. Show evidence you've done your homework: a product they shipped, a value they've published. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#1-the-three-part-skeleton]
- Why this role. Connect the specific responsibilities to specific skills or experiences you have. Reuse 2-3 keywords from the JD. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#1-the-three-part-skeleton]
- Why me. Demonstrate through evidence and stories. Don't list skills; show outcomes. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#1-the-three-part-skeleton]
2. Opener discipline
- "I am writing to apply for the X position at Y." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#2-opener-discipline]
- "My name is X and I am a [degree/title]." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#2-opener-discipline]
- "I noticed your team published the design for the X system last month - the tradeoffs you made on Y are the same ones I worked through at Z." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#2-opener-discipline]
3. Show evidence, don't list skills
- Weak: "I have strong project management skills and am highly organized." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#3-show-evidence-dont-list-skills]
- Stronger: "Last year I shipped the X migration on a six-engineer team. The original estimate was four months; we delivered in five because I caught a dependency that wasn't in the original scope." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#3-show-evidence-dont-list-skills]
4. Length conventions
- One page maximum, no exceptions. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#4-length-conventions]
- 250-350 words is the standard target. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#4-length-conventions]
- 3-4 short paragraphs, block-formatted. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#4-length-conventions]
5. Customization per application
- At a minimum, customize: [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#5-customization-per-application]
- Company name and the "why this company" paragraph [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#5-customization-per-application]
- 2-3 keywords from the JD [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#5-customization-per-application]
- The job title in the opener [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#5-customization-per-application]
6. Signature and sign-off
- Salutation: "Dear [Name]," when you know the hiring manager's name. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#6-signature-and-sign-off]
- Sign-off: "Sincerely," is the universal safe choice. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#6-signature-and-sign-off]
- Capitalization: Only the first word of the closing phrase is capitalized. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#6-signature-and-sign-off]
7. The "I" parade
- Count how many sentences open with "I." If more than half do, the letter reads self-absorbed. Vary openings: lead with the company, the role, the project, the result. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#7-the-i-parade]
Anti-Patterns
- The cliché opener. "I am writing to apply..." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
- The reused letter. Generic flattery, no company name in the first paragraph. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
- The skill list. "Strong communicator, fast learner, team player." [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
- The resume rehash. Repeating the resume's bullets in paragraph form. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
- The two-page letter. Always cut to one page. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
- The typo in the company name. Auto-disqualifying. [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#anti-patterns]
References
- Ask a Manager - this is how to write a good cover letter (Alison Green, 2024) [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#references]
- Harvard Business Review - Cover Letters Still Matter (2025) [archived source: https://llms-explorer.com/sources/mdb-context-hub/cover-letter-writing/#references]
Where this helps
- Applying to a role where the job posting invites a cover letter, or where a hiring manager's stated preferences signal one will actually be read. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A career pivot or nonlinear background where the resume's bullet points alone don't explain the connection between past experience and the target role — the letter is where that argument gets made. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A referral or warm connection, where naming that context and the specific reason for applying can meaningfully change how the resume gets read. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A competitive application where why-this-company, why-this-role, and why-me need to be argued explicitly rather than left for the reader to infer from a generic resume. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
How to apply this
- Draft against the three-part skeleton — why this company, why this role, why me — for a specific application, then check whether each section survives if you swapped in a different company's name; if it does, it's too generic. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Replace any skill-listing sentence such as "I have strong project management skills" with a single concrete outcome-based story, following the weak-vs-stronger pattern of estimate, catch, delivered result. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Count how many sentences open with "I" before sending; if more than half do, rewrite some openers to lead with the company, the role, or the result instead. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Customize at minimum the company name, the why-this-company paragraph, two to three keywords pulled from the job description, and the job title in the opener, for every application. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Common mistakes
- Opening with a cliché line like "I am writing to apply for the X position," which wastes the reader's first and most attention-getting sentence on filler. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Sending a reused, generic letter with no company name or company-specific detail in the first paragraph, signaling the application wasn't customized. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Rehashing the resume's bullet points in paragraph form instead of adding a story the resume couldn't tell. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Going past one page, which by convention signals a lack of editing discipline regardless of how good the content is. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Limitations
- The one-page, 250-350 word convention is a norm, not a rule enforced anywhere, so it can vary by industry, seniority, and region in ways this pack doesn't fully cover. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A perfectly crafted cover letter cannot compensate for a resume that doesn't support its claims — the two documents have to agree, and this pack covers only the letter. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- Customization advice assumes real, specific detail about the target company is findable; for a company with almost no public presence, the why-this-company paragraph is much harder to make credible. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
- A typo in the company name is called out as auto-disqualifying, but the pack doesn't quantify how forgiving different hiring processes actually are about smaller errors elsewhere in the letter. [source] — AI-suggested, synthesized from this pack's existing facts — not extracted from a source document.
Children
- No children recorded.