Write a Cover Letter From a Job Description

9 min read

Most cover letters fail before paragraph two because they're written from a template, not from the posting open on the second monitor. You're not summarizing your career. You're answering three questions the hiring manager already asked in paragraph one of the req.

If you can't tie a posting phrase to a dated bullet on your resume, don't fake it in the letter. Fix the resume first or pick a different req. The letter isn't a second chance to invent scope.

Check your resume for free against the same PDF before you draft. When bullet one already mirrors the posting, the letter writes itself in twenty minutes.

Generate a cover letter skeleton after step four if you want a clean docx, then rewrite every sentence until it sounds like you on a call.

What a job description gives your cover letter

The posting is a priority stack, not a wish list to copy. Paragraph one usually states outcomes. The bullets underneath name tools, audiences, and cadence. Your letter should echo that order: outcome first, proof second, polite close third.

Required versus preferred lines tell you what to lead with. If you miss a required license, the letter won't save the apply. If you only miss a preferred tool, paragraph two is where you show adjacent proof without overstating.

Tone matters. A formal government req wants full titles and no slang. A startup req still wants specifics, not hype. Read two employee-written posts on the company site if you need one detail for paragraph three that isn't in the posting.

Cover letters ride alongside resumes in most ATS folders. Recruiters search both. That doesn't mean keyword stuffing. It means the same tool names and scope phrases appear in both files without contradiction. See how ATS screens cover letters for what gets stored as text.

Split the posting into must-have, nice-to-have, and culture lines on a scratch page. Must-haves earn paragraph one and two. Nice-to-haves earn one clause if you have proof. Culture lines earn one specific detail in paragraph three, not flattery.

Acronyms follow the posting spelling. If they write PMO, you write PMO in the letter when describing the same program office work from your resume. Don't introduce a different acronym family unless you expand once for clarity.

Government and contractor reqs sometimes cap letter length in the instructions. When they give a word max, hit ninety percent of it with proof, not filler. Missing the cap looks like you didn't read the req.

Six steps to write a cover letter from a job description

Work one posting tonight. Don't batch five letters with the same opener. When you finish, read the letter backward sentence by sentence to catch duplicated company names from an earlier draft.

1. Save and highlight. Export the req PDF. Highlight three must-have nouns from paragraph one and the first bullet block. Write them in a scratch file with the exact spelling the employer used.
2. Map to resume bullets. For each highlight, find one Experience bullet with dates. If none exists, add the bullet to the resume before you write the letter.
3. Draft paragraph one. Sentence one names role and company. Sentence two states one metric or scope line from your mapped bullet using the posting's tool name.
4. Draft paragraph two. Take the second must-have. Tie it to a different job block. Keep verbs active and numbers identical to the resume.
5. Draft paragraph three. One sentence on why this team or product, one sentence on start timing, one sentence inviting next steps. No generic passion paragraphs.
6. Read aloud and cut. If a sentence could fit any employer, delete it. If a claim isn't on the resume, delete it. Save as PDF with the same font family as the resume.

Before: Opening says I am excited to apply and lists five skills with no employer proof.
After: Opening names Customer Success Manager at Northwind, cites one renewal metric from your resume bullet tied to Salesforce.

Before: Paragraph two pastes three lines from the job description in quotation marks.
After: Paragraph two describes how you ran weekly business reviews for twelve accounts using the same cadence the posting mentions, with one outcome illustration from your file.

Copy-paste cover letter skeleton

{`Dear [Hiring team or name],

I'm applying for [exact title] at [Company]. In my [recent role], I [verb] [posting tool] for [scope from resume bullet] with [metric that matches resume].

Your posting emphasizes [second must-have]. At [Employer], I [one sentence proof with same numbers as resume].

[One specific detail about team/product]. I'm available [start window] and welcome a conversation about [one outcome from posting].

Sincerely,
[Name]`}
            

I've passed on letters that sounded polished until I cross-checked numbers against the resume and found mismatched percentages. Fix the resume first, then paste metrics into the letter verbatim.

For opener formulas when you're stuck on sentence one, read how to start a cover letter . For matching language on the resume side, see how ATS matches resumes to job descriptions .

Paragraph-by-paragraph checklist

Paragraph one must answer why this role at this company tonight, not why you need a job. Paragraph two must answer which posting requirement you already handled elsewhere. Paragraph three must answer what happens next without begging.

Greeting line: use a named recruiter from the posting footer when it's public. When the req says hiring team only, write Dear Product Analytics Hiring Team instead of To Whom It May Concern unless the employer is extremely formal.

Before: Letter opens with three adjectives about yourself and no company name.
After: Letter opens with exact title, company, and one metric pulled from bullet one on the resume PDF.

Before: Closing says I hope you'll consider my application.
After: Closing confirms you're available to start in the window on the offer or posting and welcome a short call about the team's Q4 priority named in the req.

Save the letter with the same file naming pattern as the resume: Firstname_Lastname_CoverLetter_Company.pdf. Recruiters search folders quickly when attachments are consistent.

When the portal has a plain text box instead of upload, paste without fancy bullets. Strip tabs and extra spaces so the stored text matches what you proofread in Word.

Re-read the posting footer for work authorization or clearance lines. If the req asks you to confirm eligibility, add one factual sentence in paragraph three instead of ignoring the instruction.

Optional fourth paragraph belongs only when the posting asks for relocation, clearance, or work authorization details you didn't cover in the form. Keep it to two sentences.

Cover letter mistakes tied to job descriptions

• Pasting the posting: parsers and humans both flag block quotes from the req.
• Leading with what you want to learn: lead with what you already did that matches their first bullet.
• Different numbers than the resume: reference checks start with the letter on the desk.
• Two pages: if you need two pages, you're repeating the resume. Cut to three paragraphs.
• Wrong company name: mail-merge errors end the read in sentence one.
• Attaching the wrong PDF: double-check the filename before upload; recruiters open the letter first on some teams.

Before: Letter mentions HubSpot while resume only shows Salesforce.
After: Letter and resume both name Salesforce for the same campaign work, or you add HubSpot honestly to the resume before you send.

Salary and level lines from the posting rarely belong in the letter unless you're confirming you understand the band. Don't negotiate pay in the cover letter file; save that for the offer thread after they choose you.

Use tools after the draft, not instead of reading

Run match on the resume against the saved posting first. When highlights sit under Experience, draft the letter from those same lines. A letter won't fix skills that only live in a sidebar list.

Run a job match score on the req, then generate a cover letter outline if you want structure. Rewrite every line before you upload beside the resume PDF.

Read the letter on your phone before submit. If a line wraps awkwardly or the greeting looks like a typo, fix it. Many portals don't preview cover uploads the way they preview profile fields.

Send one letter tonight

A cover letter from a job description isn't a creative writing exercise. It's three answers to what they already said they need, backed by the same numbers on your resume. Highlight three phrases, map them, draft three paragraphs, read aloud, upload with the PDF you checked.

Keep a folder per company with the saved req PDF, your resume version, and the letter draft. When a recruiter replies, you'll know exactly which file they read without guessing which template you sent.

If you're out of time, skip the letter only when the portal marks it optional and your resume already mirrors paragraph one. When the field is required, send the short version above instead of an empty upload.

Batch similar reqs on one evening, not one letter for all industries. A fintech ops letter shouldn't reuse sentences from a healthcare admin posting even when your resume bullets overlap.

Set a twenty-five minute timer for the first draft. Editing passes can run longer, but the first pass should only map three highlights to three paragraphs without polishing every adjective.