Skip to content
Writing Style Library

Cover Letter

A letter accompanying an application that makes the case for one specific person for one specific role.

Cover Letter

Section titled “Cover Letter”

A cover letter accompanies a resume or application and makes the case for one specific person for one specific role. It connects the applicant’s experience to the posting’s stated needs, in the applicant’s own voice, and asks for the interview. Unlike cold outreach, which contacts a stranger with no posting and no established opening, a cover letter responds to an advertised opportunity and assumes the reader is already evaluating candidates against a known set of needs.

The format is not a prose version of the resume. The resume lists; the cover letter argues. The argument is always the same: given what you need and what I have done, an interview is the logical next step. Everything else - the opener, the body, the close - exists to build that argument and make it feel earned rather than asserted.

Canonical template

Section titled “Canonical template”
[Header: Applicant name, contact info, date]
[Employer name, title, company, address - optional for email submissions]


Dear [Hiring Manager Name, or Hiring Team if name unknown],


[Opening: name the specific role and establish the applicant's direct claim to it. One to two sentences.]


[Body 1: connect the applicant's single strongest relevant experience to the posting's primary stated need.
Name the experience specifically - a result, a project, a problem solved.]


[Body 2 (optional): address a second stated need or preempt an obvious gap. Two to three sentences.]


[Closing: ask for the interview directly. One sentence. Do not hedge.]


Sincerely,
[Name]

When to use

Section titled “When to use”

Applying for an advertised job posting that explicitly requests a cover letter; applying for a role where the resume alone cannot convey the relevant fit; situations where a career change, gap, or unconventional background needs framing; applications to organizations where cultural fit and voice matter alongside the credential; any application where the job description names specific values or priorities the applicant can address directly.

When not to use

Section titled “When not to use”

Applications that explicitly state no cover letter or use form-only intake; initiating contact with a company that has no open posting (use cold outreach instead); submitting to job boards where the system strips attachments and only the resume reaches the screener.

Pairs well with

Section titled “Pairs well with”

senior-consultant, direct-communicator, confident, diplomatic, problem-solution

Often confused with

Section titled “Often confused with”

cold-outreach: Cold outreach is a first-contact message to a stranger with no prior relationship and no established opening - it earns a reply by leading with a specific, researched observation about the recipient, because there is no shared context to draw on yet. A cover letter differs in every structural decision that matters: it responds to an advertised opportunity, addresses a reader who is already evaluating candidates against known needs, and leads with the applicant’s direct claim to the role rather than an observation about the employer.

Tells

Section titled “Tells”
  • Opens by naming the specific role and the applicant’s direct reason for applying to this employer
  • Body paragraphs map named applicant experiences to the posting’s stated needs, not to the category
  • Asks for the interview by name in the closing paragraph, without hedging
  • Written in first person; formal salutation and sign-off frame a professional register
  • Length held to 250-400 words: enough to argue the case, not enough to restate the resume
  • Every paragraph has one job: open to establish fit, body to prove fit, close to ask for the interview

Anti-patterns

Section titled “Anti-patterns”
  • Summarizing the resume instead of arguing from it - The cover letter’s job is to make a case, not recap facts the reader already has. “As my resume shows, I have five years of experience” adds nothing; naming a specific result closes the argument.
  • Writing a generic letter that could apply to any employer in the industry - Hiring managers identify generic letters immediately. The letter must name the employer’s specific stated need, project, or value. A generic opener signals the applicant did not read the posting.
  • Opening with a recipient-first observation about the employer rather than the applicant’s direct claim to the role - Cold outreach earns a stranger’s attention by leading with a specific, researched observation about the recipient because there is no shared context or established opening to draw on. A cover letter responds to an advertised posting; the reader is already evaluating candidates and needs to know what the applicant brings to the role, not a researched observation about the company.
  • Hedging the closing ask with phrases like “I hope to hear from you” or “I look forward to possibly connecting” - The closing is the only sentence that asks for what the letter exists to request. Softening it signals low confidence and dilutes the argument the preceding paragraphs worked to build.

Failure modes

Section titled “Failure modes”
  • Piles on credentials until the letter reads as a second resume - every sentence claims a qualification, none of them builds toward the ask - Two or three well-chosen examples outperform six that compete for attention. If the draft exceeds 400 words or feels like a credential inventory, cut to the strongest and let the resume carry the rest.
  • Assertiveness tips into presumptuousness - the closing moves from asking for the interview to informing the reader when the applicant will follow up or how the process should proceed - The ask should be confident but calibrated to the actual power dynamic: the applicant requests the interview, the employer grants it. “I would welcome the opportunity to discuss this role” is assertive; “I will call Tuesday to schedule” assumes authority the applicant does not hold.
  • The own-voice quality overshoots into casual register or confessional disclosures that undermine the professional credibility the format exists to establish - Cover letter voice is the applicant’s professional voice, not their conversational one. One sentence of genuine specificity about the role earns authenticity; a paragraph of personal backstory or informal language tips the letter outside the hiring context.

Instruction

Section titled “Instruction”
Write as a cover letter. The applicant is responding to an advertised job posting and must make
the case for one specific person for one specific role. Open by naming the role and establishing
the applicant's direct claim to it - not the company's prestige, not a generic statement of
enthusiasm, but the applicant's specific fit. In the body, map the applicant's strongest relevant
experiences to the posting's stated needs by name. Do not summarize the resume; argue from it.
Name results, projects, or problems solved. In the closing paragraph, ask for the interview
directly and without hedging. The format is not cold outreach - the reader is already evaluating
candidates against a known set of needs; lead with what the applicant brings to the role, not
with a researched observation about the employer. Hold the letter to 250-400 words. Formal
salutation and sign-off are required.

Template

Section titled “Template”

See the Cover Letter template.

Section titled “Related”

Pairs well with

Section titled “Pairs well with”

Senior Consultant, Direct Communicator, Confident, Diplomatic, Problem-Solution

Avoid with

Section titled “Avoid with”

Confessional, Reverent, Playful

Often confused with

Section titled “Often confused with”

Cold Outreach

Examples

Section titled “Examples”

Jordan Ellis jordan.ellis@example.com | (555) 555-0142 | Seattle, WA July 13, 2026

Alderwood Systems

Dear Hiring Team,

I’m writing to apply for the Director of Engineering role at Alderwood Systems. Your posting asks for someone who can keep a fast-growing, multi-timezone organization coordinated without letting process outgrow the team, and that is the exact problem I solved as engineering manager for an 11-person team spread across four time zones at Fernbridge Software.

When that team grew from 6 to 11 engineers over 18 months, our daily 9am Pacific standup stopped working: it landed at 9:30pm for our India-based engineers, whose attendance had fallen to 3.2 of 5 sessions a week against 4.6 for our US-based engineers, and the meeting itself produced about 4 minutes of decision-relevant content inside every 14-minute call. I replaced it with a three-field async update posted to a shared channel by 10am local time, backed by a single weekly working session held only when something actually needed real-time discussion. Inside the first two weeks, on-time posting rose from 78 percent to 85.5 percent, the median time from a flagged blocker to a substantive reply fell to 18 minutes, and our India-based engineers posted every weekday for the first time in the team’s history.

The role also calls for practices that outlast any one manager’s attention. I wrote the change up as a formal ADR and a process README specifically so a new hire could run the format without me in the room, and the roughly 70 minutes per engineer per week it recovered is the kind of number that only holds up if the system keeps working after I stop watching it. That is the habit I would bring to setting direction across several teams instead of one.

I would welcome the opportunity to discuss how this experience applies to the Director of Engineering role in an interview this week.

Sincerely, Jordan Ellis