Cover letters were declared dead approximately once per year from 2015 to 2023. They are not dead. Most hiring managers still read them, many read them before the resume, and a strong one can rescue an application that isn't perfect on paper.
The problem isn't the format. It's that most cover letters are bad: generic, formal to the point of sterility, and structurally identical to thousands of others in the same applicant pool. Here's how to write one that isn't.
What a cover letter is actually for
It's not a resume summary. It's not a list of skills. It's an answer to one question:
Why should we hire you for this specific role at this specific company, and why do you want it?
Hiring managers use cover letters to understand motivation, context, and how a candidate thinks about their own experience. The resume shows what you did. The cover letter explains why it matters here.
Structure: 4 paragraphs, 300–450 words
Keep it to one page. Hiring managers scan quickly and most read cover letters in under a minute on the first pass.
Paragraph 1: The hook
Don't open with "I am writing to express my interest in..." That phrase has been written millions of times and signals zero effort.
Open with a specific observation about the company, a direct statement of your most relevant credential, or a connection between their stated need and your actual experience.
Weak:
"I am writing to apply for the Product Manager position at Linear. I have 5 years of product management experience and believe I would be a great fit for your team."
Strong:
"Linear's decision to build for individual contributors first, letting enterprise adoption follow from the bottom up, is the kind of product philosophy I've been arguing for at every company I've worked at. I'm applying for the PM role because I want to work somewhere that already believes it."
The difference is specificity and a point of view. You've demonstrated that you know the company, and you've given them a reason to keep reading.
Strong (SWE version):
"Stripe's approach to API design (treating developer experience as a first-class product concern) is the reason I've spent the last four years as a backend engineer obsessing over latency, error surfaces, and documentation quality. I'm applying for the software engineer role because it's the right place to do that work at scale."
Paragraph 2: Your most relevant experience
Pick 2–3 accomplishments that map directly to what the job description asks for. Use numbers. This is not a resume recap. It's a curated argument for why you're right for this specific role.
Format: claim, evidence, relevance.
"In my last role, I led a team of 8 to ship a core data infrastructure overhaul that reduced query latency by 70% for 400,000 daily active users. We shipped on time, with zero critical incidents post-launch. Your job description calls out 'reliability and performance at scale'. That's the specific problem I've been solving."
"I've built content programs that generate pipeline, not just traffic. At [Company], I grew organic from 12,000 to 110,000 monthly visitors in 16 months and drove 28% of inbound revenue from content alone. The growth motion your job description describes is one I've run."
Paragraph 3: Why this company
This is where most cover letters fail. "I admire your mission and culture" tells the hiring manager nothing except that you didn't research the company.
Instead, cite something specific: a product decision, a public announcement, something a founder or exec said, a business challenge you know they face, or why this role at this company beats a similar role at a competitor.
"What drew me specifically to Figma isn't the scale. It's the recent push to make collaborative design a default rather than a feature. That's a fundamentally different product problem than what most design tools are solving, and it's the kind of framing I want to be working inside."
If you can't write a specific paragraph about this company, that's a signal. Either do the research or reconsider whether you actually want the role.
Paragraph 4: Close
Short. Don't grovel. Express genuine interest and invite next steps.
"I've attached my resume and would welcome the chance to discuss how my background maps to what you're building. Happy to make myself available whenever works."
Format
- Length: 300–450 words
- File format: PDF (not Word; formatting shifts)
- Font: Same as your resume, 10–12pt
- Greeting: "Dear [Name]," if you can find it. "Dear Hiring Manager," otherwise. Never "To Whom It May Concern."
- Header: Your name, email, phone, LinkedIn, matching your resume
To find the hiring manager's name: search LinkedIn for the company + role title, check the company's team page, or look at who posted the job. If you can find a name, use it.
Tone by context
In tech and product roles, write the way you talk to a colleague: clear, direct, no filler. The cover letter that reads like an actual human wrote it stands out immediately in a pool of templated submissions.
In finance, law, and consulting, be more formal. These industries still read formality as signal. Quantify everything; personality takes a back seat to precision.
In startups, especially early-stage ones, show that you understand the stage. Reference the product. Demonstrate that you've thought about the specific problems they're working on. Founders read cover letters differently than HR teams do.
What kills a cover letter
Starting with "I am writing to apply...": every hiring manager has read this 10,000 times. Write something real instead.
Restating your resume bullet by bullet. The cover letter contextualizes; it doesn't repeat. If your cover letter can be replaced with "see attached resume," it's not doing anything.
No company-specific detail. If you could swap the company name and send the same letter to 20 places, you're batch-applying with no real interest in any of them. Hiring managers can tell.
No numbers. "Improved team performance" means nothing. "Reduced deployment time from 40 minutes to 8 minutes" is specific and memorable.
Longer than one page. Anything over 450 words is asking too much of someone who has 200 applications in their queue.
Reading like AI wrote it. If your letter is full of "I am deeply passionate about," "I thrive in fast-paced environments," and three-sentence clauses separated by semicolons, rewrite it. Read it out loud. If you'd never say it in a conversation, don't put it in your letter.
Before and after
Before (generic):
"I am writing to apply for the Product Manager position. I have 6 years of product management experience and am skilled in agile methodologies, stakeholder management, and data analysis. I am very excited about this opportunity and believe my skills would make me a great asset to your team."
After (specific):
"Your recent launch of [Feature], particularly the decision to ship a limited version to enterprise accounts first, is the kind of disciplined sequencing I've been practicing for three years. I'm applying for the PM role because I want to bring that same rigor to a product that's growing faster than it was.
In my last role, I led a cross-functional team of 11 to ship a core infrastructure overhaul affecting 800,000 active users. We shipped on time, with zero critical incidents, and improved system reliability from 99.1% to 99.8%. The platform stability work your job description calls out in Q4 is exactly where I've spent the last two years."
Checklist before you submit
- Opens with something other than "I am writing to apply..."
- Includes at least one specific company or product reference
- At least one metric or measurable outcome in paragraph 2
- 300–450 words total
- Submitted as PDF
- Greeting uses a real name if you could find one
- Read aloud. Does it sound like a human wrote it?
- No typos, especially in the company name
When you're applying at volume
Writing a tailored cover letter for every application is the gold standard, but it's time-intensive at scale. Some candidates use AI to draft and personalize at volume, which works if edited carefully (see the guide on whether employers can tell).
Job Agent handles the application submission layer automatically (direct company job boards), so your writing energy goes to the roles you're most excited about rather than form-filling.