You spend hours on bullets. The hiring manager spends 6 seconds on the first pass.
This isn’t a complaint about hiring quality — it’s a structural reality. A hiring manager screens 100+ resumes per role. They can’t read them. They scan for shape match: does this résumé look like the kind of person we hire for this role? If yes, they’ll spend another 30 seconds. If not, reject.
Knowing what they scan for changes everything.
Pass 1 — silhouette (~2 seconds)
The hiring manager’s brain does a near-instant gestalt read of the document:
- How long is it? (Two pages for a senior IC = “trying too hard,” 0.5 pages = “junior or sloppy”)
- Where does the experience section start? (Top? Below a long summary? They want the meat fast.)
- Does the most recent role take up the majority of the page? (As it should.)
If the silhouette is wrong — too dense, too sparse, summary that won’t end — they often reject before reading a word.
Pass 2 — level cues (~4 seconds)
The eye lands on three places:
- Most recent title. “Head of Product, Growth” reads instantly different from “Senior PM” or “Product Manager.”
- Years of experience. The number itself, plus the implied seniority (3 yrs ≠ Lead, 12 yrs ≠ IC2).
- Top bullet of the most recent role. This is the one that gets read in full. Everything else is skimmed.
The triangulation tells the manager what level you are. If that level doesn’t match the role, they reject. They don’t care that you could do the work — they care that they’d have to defend the hire to their boss, and the defense is hard when level visibly mismatches.
More on this: Am I overqualified for this job? · Seniority mismatch on a resume
Pass 3 — execution signal (~4 seconds)
If level passes, the manager looks for verbs that match the work. They scan for things like “shipped,” “wrote,” “deployed,” “queried” — the things the JD said the role would do.
If your bullets are all “led,” “aligned,” “championed,” “owned” — strategic verbs without the execution underneath — you fail this pass even when level was fine. They read “this person directs work; we need someone who does it.”
More on this: Execution verbs vs. strategic verbs · Mirror the job description in your resume
Tacit disqualifiers — what’s not in the JD
The third filter is the one nobody writes down. It’s what the JD implies:
- “You’ll work with a 4-engineer pod” → no direct reports, no team to manage.
- “Async-friendly” → expectation of long async writing, comfortable with no real-time meetings.
- “Reports to the Director of X” → the manager is not an exec; you can’t pitch yourself as peer-of-CEO.
If your résumé contradicts these implications, you read as the wrong shape — even if every requirement on the list is met.
More on this: Tacit disqualifiers in job postings · Team size and reporting structure cues on a resume
The diagnostic mirrors this in 27 seconds
Reading your own resume the way a hiring manager will is hard because you wrote it. The diagnostic does it for you: it reads the JD for level cues, execution-verb density, and tacit disqualifiers, then matches them against your profile and tells you which of the three passes you’ll fail.
Two free runs, no card. The first one usually surprises people.
Related reading
- Resume red flags for hiring managers — the specific phrases and patterns that move a resume to the reject stack.
- Resume filters beyond ATS keywords — the filters that matter once your resume passes the keyword scanner.