How to Write a Cover Letter That Gets Interviews

Every year a thinkpiece tells you cover letters are dead. Every year recruiters tell us they read the good ones. Both are true. A lazy cover letter is ignored. A specific one gets replied to.

This post is about writing the second kind. Not the form letter you can send to fifty companies. The one you write in 45 minutes for a single role, that takes a recruiter three minutes to read, and turns a maybe into a screen.

Cover letters didn't die. Lazy ones did.

The reason "are cover letters required" still ranks every six months is that the honest answer is genuinely both. Most postings don't require one. Most hiring managers still read the one you send. Those facts coexist because the cover letter has changed role: it used to be a check-the-box submission requirement, and it has become an optional but consequential signal a candidate can choose to send.

In recruiter conversations and hiring-manager surveys over the past few years, a consistent pattern shows up. The bar for whether a cover letter helps is whether it adds something the resume can't carry. A letter that restates your resume in prose form is filler the reader resents. A letter that names a specific reason for this company, this role, this moment, is the candidate doing the screening work the recruiter would otherwise have to do themselves.

The practical implication is direct. If two finalists arrive with comparable resumes and one has a cover letter naming something specific about the company while the other has nothing, the one with the letter gets the screen. Cover letters are a filter. They filter out candidates who are spraying applications, which is most of them. The candidate willing to spend 45 focused minutes on one company is, by that act alone, unusual.

That's the version of "still matter" worth taking seriously. Not as a compliance requirement, but as a signal you choose to send when you want a specific outcome.

The three-paragraph structure

Paragraph one: who you are, in one sentence the hiring manager can repeat to their boss. Paragraph two: the specific reason this company, not a competitor, and the work you would do in the first ninety days. Paragraph three: one concrete next step.

That's it. No more.

The structure is short on purpose. A three-paragraph cover letter forces decisions a five-paragraph one lets you avoid. You cannot include both your education and your most relevant project. You cannot list three reasons you're interested in the company and three reasons you're qualified. You have to pick. The picking is the work.

Each paragraph carries one job:

Paragraph one (the credential). Two to three sentences. The role you're applying for, the level you're at, and one concrete claim that establishes you as a serious candidate. Not your resume in miniature. The one fact about your career that, if the reader stops here, would make them want to read paragraph two.

Paragraph two (the why-them, why-now). Three to five sentences. What you noticed about the company: the team, the recent product release, the engineering blog post, the funding round, the new market they entered. Then what you would actually do about it in the first 90 days of the role. This is the hardest paragraph to write because it requires reading the company carefully. It is also the only paragraph the reader cares about.

Paragraph three (the close). One to three sentences. A specific next step you propose. Not "I look forward to hearing from you," which is a closing politeness, not an action. A concrete next step is "I'm in San Francisco the week of May 12th and would welcome a 30-minute call any morning that week" or "I'll plan to follow up next Wednesday if it's helpful, or feel free to reach me at [email]."

Total word count: 250 to 300. Under one page, single-spaced. If yours is longer, you have not finished writing it.

What "specific" actually means

Specific is not "I'm passionate about your mission." Half the cover letters a hiring manager reads include that sentence. The other half use a synonym. Neither half gets a callback for it.

Specific is something the company published or did that you can quote back accurately, paired with a thing you've done that connects to it. "I read your engineering blog post on migrating to Postgres 16 last month and noticed you still do blue/green deploys. I spent the last two years rebuilding deploy infrastructure at a fintech and would welcome a conversation about how we cut cutover time from 40 minutes to six."

Two halves. The first half proves you read the company. The second half proves you have the right kind of experience. Together they prove the application wasn't a copy-paste.

A useful test: could the same sentence appear in another candidate's cover letter for a different company? If yes, the sentence is generic. If no, the sentence is specific. Apply this test to every sentence in paragraph two. The ones that survive go in. The ones that don't get cut and rewritten.

Specific is unfair to candidates who can't be bothered — and the hiring manager treats that unfairness as a leading indicator of how the candidate will behave on the job.

