David runs every Beacon search personally and reviews every resume and interview debrief before a candidate reaches a client.
Most hiring managers decide whether to keep reading your resume within seconds, then spend one to three minutes on it if it survives that first pass. What they're scanning for in that window, and what a system-design round evaluates once you're past it, is more specific than most advice admits.
What gets you past the first scanThe top third of the page does almost all the work. Hiring managers are matching your most recent, most senior role against the job's required skills and scope within seconds, so if the headline role, the keywords the job description actually asks for, and a sense of scale aren't visible without scrolling, the rest of the resume may never get read.
| What's on the resume | Reads as a strength | Reads as a risk |
|---|---|---|
| Bullet points | Specific outcome with scale ("cut p95 latency 40% across 3 services") | Responsibility with no outcome ("responsible for backend services") |
| Tech stack | Matches the job description's actual stack, no padding | Long keyword list unconnected to any project |
| Scope over time | Visible growth in scope, team size, or ownership role over role | Same scope and title repeated across several employers |
| Tenure pattern | Each move has an implied or stated reason tied to growth | Multiple short stints with no visible reason |
| Formatting | Plain text, single column, parses cleanly into an ATS | Multi-column or graphic-heavy layout that can parse into the wrong fields |
It's testing whether you can reason about tradeoffs out loud at the scope the role requires, not whether you can recite a textbook architecture from memory. A candidate who says "I'd start with X because Y, and I'd reconsider if Z" is demonstrating the actual skill; a candidate who jumps straight to a fully-formed diagram without naming any tradeoff usually isn't.
Most engineering interview loops run four to six rounds covering coding, system design, and behavioral fit, with system design weighted more heavily as the role gets more senior. For an IC role it's typically one round among several; for an engineering-manager or VP-level search, tradeoff reasoning often carries the loop, because the job itself is mostly tradeoff decisions made at a larger scale.
Gaps and job-hopping get flagged by a meaningful share of recruiters, but neither is automatically disqualifying on its own. The pattern behind the move matters more than the move itself: what changed, why you left, and what you shipped before you did. Typos and inconsistent formatting are the one category that reads badly with almost no exception, because they're read as a signal about attention to detail, not context.
We've placed engineers with three jobs in four years and engineers with one job in ten. Neither pattern tells you anything by itself. What tells you something is whether the candidate can explain each move in one honest sentence.
Seconds, not minutes, on the first pass, commonly cited in the single digits to roughly 30 seconds. If your resume survives that scan, most hiring managers who move to a closer read spend one to three minutes, per recruiter-reported data. The top third of the page is doing almost all the work in that first pass.
It's weighted, not disqualifying. Recruiter-reported data puts job hopping as a concern for roughly half of recruiters, but most hiring managers we talk to read the pattern, not the count: what changed at each move, why the candidate left, and what they shipped before moving on. A string of short stints with no stated reason reads very differently from the same stints with a clear one.
Rarely on its own. Gaps get flagged by a meaningful share of recruiters as something to ask about, not something to reject on sight, and that's grown more true since the recent wave of tech layoffs normalized them. An unexplained gap paired with vague descriptions elsewhere on the resume is the actual combination that raises concern.
Whether you can reason about tradeoffs out loud at the scope the role requires, not whether you can recite a textbook architecture. For IC roles that's usually one component of a multi-round loop; for engineering-manager and VP-level searches it's often weighted more heavily because the role itself is mostly tradeoff decisions.
Address it briefly in the resume or cover context if it's a gap or a short stint with a clear, honest reason. One line removes the question before it becomes a silent assumption, which is almost always worse than the actual explanation.
David runs every Beacon search personally and reviews every resume and interview debrief before a candidate reaches a client.
Join the Beacon Devs candidate network. It's free, always, and most of the roles we fill never go on a job board.
Join the network