Cover Letter

Cover Letter

Overview

This skill produces tailored, compelling cover letters that pass ATS screening and give hiring managers a reason to schedule an interview. It applies a proven four-part structure—opening hook, skills match, company research signal, and CTA—while avoiding the generic, template-feeling language that fills most cover letters. The result reads like a letter from a person, not a form: specific, confident, and directly responsive to what the job posting asks for.

When to Use

• Applying to a job posting for the first time (cold application)
• Applying through a referral where a cover letter is expected
• Switching careers and needing to explain transferable skills
• Returning to the workforce after a gap
• Applying for a role where you're overqualified or underqualified on paper
• Responding to an internal job posting within your company

When NOT to Use

• Job applications that explicitly say "no cover letter"
• Platforms where a cover letter field isn't provided (many automated ATS systems)
• General professional bios or LinkedIn "About" sections (different format/purpose)
• Academic positions (use an academic cover letter format, which differs significantly from professional ones)

Quick Reference

Instructions

1. Gather the inputs. To write a great cover letter, you need:

   • The full job posting (job title, requirements, company name)
   • The candidate's relevant experience, skills, and accomplishments
   • Any specific context: career change, gap, over/underqualification
   • The hiring manager's name (if known)

2. Address it correctly.

   • Use "Dear [Name]," if you know the hiring manager's name (find it on the job post, LinkedIn, or company website)
   • "Dear Hiring Manager," is acceptable but impersonal
   • Never use "To Whom It May Concern"—it signals zero effort

3. Write the opening hook (paragraph 1). This is not "I am writing to express my interest in the [Role] position." Everyone writes that. Instead:

   • Lead with your strongest relevant credential: "Five years ago I rebuilt a data pipeline from scratch in 36 hours during a product launch crisis—it's the kind of pressure I've realized I thrive in. That instinct is exactly what your Senior Data Engineer role asks for."
   • Reference a specific company achievement or product: "When Ramp released its spend analytics API last spring, I immediately started building integrations for my finance team's internal tools. That's the kind of problem-solving I'd love to bring inside."
   • State the specific value you bring: "I've grown enterprise partnerships from $0 to $4M ARR at two B2B startups—and your VP of Partnerships role is exactly the stage where that experience matters most."

4. Match your skills to their requirements (paragraph 2–3). Go through the job description and identify the top 2–3 requirements. Write a paragraph that connects your past experience to each:

   • Be specific about results, not just responsibilities
   • Use numbers wherever possible: "increased retention by 22%," "managed a team of 8," "reduced infrastructure costs by $40K/year"
   • Mirror the language of the job posting (for ATS keyword matching)

5. Show company research (paragraph 3 or 4). One focused paragraph that signals you researched this specific company:

   • Reference a recent news story, product launch, or initiative
   • Name something specific about their culture, values, or approach
   • Connect it to why you want to be there specifically—not just "it seems like a great place to work"

6. Write the CTA (closing paragraph). Express genuine enthusiasm and ask directly for the next step:

   • "I'd welcome the chance to talk through how my background fits what you're building."
   • "I'm excited about this role and would love to discuss it further—I'm available for a call anytime this week."
   • Avoid: "I hope to hear from you" (passive), "Please find my resume attached" (obvious)

7. ATS considerations. Many companies use Applicant Tracking Systems to screen cover letters:

   • Include the exact job title as it appears in the posting
   • Mirror key phrases from the job description naturally (not as a word dump)
   • Use standard section formatting; avoid tables or graphics
   • Save as PDF unless the application requires .docx

8. Final check before sending:

   • Correct company name (not the company you applied to yesterday)
   • Correct job title
   • Correct hiring manager name (if used)
   • No "I" as the first word of a paragraph (stylistic, signals self-focus)
   • One specific reason why this company, not just this role

Examples

Example 1: Software Engineer Cover Letter

Input: "Write a cover letter for a Senior Frontend Engineer role at Vercel. The job requires React expertise, TypeScript, performance optimization experience, and ideally open source contributions. I have 6 years of React experience, contributed to the React Testing Library project, led a Lighthouse score improvement from 38 to 94 at my last company, and I genuinely love and use Vercel's product."

Output:

Dear Hiring Team,

I've deployed my last four projects on Vercel—not because it was the default, but because every time I try to switch I end up switching back. When I saw you were hiring a Senior Frontend Engineer, it felt less like a job application and more like asking to join something I'm already part of.

I bring six years of React experience and a deep focus on the part of the stack that users actually feel: performance. At Wander (my most recent role), I led a six-month initiative to address critical rendering and asset delivery issues that had driven our Lighthouse score to 38. By the time I handed it off, we were at 94. The work spanned Core Web Vitals optimization, code splitting strategy, image pipeline refactoring, and a migration from a legacy CSS architecture that was contributing significant render-blocking time. It was the most technically satisfying project of my career.

