Reading a Job Description Like a Recruiter: The Four Signals That Decide Your Verdict

Key takeaways

• Read the responsibilities before the requirements; they describe the job, not the imagined candidate.
• Four signals decide the verdict: the thing the posting repeats, the numbers, the reporting line and verbs, and the posting's health.
• Ignore the company blurb, culture language, benefits, and adjectives — none of it changes a verdict.

Most candidates read a job description the way it is laid out: title, company blurb, responsibilities, requirements, benefits, boilerplate. By the end they remember the title, a general impression, and whether the salary was listed.

A recruiter reads the same document differently, because they wrote it — or watched it being written — and they know which parts carry information and which parts are furniture. They read for a handful of signals, in a few minutes, and those signals are most of what decides whether an application gets read.

You can read it the same way. This guide gives you the anatomy, the four signals, and a five-minute procedure that feeds the Apply / Adapt / Skip verdict.

The anatomy of a posting

Six parts, in roughly this order, with roughly this information content:

Section	Written by	Carries
Title	Hiring manager, edited by HR to fit a grade	Level (unreliably), function
About the company	Marketing template	Nothing you cannot get elsewhere
Responsibilities	Hiring manager	The job — the most honest section
Requirements	Manager + recruiter + template accretion	The imagined candidate, mislabeled
Benefits, culture	HR template	Nothing for the verdict
Legal, EEO, accommodations	Legal	Nothing for the verdict

Two sections matter. Responsibilities describe what the person will do; requirements describe who the writers imagine doing it. When the two disagree — and they often do — the responsibilities win, because a manager writing "you will own the monthly close" is describing a fact, and a template writing "10+ years' experience" is describing a habit.

The four signals

Signal 1 — The repeated thing. Every posting has one activity that appears more than once: in the title, in the first responsibility, again in the requirements, maybe in the summary. That repetition is not sloppy editing; it is the writer telling you what the job actually is. Find it first. It is the core requirement against which everything else is decoration, and it is what the interview will spend most of its time on. What "must-have" and "nice-to-have" really mean covers how the rest of the list sorts around it.

Signal 2 — The numbers. Budget, revenue, headcount, deal size, transaction volume, number of markets. A number in a posting is a fact someone bothered to write down, and it fixes the scale of the role more precisely than any adjective. "Lead a team" means nothing; "lead a team of 6" means one thing; "lead a team of 40 across three sites" means another. A posting with no numbers at all is either junior, or a template — a posting-health signal in itself.

Signal 3 — The reporting line and the verbs. "Reports to the CFO" and "reports to the FP&A manager" are different jobs with the same title. The verbs do the same work: own, define, set, lead sit at one level; support, execute, maintain, assist sit at another. Together they tell you the level of the role far more reliably than the title, which was set by a grading scale rather than by the work.

Signal 4 — Posting health. The first three signals tell you what the job is. The fourth tells you whether the job is real and open. Age: how long has it been up, and has it been reposted? Specificity: does it describe one job, or three jobs stitched together? Particularity: does the requirements list read like a description of one specific person who already works there? Any of these can turn a perfect fit into a SKIP, because the posting's outcome was decided before you arrived. Is it worth applying to a job posted 30+ days ago and Ghost jobs and internal-candidate postings go through the tells in detail.

The five-minute procedure

1. Skip to the responsibilities. Read them twice. Underline the activity that recurs or is stated first. That is the job.
2. Circle every number. Write the scale of the role in one line: owns X, team of Y, reports to Z.
3. Read the requirements against the responsibilities. Anything that echoes a responsibility is core. Anything with a licence, clearance, authorization, or a tool in the title is a gatekeeper. Everything else is decoration, whatever heading it sits under.
4. Check the health. Date posted and reposted; one job or several; a requirements list that describes a particular person; salary present where it is expected.
5. Write the verdict inputs in one line. Gatekeepers: A, B. Core: C, D, E at scale S. Level: L. Health: fine / suspect. That line, against your resume, is the verdict.

Five minutes. It replaces the top-to-bottom read that produces a feeling, with a read that produces inputs.

What to ignore

• The company blurb. If you need to know the company, use the company's site, not its recruiter's paragraph.
• Culture language. "Fast-paced," "collaborative," "we're like a family" — no verdict has ever turned on any of it.
• Benefits. Relevant to whether you accept an offer; irrelevant to whether you apply.
• The EEO and accommodation text. Legal boilerplate, identical across every posting the company runs.
• Adjectives in the requirements. "Strong," "excellent," "proven." They modify nothing measurable.

Ignoring these is not cynicism. It is reading the document for what it can actually tell you, which is the job, its scale, its level, and whether it is real.

Reading faster

The procedure above is what SmarterApply runs on a posting before it compares anything to your resume: it isolates the repeated thing, extracts the numbers, reads the level from the reporting line and verbs, and checks the health signals — then applies the result to your resume for a verdict with the reasons attached. The first analyses are free. Paste the posting you just read top to bottom.

FAQ

What if the responsibilities and requirements contradict each other?

Trust the responsibilities. They were written by the person who will manage the role. A requirement with no echo in the responsibilities is usually a template line, and you should not let it decide your verdict either way.

The posting has no numbers at all. What does that tell me?

Either the role is junior enough that scale does not matter, or the posting was assembled from a template without the manager's input — which is a health signal worth weighing. Look for scale elsewhere: team size on the company page, the reporting line, the level in the title.

How much weight should I give the title?

Less than you do. Titles are set by grading scales and vary wildly between companies. Read the level from the reporting line and the verbs, and let the title confirm or contradict it.

Should I read the salary as a signal?

Where posting a range is expected and it is missing, note it as a mild health signal. Where a range is present, read it as a level signal — it will confirm or contradict what the verbs and reporting line said.