Read a job description in three passes before touching your resume: first for the overall picture (what problem is this role solving), second for hard requirements versus preferences (separating must-haves from nice-to-haves), and third for language patterns (the exact terminology the employer uses, which belongs in your resume verbatim). Most candidates only do the first pass — which is why their applications miss the mark even when they're genuinely qualified.
There's a specific kind of job search frustration that comes from doing everything right and still not moving forward. You tailored the resume. You wrote a cover letter. You applied. Nothing.
Most of the time, the problem started before any of that — in the 30 seconds most people spend skimming a job description before deciding to apply. That skim tells you enough to know whether the role sounds interesting. It doesn't tell you what you need to know to apply competitively.
A job description, read properly, is a scoring rubric. It tells you what the employer weights most heavily, what language they use internally, what they'll be evaluating you against, and often — if you know what to look for — whether the role is genuinely worth your time. Reading it that way takes 15 minutes. Most candidates won't spend those 15 minutes. That's actually in your favor.
The Three-Pass Method
One read-through isn't enough and a line-by-line crawl isn't efficient. Three passes — each with a specific purpose — extracts everything the JD is actually telling you.
Read for the overall picture
What kind of role is this, really? What problem is the company trying to solve by hiring someone? Is this a build role or a maintain role? Is the team early-stage or established? Read the whole posting once without taking notes — just to understand what you're looking at before you analyze it.
Separate required from preferred
Go through again and mark every requirement as hard (required, must-have, essential) or soft (preferred, nice-to-have, bonus). This is your applicability filter — it tells you whether you're a realistic candidate and which gaps in your profile you'll need to address or explain.
Extract their exact terminology
Read one more time specifically for language — the exact words and phrases the employer uses for the skills and work this role involves. These are the terms your resume needs to mirror. Not synonyms, not your preferred phrasing — their words. This is the pass most people skip entirely.
Three passes on a typical job description takes about 12–15 minutes. What you have at the end is a clear picture of what you're being evaluated on — which is something most candidates never establish before they start writing.
Required vs. Preferred: Why This Distinction Matters More Than You Think
The most costly misread in a job description is treating preferred qualifications as dealbreakers. It causes qualified candidates to self-select out of roles they'd be competitive for. If you've ever looked at a posting and thought "I don't have everything they're asking for" and moved on — there's a real chance you were looking at a preferences list, not a requirements list.
| Signal words for REQUIRED | Signal words for PREFERRED |
|---|---|
| Required, Must have, Essential, Minimum qualifications, You will need | Preferred, Nice to have, Bonus, Ideal candidate has, Plus if you have |
| What it means: Missing these is typically an automatic filter-out in ATS screening. These are the baseline for the role. | What it means: Genuine bonuses the employer would welcome but will hire without. Strong alignment on required qualifications can compensate for missing preferred ones. |
The rule of thumb: if you meet the required qualifications and a majority of the preferred ones, you're a competitive applicant for that role. Apply. If you're missing multiple required qualifications, your match score will reflect that — and it's worth being honest with yourself about whether the application is a realistic investment of time.
The years-of-experience trap: Experience requirements listed as "5+ years" are usually soft targets, not hard gates — especially when they appear in the preferred section. Studies consistently show that women and underrepresented candidates disproportionately self-screen based on years-of-experience requirements that hiring managers themselves treat as guidelines. If the experience you have is genuinely relevant, let your match score tell you whether to apply — not a number in a bullet point.
Reading for Language: The Pass Most People Skip
Your resume could be a perfect representation of your experience and still score poorly against a specific JD — because it uses your language, not theirs.
This isn't about keyword stuffing. It's about translation. Every industry, every company, every team has its own internal vocabulary for the same underlying work. "Paid media execution," "performance marketing," "digital advertising management," and "paid channel strategy" can all describe the same job. The ATS doesn't know they're synonyms. The AI screening tool doesn't either. If the JD says "paid media execution" and your resume says "digital advertising management," you've described the same experience in a way the system doesn't connect.
On your third pass through the JD, pull out the specific phrases the employer uses for:
- The core skill areas — how do they describe what this role does day-to-day?
- The tools and technologies — what exact product names, platforms, and systems do they mention?
- The outcomes they care about — what metrics, results, or deliverables do they reference?
- The team and collaboration language — do they say "cross-functional" or "cross-team"? "Stakeholders" or "partners"?
Every term you extract from this pass is a candidate for your resume. Not forced in — woven in naturally, replacing your synonyms with their vocabulary wherever both are accurate descriptions of the same thing.
The frequency signal: If a word or phrase appears three or more times in a job description, that's a strong signal it's a core evaluation criterion — not just filler. Weight those terms heavily when deciding what to emphasize in your resume. The employer is telling you, repeatedly, what matters most.
Reading Between the Lines: Implied Requirements
Every job description has two layers of requirements: what's written and what's obvious. The written requirements are explicit. The implied requirements are what any thoughtful reader of the JD would recognize as necessary even though they're never stated.
What does this actually look like?
- A content marketing role that mentions "working closely with the sales team" implies you need to understand pipeline, conversion, and revenue goals — even if those words don't appear in the requirements.
- A "senior" title on any role implies ownership of outcomes, not just task completion — even if the bullet points describe tactical work.
- A startup listing "you'll be our first X hire" implies you need to be comfortable building from scratch without existing processes, documentation, or teammates to ask.
- A remote role at a distributed company implies strong async communication skills and self-direction — rarely stated, always evaluated.
Candidates who demonstrate awareness of implied requirements stand out because most applicants never think past the written list. If your resume or cover letter shows that you understood what the role actually demands — not just what was written down — that's a signal of judgment that's hard to fake.
Red Flags to Spot While You're Reading
A job description is also the employer's first communication with you. The same read that tells you what they're looking for also tells you something about how they think, what they value, and whether the environment is likely to be functional.
Certain phrases show up in bad job postings repeatedly. They're not dealbreakers by themselves — but they're worth taking seriously:
Almost always signals an understaffed team. Within 60 days you'll be doing work that wasn't in the job description — often work that belongs to a role they can't afford to hire.
They haven't thought carefully about what this role actually needs. Vague expectations going in means vague feedback and moving goalposts once you're there.
Can mean exciting and high-growth. More often means no documentation, no processes, and someone in your Slack at 9pm asking where a file is.
Companies that are genuinely good to work at don't need family language to keep people around. When they use it, they often mean professional boundaries will be framed as disloyalty.
Passion is what companies ask for when they're planning to underpay you. Enthusiasm doesn't pay rent and it doesn't justify below-market comp.
If the salary were genuinely competitive, they'd lead with it. The number not being there is the answer. A salary range in the posting is a green flag, not a standard.
Two or three of these together? Don't apply. The full breakdown of red flag phrases covers each one in more depth.
Putting It Together: The Full Pre-Application Process
Here's the complete sequence — from finding a role to having a tailored application ready — built around reading the JD first:
First pass: context read
Read the full JD once without stopping. Get a clear sense of what kind of role this is, what problem it solves, and whether it's a realistic fit for where you are in your career. Make a go/no-go call before investing further time.
Second pass: classify requirements
Go through every requirement and mark it as required or preferred. Build a short list of the 6–8 core hard requirements — the things the ATS and the recruiter are primarily evaluating you on. These become your resume's primary targets.
Third pass: extract language
Identify the specific terminology the employer uses for the work, tools, and outcomes this role involves. Anywhere your resume uses a synonym for the same concept, swap it for their language — provided it's an accurate description of what you actually did.
Scan for red flags
Before you start writing anything, check the JD for warning signs. If you find two or three, decide whether the role is worth your time before investing in tailoring. An honest answer now saves you from a decision you'd regret later.
Run a match score check
Before or after your tailoring edits, run your resume against the JD to see where you land. The score and skill-by-skill breakdown will surface gaps your manual read missed and confirm whether your rewrites moved the needle.
Now write
With the requirements, language, and gaps in hand, write your tailored resume and cover letter. Every decision has a clear reference point: the JD you've read three times. You're not guessing what they want — you know.
What This Changes About How You Apply
The practical effect is that you apply to fewer roles and advance more. Not because you're better qualified — but because your resume now speaks the language each employer uses to evaluate you.
You also waste less time. Fifteen minutes reading a JD upfront means you might skip roles you'd have spent 90 minutes on. That's not lost work. That's being selective. Every application costs time and energy. Spend them on the ones worth pursuing — and kill the others before you start writing.
The connection to match scoring: Everything you extract from this three-pass process — the core requirements, the language, the implied expectations — is exactly what a match score is measuring. Reading the JD this way and then running a score check gives you a double signal: your qualitative read plus a quantitative verification of whether your resume communicates what you intend it to.
Frequently Asked Questions
How do you actually read a job description?
Three passes. First: read the whole thing once. Get the shape of it. Second: go back and mark every line as required or preferred. Third: pull out the exact words they use — for skills, tools, outcomes, all of it. That's what goes in your resume. Most people skip pass three. That's why they lose to people with the same qualifications.
What am I actually looking for?
Four layers: the hard requirements (non-negotiable), the implied ones (obvious if you read carefully), their exact terminology (which you use, not synonyms), and red flags that tell you the company won't be good to work for. Most candidates see the first one and miss the other three.
What is the difference between required and preferred qualifications?
Required qualifications are the baseline — missing them typically means automatic disqualification in ATS screening. Preferred qualifications are genuine bonuses the employer would welcome but will hire without. If you meet the required qualifications and most of the preferred ones, you're a competitive applicant. Many candidates disqualify themselves from roles they'd be strong for by treating preferred requirements as hard gates.
How much time do I actually need to spend?
Twelve to fifteen minutes if you're reading it right. More valuable than an hour of resume work. Because this is where you figure out what you're actually competing on. Without it, you're just guessing.
How do I know if the posting is bad?
Certain phrases keep showing up: "wear many hats" means they're understaffed. "Rockstar" or "ninja" means they haven't actually defined the job. "Fast-paced" means no structure. "Must be passionate" means they're going to underpay you. "Competitive salary" with no number means it isn't. See two or three of these? Skip it.
⚡ Read the JD. Then check your score.
Match score, missing keywords, skill matrix, and line-by-line rewrites. Free to start.