On the TypeScript side, I've written production TypeScript for four years and have contributed to React Testing Library—which has given me a ground-level understanding of how framework design decisions ripple into developer experience. It's shaped how I think about component APIs and documentation, and I imagine that kind of lens would be useful inside Vercel.

What draws me to this role specifically is the chance to work on tooling that shapes how a generation of developers builds. Vercel's influence on the web platform isn't incidental—it's deliberate, and I want to be part of that deliberateness.

I'd love to talk through this further. I'm available any time this week.

Jamie Chen

Why it works:

• Opens with a specific, personal relationship to the product—not "I'm passionate about frontend development"
• Performance win (38 → 94 Lighthouse score) is specific and impressive
• Open source contribution signals community engagement—mirrors the job requirement
• Company research paragraph is authentic: "deliberateness" reflects Vercel's actual brand positioning
• CTA is direct, not deferential

Example 2: Career Changer Cover Letter

Input: "Write a cover letter for a UX Research role. I'm coming from 7 years in clinical psychology (therapist), pivoting to UX. I have no formal UX experience, but I've done a UX certification, conducted 40+ user interviews for a volunteer project, and my psych background means I'm extremely skilled at interviewing, behavioral analysis, and identifying unspoken needs."

Output:

Dear [Hiring Manager's Name],

For seven years, my job was to sit with someone who couldn't tell me what was wrong and figure out what was wrong. As a clinical psychologist, that meant learning to distinguish between what people say, what they mean, and what they actually need—often in a single session. I've since realized that's exactly what UX researchers do.

I transitioned intentionally. After completing the Google UX Research Professional Certificate, I conducted 40+ user interviews for Literacy Lab, a nonprofit building reading tools for adult learners. I designed the research protocol, recruited participants, ran moderated sessions, synthesized findings into affinity diagrams, and presented recommendations that shaped two major product pivots. The skills weren't borrowed from psychology—they were the same skills, applied to a different problem space.

Clinical training gives me things most early-career UX researchers are still developing: comfort with silence in interviews, the ability to detect inconsistency between stated and revealed preferences, and experience writing clinical summaries that distill complex behavioral data into actionable insights. I also have a specific sensitivity to accessibility and cognitive load that comes from working professionally with people who process information differently.

I've followed [Company]'s research into [specific project or initiative], and the way your team approaches [specific research challenge] is exactly the kind of work I want to contribute to. I'm particularly drawn to the emphasis on longitudinal research—an approach I believe leads to insights that one-off usability studies can't surface.

I'd welcome the opportunity to talk through how my background fits your needs. Thank you for considering a non-traditional path.

[Name]

Why it works:

• Opens with a strong analogy that reframes the "no UX experience" liability as an asset
• Specific project with specific output (40+ interviews, two product pivots) demonstrates credibility
• Addresses the career change concern proactively—confident, not apologetic
• Company research placeholder shows where to insert specific detail
• Closes without over-apologizing for the non-traditional background

Best Practices

• Customize the company research paragraph for every application—it's the only paragraph that can't be templated
• Quantify accomplishments wherever possible: hiring managers see hundreds of letters claiming "strong results"
• Match energy: if the job posting uses casual language and emoji, a very formal cover letter will feel like a mismatch
• One page, always—cutting to fit is part of the discipline
• Read it from the hiring manager's perspective: what question does this answer, and does it make them want to meet you?

Common Mistakes

• Generic opening: "I am excited to apply for the [Role] at [Company]. I believe my skills and experience make me an excellent candidate." This gets skimmed past in seconds.
• Summarizing the resume: The cover letter should add context and personality, not repeat what's already in the resume
• Underselling or over-apologizing: "Although I don't have direct experience in X, I believe I could learn it quickly." Reframe: what DO you have?
• Failure to name the company specifically: Hiring managers can tell when a letter was written once and sent 50 times
• Wrong name or title: Addressing the wrong company or role is an instant disqualifier at many firms

Tips & Tricks

• Use the job description's exact language for skills/tools (ATS keyword matching)
• If you don't know the hiring manager's name, spend 5 minutes on LinkedIn before defaulting to "Hiring Manager"
• Save a master version with notes on what to customize per application to save time
• For competitive roles at recognizable companies, open with something specific about the company—they get thousands of "I've always admired [Company]" letters
• A referral should be named in the first sentence: "Jamie Rodriguez suggested I reach out about the Product Design role"
• Ask someone outside your field to read it—if they find it boring, a hiring manager will too

Related Skills

• email-drafter
• proofreader
• storyteller