10 min read
Open the posting, highlight two must-have skills, one team line, and one metric from your resume. Those four highlights become four short paragraphs. That's the cover letter from job description step-by-step method. You're not writing your life story. You're showing a recruiter you read the same sections they did before they opened your file.
Most cover letters fail because they're generic essays pasted into every portal. Before you draft, check your resume for free against the posting. If your top bullet doesn't prove a must-have yet, fix the resume first. The letter should point at proof that's already on page one.
Job searching is stressful enough without rewriting the same paragraph twelve times a night. This page gives you the four-line skeleton, where each line maps on the job description, the exceptions that still need a letter, and what to send when the portal only gives you a text box.
If you'd rather start from a blank page with the posting pasted in, generate a cover letter and then swap in your proof bullet from line three below. The skeleton still applies. You're just skipping the empty Google Doc stare.
Quick Wins
- Highlight must-haves, team context, and one metric before you write.
- Four paragraphs only: skills, team, proof, close.
- Use the posting's exact skill names, not synonyms they didn't use.
- Save one PDF named LastName_Role_CoverLetter.pdf.
Why a generic cover letter gets skipped in Greenhouse
Recruiters open cover letters when the resume is close and they need a tie-breaker. They close them fast when paragraph one could apply to any company in the industry.
The symptom is the same on every bad file. Dear Hiring Manager, I am excited to apply for your open position. I am a hard worker with excellent communication skills. That tells them you didn't read the req. It also tells them you might not read the job once you're hired.
A mid-level marketing coordinator sends a letter about passion for innovation. The posting asked for HubSpot workflows, SQL for campaign reporting, and experience supporting a demand-gen team of six. None of those words appear in the letter. The resume might list HubSpot. The letter didn't connect the dots.
Another pattern: the letter repeats the resume summary word for word. Recruiters already have the resume. They wanted one new proof point or one line that shows you understand who you'd report to.
Cover letters aren't magic keywords. They're evidence you mapped the posting to your background on purpose. When the field is optional, that's exactly why a tight four-line letter wins over silence or a novel.
For openings that still feel stuck, read how to start a cover letter after you draft line one here. This page is the structure. That page is the first sentence when you're blank.
Cover letter from job description step-by-step: the four-line skeleton
Pull the job description into a doc or print it. Highlight in three colors: yellow for must-have skills, blue for team or department context, green for one result on your resume that proves a yellow highlight. Those colors become lines one through three. Line four is always the close.
Line 1: Name two must-haves from the requirements block
Find the section labeled Requirements, Qualifications, or What You'll Bring. Pick the two skills that appear earliest and that you actually have. Line one says you're applying for [exact title] and you match [skill A] and [skill B] from the posting.
Before: I am applying for the Analyst role and I have many relevant skills.
After: I'm applying for the Revenue Operations Analyst role at Northwind. Your posting asks for Salesforce reporting and SQL for pipeline dashboards. That's been the core of my last two roles.
Don't list six skills. Two proves you read the top of the req. Save the rest for the resume bullets.
Line 2: Mirror team context from the about-the-team paragraph
Most postings have a line about the team, the manager, or the mission. Quote the structure, not the marketing adjectives. If they say you'd join a four-person demand-gen team supporting enterprise sales, say that back in plain English.
Before: I love working in fast-paced collaborative environments.
After: Your note that this role sits on a four-person demand-gen team supporting enterprise AEs tells me the job is half campaign ops and half sales partnership. That's the split I've been working in for the last year.
If the posting has no team paragraph, use the department name and one product line from the company section. Something specific beats something inspirational.
Line 3: One proof bullet tied to a must-have
Line three is one accomplishment with a system name and a number. It must prove one of the skills you named in line one. Pull from your resume, but rewrite the angle so it isn't a copy-paste.
Before: I have strong experience with data and reports.
After: At my current company I built weekly HubSpot funnel reports in SQL that cut manual spreadsheet work from six hours to forty-five minutes and gave sales managers same-day pipeline visibility.
Edge case: you're light on one must-have. Name the adjacent skill you do have and say you're building the gap. Don't claim the skill outright. Recruiters phone-screen the gap anyway.
Line 4: Close with availability and one ask
Line four is three sentences max. Thank them, state your availability for a call this week or next, and invite them to review your attached resume. No pleading, no salary, no links to portfolios unless the posting asked.
Before: I hope you'll consider me for this amazing opportunity. I promise I won't let you down.
After: Thanks for reviewing my application. I'm free for a 20-minute call Tuesday or Thursday after 2 p.m. ET. My resume is attached with the same HubSpot and SQL examples above.
Copy-paste block: four-line skeleton
{`I'm applying for the [Exact Job Title] role at [Company]. Your posting emphasizes [Must-have 1] and [Must-have 2], which I've used in [context from last role]. Your description of [team name / team size / who you'd support] matches how I've worked recently: [one plain sentence tying your experience to their team setup]. At [Current or Recent Employer], I [action verb] [system or task] that [metric or outcome], which maps directly to [must-have from line one]. Thank you for your time. I'm available for a brief call [two specific windows]. My resume is attached with additional detail.`}
Swap bracket lines in order. Read it aloud once. If any sentence could fit another company, rewrite that sentence until it can't.
Worked example: operations role
Posting must-haves: NetSuite inventory, vendor PO workflow, cycle counts. Team line: three-person ops team supporting two retail locations. Proof on resume: cut stockouts 11% in Q3 after weekly cycle count cadence.
Line one names NetSuite and vendor POs. Line two mentions the three-person ops team and two locations. Line three gives the cycle count story with the 11% figure inside the bullet illustration. Line four offers Thursday or Friday mornings. Total word count stays under 220.
Edge case: the portal strips formatting and limits characters. Paste plain text with blank lines between the four paragraphs. Remove smart quotes. Same four blocks, fewer words in line two.
Edge case: posting requires a cover letter question such as why this company. Add one sentence between line two and line three answering only that question. Don't turn it into a fifth paragraph of fluff.
Edge case: you're switching industries and none of the must-haves match your old title. Line one names the transferable skill the posting lists first, such as stakeholder management or SQL, and line three proves that skill in the old industry. Don't pretend you already did the new industry's work.
Edge case: the posting lists must-haves as nice-to-have and preferred. Lead line one with the required block only. Preferred skills can appear in line three if you have proof. Required beats preferred when space is tight.
Before you export, search the letter for the words passionate, excited, and opportunity. Delete two of the three if they appear. Recruiters aren't grading enthusiasm. They're checking whether you read the req carefully.
Save the file as LastName_Role_CoverLetter.pdf so HR can find it when your resume is already in the queue.
Openings that waste the upload field
Starting with your degree when the posting didn't ask for education. Line one should be must-haves, not graduation year. Education belongs on the resume unless the letter prompt demands it.
Quoting the company's mission statement back to them. They wrote it. They know. Team context from the req beats values language from the careers page.
Apologizing for a gap or a career change in paragraph one. If you need to address a gap, line three can show recent relevant work. Save the gap talk for the recruiter call if they ask.
Attaching a letter that names the wrong company. Search the PDF for the last company you applied to before you upload. Wrong-name letters end reviews faster than weak ones.
Using a two-column template or a header graphic. Many parsers read cover letter attachments as plain text. Tables turn into garbage lines. One column, 11-point Calibri or Arial, margins default.
For interview-stage alignment after the letter works, see behavioral interview answers that don't sound rehearsed . The letter gets you read. The screen proves line three wasn't fiction.
Match the resume and letter before you upload
Run the same posting through the free ATS checker with your resume file. You're confirming the must-haves in line one actually appear in your experience section, not chasing a score.
Then open the cover letter generator with the posting pasted in. Drop your line-three proof bullet into the body field. Generate once, edit line two by hand, export PDF. Don't regenerate five times hoping for magic wording.
What to do in the next twenty minutes
Cover letter from job description step-by-step isn't a creative writing exercise. Highlight must-haves, team context, and one metric. Write four paragraphs. Read once for wrong company names.
Send the letter only when line three proves something line one claimed. If it doesn't, fix the resume bullet first, then draft the letter. That order saves you from defending an empty claim on a phone screen.
Save the final PDF with the role in the filename. Upload it with the same resume version you checked. Small consistency details are what separate files that get a full read from files that get ten seconds.
Read more
Frequently asked questions
When the posting lists cover letter as optional and you meet the must-haves on paper, a short four-line letter still helps on tie-breaker files. Skip it only when the portal has no upload field and the posting says not to send one. Never paste the letter into a comments box that truncates at 500 characters.
Mirror the skill names and team labels the posting uses, but write full sentences in your voice. Pasting bullet text from the req reads like mail merge. The goal is to show you read the same sections a recruiter highlighted, not to match keyword density.
Repeat the skill, not the sentence. Line three should prove one must-have with a different angle than bullet one on your resume. If both say the same Salesforce report story word for word, the letter adds nothing and recruiters skip it.
Four short paragraphs or about 180 to 250 words total. Line one names two must-haves. Line two names team context. Line three is one proof bullet. Line four closes with availability. Longer letters get skimmed in Greenhouse when forty similar files arrived that morning.
Many US portals store the cover letter as a separate text field or attachment. Some parsers index keywords from it; others ignore it until a human opens the packet. Write for the human reader first. Plain text, standard fonts, no tables or text boxes.
