A job description is a draft. It was written by a hiring manager who was busy, edited by a recruiter who has fifteen open roles, padded by a legal team, and posted by an applicant tracking system that strips formatting on the way through. By the time it lands on a careers page it reads as a single confident document, but it isn't one. It's a stack of competing intentions that nobody had time to reconcile.
The mistake most candidates make is reading it as if it were finished. They mirror every bullet, echo every phrase, treat every "preferred qualification" as a hard gate. The result is a resume that reads as a translation of the JD back into the JD's own voice, which is exactly the document the reader cannot use, because they wrote it and they already know what it says.
The move is to read the JD the way an editor reads a draft. Skeptically. Looking for the two or three claims that matter and the surrounding text that's there because someone had to fill space.
What's actually load-bearing
Most JDs have a real shape underneath the noise. Usually three or four things that the role is genuinely about, and the rest is scaffolding. Your job on the first read is to find the load-bearing parts.
The signal is repetition. If a phrase shows up in the title, the first paragraph, the responsibilities, and the qualifications, it's load-bearing. The hiring manager wrote it, the recruiter kept it, and nobody on the chain felt the need to soften it. That phrase is what the role is about. Everything that appears once, in one section, is decoration until proven otherwise.
The other signal is specificity. Generic verbs ("collaborate," "drive," "own") are filler. Specific nouns and numbers ("the billing platform," "a team of eight," "a 99.95% SLA," "the EMEA region") are the real description. Specific lines tell you what the work is. Generic lines tell you the JD was written quickly.
The three lists you actually need
After the first read, sit with the JD and pull out three short lists. Not in your head, written down, somewhere you can look at them next to the resume.
The first list is the two or three repeated load-bearing phrases. Usually a domain ("payments infrastructure," "lifecycle marketing," "regulated healthcare data"), a scale signal ("series B," "global rollout," "first hire on the team"), and a stance ("greenfield build," "platform consolidation," "turnaround"). Three is the maximum. If you have five, you haven't decided yet.
The second list is the specific nouns. The actual systems, regions, customer types, regulatory regimes, languages, frameworks. These are what your bullets will need to mirror, not in vocabulary, but in concreteness. If the JD names a specific system and your bullets only name categories, you read as one level less concrete than the role.
The third list is the verbs the JD uses for the work. Not adjectives, not soft skills, verbs. Migrated, scaled, closed, shipped, designed, recovered, hired, sunset. These are the verbs your bullets should be using when the underlying work supports it. Borrow the verb when it's honest; don't borrow it when it isn't.
What to ignore
A surprising amount of any JD can be ignored without cost. The "about us" paragraph at the top is usually marketing copy and tells you nothing about the role. The benefits paragraph at the bottom tells you nothing about fit. The "equal opportunity" boilerplate is legal scaffolding.
The harder cuts are inside the qualifications section. Most JDs list eight to twelve required qualifications. Roughly half of those were copied from a previous JD by the recruiter, and the hiring manager has not reread them. The way you tell which is which is by checking against the responsibilities. If a qualification maps to nothing in the responsibilities section, it's probably scaffolding. If a qualification appears in both (phrased differently in each, but pointing at the same work) it's real.
The "nice to haves" or "preferred qualifications" section deserves its own posture. Read it as a wishlist, not a gate. Hiring managers append items to that list when a candidate they liked but didn't hire had something particular. It accumulates. Treat it as evidence of what would surprise the reader pleasantly, not as a checklist you need to clear.
Mirror the work, not the wording
Once the load-bearing parts are clear, the temptation is to paste the JD's exact phrases into your bullets. Don't. Recruiters and hiring managers read enough resumes against their own JDs to recognize copy-paste in seconds, and copy-paste reads as a candidate who didn't have the work and reached for the words instead.
The move is to mirror the work the JD describes, in your own concrete language, with your own evidence behind it.
JD-mirroring (echoes the wording)
Drove cross-functional initiatives to deliver scalable solutions for enterprise customers in regulated industries.
Work-mirroring (echoes the work)
Led the SOC 2 readiness program for a 40-person fintech, coordinating engineering, legal, and the third-party auditor across a five-month window to a clean Type II report.
The first bullet uses the JD's vocabulary and tells the reader nothing they didn't already know. The second names the specific work, the specific scale, and the specific outcome, which is what the JD was reaching for when it wrote 'scalable solutions for regulated industries' in the first place.
The reader doesn't want to see their own words back. They want to see evidence that the work the words point at has actually happened. For a worked example of how this lands across two roles from the same record, see what tailoring changes; for the full sequence of moves once the JD is parsed, see how to tailor a resume to a job description. The vocabulary question, which terms from the JD belong on the page, is handled in more depth in what ATS keywords actually do.
When the JD contradicts itself
JDs written by committee often contradict themselves. The title says "senior," the responsibilities describe a staff-level scope, and the salary band lands at mid-level. Or the role is described as greenfield in one paragraph and as platform stewardship in the next. Or it asks for ten years of experience in a technology that's six years old.
These contradictions are real information. They tell you the role hasn't been agreed on inside the company yet. The hiring manager has one picture of it, the recruiter has another, and HR has a third. If you go to interview, expect to spend the first conversation figuring out which version of the role is the real one, and use the JD's contradictions as the questions you bring.
For the resume, write to the version of the role you'd actually want, and let the interview sort the rest. Trying to satisfy all three versions on the page produces a draft that doesn't satisfy any of them.
Closing
The JD is a draft. Read it like one.
A JD that's read carelessly produces a resume that mirrors carelessness. A JD that's read like a draft (with three short lists pulled out of it, the load-bearing claims separated from the scaffolding, the contradictions noticed instead of papered over) produces a resume that reads as if the candidate already understood the role before they applied. That's the posture that gets the next conversation.
Take the time. Read the JD twice. Pull the three lists. Then open the resume and write to what's actually there.
Read next