Most candidates read job descriptions linearly — top to bottom — and assume the posting means what it says, equally weighted. That misreads the posting. A job description is a structured document that signals different things at different layers, and the layers carry very different weight in the screening process. The candidates who tailor well aren't reading the posting more carefully; they're reading it differently.

This post is about decoding the structure: what's actually a must-have, what's wishlist, and what the soft signals tell you about the team and the role beyond the explicit requirements.

The three layers of a posting

Every job description, regardless of how it's structured, contains three layers:

What a posting actually contains

Three layers

Layer 1

Hard requirements

Years of experience, certifications, work authorization, security clearances, location. Filtered on automatically. Hit these or you're out before content matters.

Layer 2

Stated skills

Tools, frameworks, methodologies. Some are real must-haves; many are wishlist. Phrasing tells you which is which.

Layer 3

Soft signals

Tone words, repeated themes, structural cues. What the team actually values, beyond the technical line. The most under-read part of the posting.

Layer 1 is what the system filters on. Layer 2 is what the recruiter checks against your resume. Layer 3 is what shapes how the hiring manager and interviewers read your resume in the rounds that follow. They don't carry equal weight, but each one matters at a different stage.

What the layers actually weigh

What actually drives the screening decision

Weighting

100/100

Approximate weight of each layer in the recruiter screening decision.

Layer 1 — Hard requirements50/100

Layer 2 — Stated skills30/100

Layer 3 — Soft signals15/100

Other (referrals, source, fit)5/100

Roughly half the screening decision rides on Layer 1 — the hard requirements. Years, certifications, location, work authorization. These are deal-breakers. If a posting says "5+ years of Python required" and the parser estimates you have 3.5 years, you may be filtered before content matters.

Roughly a third rides on Layer 2 — stated skills. The resume's keyword fit against the posting's skill list is what most "tailoring advice" focuses on, and the focus is correct. But it's not the whole game.

The remaining 15% — Layer 3 — is often the difference between a callback and silence among candidates who pass the first two layers. Tone words, repeated themes, the company's writing style, and structural cues all shape the recruiter's impression. They don't disqualify you, but they tip borderline calls.

Decoding the phrasing

The single most useful skill in posting-reading is recognizing the difference between must-have phrasing and wishlist phrasing:

Phrasing tells you must-have from wish-list

Read carefully

Must-have phrasing

• 'Required: 5+ years of [X] experience'
• 'Must have working knowledge of [X]'
• 'You will need to [X]'
• 'Demonstrated experience with [X]'

Wish-list phrasing

• 'Bonus points for [X]'
• 'Experience with [X] is a plus'
• 'Familiarity with [X] preferred'
• 'Exposure to [X] valued'

The patterns are remarkably consistent across industries:

• "Required" and "must have" mean what they say. Hard filter.
• "Demonstrated experience" or "proven track record" mean must-have, with the implication that the recruiter wants evidence in the resume bullets, not just claims in the skills section.
• "You will need to" or "in this role you will" describes the work, which translates to must-have ability to do that work — but it's softer than explicit "required" language.
• "Bonus points," "is a plus," "preferred," "valued" is wishlist. Mentioning if you have it; not disqualifying if you don't.
• "Exposure to" or "familiarity with" is the softest wishlist phrasing. Don't claim it unless you have it; don't worry if you don't.

The asymmetry: candidates often treat "preferred" as required (and feel underqualified for postings they'd be a fine fit for) and treat "required" as preferred (and apply to roles they don't actually qualify for). Reading the phrasing precisely fixes both errors.

Decoding the soft signals

Layer 3 is where most candidates skim. The signals that actually carry information:

• Words that repeat 3+ times. "Cross-functional," "ambiguity," "ownership," "data-driven." These are what the team actually emphasizes — what they'll ask about in interviews and what they'll look for in your bullets.
• The first paragraph's tone. Is it formal ("The Senior Engineer is responsible for...") or casual ("We're a small team building...")? This tells you the company culture and how to write your cover letter or first interview email.
• The "About the role" vs "About you" sections. Companies that lead with "About the role" tend to be more process-oriented; ones that lead with "About you" tend to be more people-oriented. Adjust your application accordingly.
• The benefits and compensation section's specificity. Vague benefits ("competitive salary, comprehensive health") often correlate with rougher hiring processes. Specific ranges and detailed benefits correlate with more transparent companies.
• The team-size or company-stage hints. "We're a team of four" tells you something different from "Join our 200-person engineering org." Optimize your application for the actual scale.

Specific patterns to watch for

A few common patterns worth knowing:

The "wishful posting" — long requirement lists with no clear distinction between must-have and preferred. These are often written by hiring managers who have a unicorn in mind. Apply if you hit 70% of the must-haves and treat the wishlist as aspirational. The role likely won't actually require everything listed.

The "hyperspecific posting" — extremely narrow requirements that read like one specific person's resume. ("7 years of [exact obscure stack] in [exact niche industry]"). These are often internal-candidate postings filed for compliance reasons. Skip unless you're an exact match.

The "vague generalist posting" — broad enough that it could describe any of ten roles. ("Help us scale!" "Drive impact!"). These can be either pipeline-building (real but not urgent) or placeholders. Treat as low-priority unless you have a specific connection to the company.

The "tone shift posting" — formal at the top, casual at the bottom (or vice versa). Often written by HR with edits from the hiring manager. The casual section probably reflects the team's actual culture; the formal section is the company line.

The "stale posting" — same listing reposted every 30 days, identical text, no changes. Often a stale opening with no real urgency. Can also be a real role that the company keeps fresh through reposts. Hard to distinguish without applying.

How to use the analysis when you tailor

Once you've decoded the posting, the tailoring decisions follow:

• For Layer 1 (hard requirements): make sure your resume parses the right values. Years of experience computed correctly, location stated, certifications visible. This is where format issues silently disqualify you.
• For Layer 2 (stated skills): match the must-haves first. Use the posting's exact phrasing in places where you've genuinely done the work. Don't sweat the wishlist items unless they're gimmes.
• For Layer 3 (soft signals): adjust your summary and the first bullet of your most recent role. If "ambiguity" repeats three times, your summary mentioning "leading product through ambiguous problem spaces" is the move. If "cross-functional" repeats, frame your work history in terms of partnerships.

The tailoring's leverage is concentrated. Layer 1 mismatches kill applications; Layer 2 fit moves you up the dashboard; Layer 3 alignment tips borderline calls. Spending five minutes decoding the layers before you tailor produces a stronger result than thirty minutes of generic rewrites.

What this isn't

A few things this isn't:

• It's not a code-breaking exercise. Job descriptions are written by people in roles where they're often rushed. Reading carefully is useful; over-reading is paranoid.
• It's not a substitute for honest fit. All the decoding in the world doesn't help if you don't actually match Layer 1. The 70% rule still applies.
• It's not advice to mention every soft-signal word. Three to five posting-language words woven into your resume reads as fit. Twenty reads as stuffed.

The point is to read postings as data, not as prose — and to weight the layers proportional to how much they actually drive the screening decision.