How to Read a Job Description (Must-Haves, Red Flags, Level)

Decode dense postings into priorities before you spend hours tailoring an application - or decide to pass.

Published June 1, 2026Updated June 2, 20264 min read

Job descriptions are written for multiple audiences - legal, hiring managers, and SEO. They are often longer than the role actually requires, sometimes undersell how senior the work really is, and occasionally hide dysfunction behind buzzwords.

Learning to decode a posting saves hours. You tailor to what matters, spot misalignment early, and walk into interviews knowing which themes will dominate the loop.

The three-pass read (15 minutes)

Pass 1: Must-have extraction (5 min)

Highlight terms in:

"Requirements," "Qualifications," "Must have"
First third of responsibilities
Anything repeated 2+ times

Sort into buckets:

Bucket	Example
Must-have skills	Python, customer onboarding, SQL
Must-have scope	Own roadmap, manage 3 reports
Nice-to-have	Looker, startup experience
Tools	Jira, HubSpot, AWS

If you miss 2+ must-haves with no honest bridge, treat it as a stretch apply - not a keyword-stuffing exercise.

Pass 2: Level read (5 min)

Compare title, years asked, and verbs used:

Signal	Often means
"Lead" + IC verbs only	Title inflation - read bullets carefully
"Player-coach"	Hands-on plus people management
"0→1"	Ambiguity, building from scratch
"Scale" / "mature"	Optimization, reliability, process
"Partner with" repeated	Cross-functional influence required
Team size mentioned	Scope expectation is explicit

Mismatch on level shows up as rejection after final rounds - not as an ATS glitch.

Pass 3: Red flag scan (5 min)

Not every flag means "do not apply" - but go in with eyes open:

Red flag	What to ask in interview
Kitchen-sink stack (15+ tools)	"Which 2–3 are core in the first 90 days?"
Vague scope ("wear many hats")	"What does success look like at 30/60/90 days?"
Urgent hire + junior pay band	"Why is the role open now?"
High turnover language	"How long has the team been together?"
Equity-only for non-founder roles	"What is the cash comp range for this level?"

Must-have vs nice-to-have: language cues

Usually required:

"Required," "must," "minimum"
Listed in first requirements block
Repeated in responsibilities

Usually optional:

"Preferred," "bonus," "ideal"
"Exposure to," "familiarity with"
Long tool laundry lists where only 2–3 appear in responsibilities

When unsure, assume required for apply/no-apply decisions, then confirm in recruiter screen.

Decode example: CSM posting

JD excerpt:

"Own onboarding for mid-market accounts. Reduce churn in first 90 days. Experience with Gainsight and SQL reporting required. Preferred: startup background, HubSpot."

Decode:

Element	Read
Must-haves	Mid-market CS, onboarding ownership, 90-day churn metric, Gainsight, SQL
Nice-to-have	Startup pace, HubSpot
Level	IC with metric ownership - likely not managing people
Interview themes	Onboarding playbook, churn reduction story, tooling depth

Prep stories and resume bullets around 90-day churn and Gainsight/SQL - not generic "customer success" language.

Turn decode into action

After decoding:

Resume Fit Checker - fit score and gap list
ATS Keywords Extractor - keyword checklist if proceeding
Cover Letter Generator or pass decision
Mock Interview Prep if interview scheduled

Use Job Description Decoder to automate must-have / nice-to-have / flags / level estimate from the full pasted posting.

When to pass instead of apply

Must-haves include regulated domain experience you lack with no adjacent bridge
Level is manager track but your examples are purely IC
Red flags stack (vague scope + urgent hire + below-market comp hints)
Same company rejected you twice for the same gap - address gap before re-applying

Passing is a time management win, not a failure.

Bottom line

Read the posting like a hiring manager's wish list, not marketing copy. Extract must-haves, estimate level, note flags, then decide fit before you spend an hour tailoring.