Where to find the specifics

Most candidates fail this section because they look in the wrong places. The "About" page is generic. The investor announcement is generic. The careers landing page is generic. None of these tell you anything the candidate next to you doesn't also know.

The specific lives in:

• The company's engineering or product blog for the last 90 days. Every post is something the team chose to make public. Reference one.
• Recent podcast or conference appearances by people on the team. Founders, heads of engineering, and senior product leaders give long-form interviews. A 60-minute podcast episode contains more useful detail about how the team thinks than a year of marketing copy.
• The company's open-source repos, if they have any. The README of a recently-active repo tells you what the team is working on at a depth the marketing site never reaches.
• Recent feature launches or pricing changes. Releases that weren't tweeted but show up in the changelog.
• The hiring manager's last six months of LinkedIn posts or X presence, if public. Not to compliment them. To understand what's on their mind.

You're looking for one detail you can name, not a thesis. Two minutes of skimming usually surfaces the right one.

A cover letter that worked

What follows is a composite, drawn from three real cover letters that earned interviews at different companies in 2025. Names, roles, and company specifics are anonymized. The structure and the moves are real.

The candidate is a senior backend engineer with seven years of experience, applying to a Series B fintech for a staff engineer role on the payments infrastructure team.

Dear Priya,

I'm a senior backend engineer with seven years of experience building payments infrastructure, most recently at a Series B fintech where I led the rewrite of our settlement pipeline from a synchronous monolith to an event-driven service. I'm writing about your staff engineer role on the payments platform team.

I read your CTO's RailsConf talk last month on why you stayed on Rails through your scaling phase, and I noticed the section on the idempotency-key system your team built to handle retries. I spent the better part of 2024 building something structurally similar at my current company, and the failure modes you mentioned at the 32-minute mark (the dual-write race between the keys table and the transactions table) were exactly what we ran into. We solved it with a deferred-write pattern using outbox tables, and I'd welcome a conversation about whether that fits how your team thinks about consistency.

I'm based in Toronto and travel to NYC every six weeks. If a screen is useful, I'm available any morning between May 8th and May 22nd. You can reach me at [email] or on Signal at [number].

Thanks for reading, Marcus

Now read it again with the editorial commentary.

Paragraph one: the credential. Three things in two sentences. Role: senior backend engineer. Years: seven. Specialty: payments infrastructure. Then one concrete recent project (the settlement pipeline rewrite) that establishes seniority without listing accomplishments. Note what's not here: no list of skills, no GPA, no education, no mention of any other job. The reader has all they need to decide whether the rest is worth reading.

Paragraph two: the why-them. Two sentences setting up the specific (the CTO's RailsConf talk, the idempotency-key section), one sentence with the candidate's parallel experience, one sentence with a concrete technical observation that proves they actually watched the talk and understood it (the 32-minute mark, the dual-write race), and a sentence that turns it into an offer to discuss. The candidate doesn't claim to have the answer. They claim to have done the work and want to compare notes. That's a stronger move than "I can solve this for you" because it respects the team's existing expertise.

Paragraph three: the close. Concrete next step. Specific dates. A second contact channel, since teams often have a preferred one. The signoff is short, no exclamation point, no "I look forward to" hedging. The reader knows exactly what action to take and when.

The full letter is 198 words. It took the candidate about an hour to write, including 30 minutes of watching the RailsConf talk at 1.5x speed.

Four common openings, rewritten

The opening sentence of a cover letter is where most candidates lose the reader. Below are four of the most common opening patterns, each rewritten into something a hiring manager would keep reading.

Pattern 1: the resume restatement

Weak:

I am writing to apply for the Senior Product Manager position posted on your careers page. I have over eight years of experience in product management at companies like Acme and Beta Corp, where I have led cross-functional teams and driven significant business outcomes.

The reader already knows you're applying. The reader can see your job titles on your resume. Nothing in this paragraph would change if the company were different.

Strong:

Your Q1 product update mentioned that you're consolidating your three checkout flows into one. I led the equivalent project at Acme in 2023 (three flows, two engineering teams, eleven months) and I'm writing about the senior PM role on your checkout team.

Same candidate, same facts. The strong version puts the company-specific observation first, paired with one credible parallel project, and only then names the role.

Pattern 2: the passion declaration

Weak:

I have been a passionate fan of your company since I first discovered your products in college. Your mission to democratize access to financial tools deeply resonates with my values, and I would be thrilled to contribute.

Three things wrong: "passionate fan" can apply to anyone, "deeply resonates" is filler, and "I would be thrilled" tells the reader nothing about why you'd be good at the job.

Strong:

I've been a customer of yours for four years and switched my freelance bookkeeping over from QuickBooks in 2023, after the receipt-OCR feature launched. I'm applying for the senior product designer role because I want to work on the part of the product that made me switch.

The candidate proves the relationship is real (length, the specific feature that earned the switch), connects it to a reason to apply, and names the role. No declared passion. No emoting about values. One true sentence about how the product changed how they work.

Pattern 3: the cold-open name-drop

Weak:

I am reaching out at the suggestion of a mutual connection. As a top performer at my current organization with a track record of delivering high-impact projects, I believe I would be an excellent fit for your team.

Vague referral, vague self-praise, vague claim of fit. The reader doesn't know who referred you, what kind of organization you're at, or what kind of fit you'd be.

Strong:

Sara on your data science team suggested I apply. We worked together at LinkedIn from 2019 to 2022, where I led the experimentation platform she used for her ranking work. I'm writing about the staff data engineer role on the experimentation team.

The referral is named, the relationship is dated, the kind of work is identified, and the role is named. A hiring manager can verify every claim in 30 seconds.

Pattern 4: the apology opening

Weak:

Although I do not have direct experience in your industry, I am a fast learner with strong transferable skills, and I am excited to bring a fresh perspective to your team.

Apologizing in the first sentence trains the reader to discount you. "Fast learner" is what people say when they have no examples. "Fresh perspective" is what people say when they don't yet know the work.

Strong:

I'm a clinical pharmacist applying for the product manager role on your medication-adherence team. I spent the last six years counseling the patients you're trying to reach, and I want to apply that knowledge to the design of the product itself rather than to one prescription at a time.

The candidate names the gap (no PM experience), reframes it as the qualification (six years with the actual user), and explains the move in one sentence. No apology. No transferable-skills language. The career change is the reason to hire them, not a problem they're working around.

When the rules bend

The three-paragraph structure works for most applications. A handful of situations call for variants.

No direct experience. If you've never held a role in this industry, paragraph one carries the gap and reframes it. The clinical-pharmacist example above is the move. Don't apologize. Name the gap, name what you have instead, and let paragraph two do the rest. A separate guide for this situation is in How to write a cover letter when you have no experience.

A referral. Lead paragraph one with the referrer's name and your relationship to them. The referral is the strongest sentence you can put first; everything else in the letter benefits from the reader's prior trust in the referrer. A deeper guide is in How to mention a referral in a cover letter.

A career change. Use the structure, but spend more of paragraph two explaining the bridge. The reader needs to see how the old career qualifies you, not be told that it does. Concrete projects from the old career that map onto the new function are doing the work; a sentence about your "transferable skills" is not.

A gap or layoff. Don't bring it up unless it's longer than a year and visible on your resume. If it is visible, one sentence in paragraph one closes it: "After a 14-month parental leave I returned to consulting in late 2024 and am now looking for a full-time role in fintech infrastructure." No apology, no over-explanation. The cover letter doesn't have to defend the gap. It has to acknowledge it and move on.

A senior role with an internal-politics dimension. Director-and-above hiring decisions are usually made by three to five people, not one. Write the letter to the hiring manager but assume it will be circulated. That means: no inside jokes, no presumptions of familiarity, and one paragraph that addresses why you'd be effective in the org's existing political reality, not only in the role's stated scope.

An application through a portal that won't accept a cover letter. Send it anyway. Find the hiring manager on LinkedIn, write a one-paragraph version of the same letter as the connection note, and submit your application through the portal in parallel. Most hiring managers either accept the connection request or reply directly, and the conversation continues outside the portal.

For the broader question of whether a cover letter still belongs on the application at all, the related framing is in Are cover letters required in 2026?, a shorter answer post that stands on its own.

Build once, render everywhere

Most cover letter advice assumes you'll write a fresh document for every application. You should. But you shouldn't be starting from scratch in a Word file every time.

The two slow parts of writing a cover letter are paragraph one (your credential, which barely changes between applications) and the formatting. The fast part is the actual specific paragraph two, the one that should take all your time. The structure of the workflow should reflect that.

A practical setup: keep one cover letter source document with paragraph one written, paragraph three written, and paragraph two as a placeholder. For each application, rewrite paragraph two from scratch and adjust the role name in paragraph one. The total time per cover letter drops from 90 minutes to 45, and the time savings go entirely into research, where they belong.

If your cover letter and your resume live in two separate files in two separate apps, every update has to happen twice. The job title in paragraph one of your cover letter has to match the title at the top of your resume. The contact info has to match. The dates of your most recent role have to match. Maintaining four documents (resume PDF, cover letter PDF, LinkedIn, personal page) without drift is a discipline most people lose within three months of a job search.

The 2026 fix is the same one we wrote about for the resume. Build your career documents once and render them where you need them. Your professional page can host your resume and your cover letter alongside the rest of your career story, all served from one URL. When the recruiter clicks the URL on your application, they land on a page that includes the same cover letter you submitted, only readable on a phone, with your other context one scroll away. The cover letter does the work of opening the door; the page does the work of closing the deal.

ProPage builds career documents (resume, cover letter, hub page) on a single data model. Update your most recent role once and every document refreshes. Export the cover letter as a clean PDF for the application portal. Share the URL for everyone else.

For the resume side of this, see How to Write a Resume in 2026. For the broader argument that the URL is the artifact, see What is a professional identity URL. For the parser-side question that decides whether your application is read at all, see ATS resume: how to beat applicant tracking systems.

What not to do

A short list of moves that consistently hurt cover letters more than they help. Some are obvious; some come up often enough to keep restating.

• Don't restate your resume. The reader has it open in another tab.
• Don't write "To whom it may concern." Find a name. If you can't, "Dear Hiring Manager" is the second-best move; addressing the team ("Dear Payments Platform team") is a defensible third.
• Don't use "utilize" where "use" would work. Same goes for leverage, navigate, drive, empower, unlock, and the rest of the LinkedIn-thought-leadership vocabulary. Plain verbs read as confident.
• Don't claim you've been "a fan since day one" of a company founded in 2009. Specificity-theater that the reader sees through immediately.
• Don't write more than one page. A two-page cover letter is a tell that the candidate didn't decide what mattered. The recruiter reads page one and decides.
• Don't open with your name. Your name is in the signature, the email, and the resume. The opening sentence is the most expensive real estate in the document; spend it on something the reader doesn't already know.
• Don't address salary unless the posting requires it. A cover letter is the wrong place. If the posting requires it, give a range and move on. Don't bargain.
• Don't reuse the same cover letter twice without rewriting paragraph two. The reader can tell.
• Don't sign off with "I look forward to hearing from you." Replace with a concrete next step. The reader will follow up if you've given them a reason to.
• Don't attach a third document. Cover letter and resume. Nothing else. A portfolio URL belongs in the resume header or the email body, not as a third file.

A cover letter is 250 words a hiring manager doesn't have to read. When they do, it's because the first sentence earned the next one. The work of writing a good cover letter is the work of making each sentence earn the one after it.

Open one company, read for fifteen minutes, write one paragraph. The rest is structure.