What Recruiters Actually Look at in the First 6 Seconds

The Ladders and Shelley Morse eye-tracking study from 2018 is widely quoted for a reason: recruiters spend about 7.4 seconds on an initial resume scan. Other studies put the number closer to 6 seconds for high-volume reviewers. Either way, that is the amount of attention your resume receives before a decision is made. It is not enough time to read your entire work history. It is barely enough time to read your job titles.

That sounds bleak. It is actually good news. If the recruiter is scanning for 6 seconds, then the question is not "how do I make them read every bullet." The question is "what do they see in 6 seconds, and does what they see match the role they are hiring for."

The F-shaped reading zone

Eye-tracking studies of how recruiters read resumes consistently show the same pattern: an F-shape. The eye moves in a horizontal sweep across the top of the page — name, current title, current employer. It then drops down and does a second, shorter horizontal sweep. Then a third, even shorter. The right side of the page and anything below the third row receive almost no attention.

Practically, this means the top of your resume is the only part that gets read carefully. Below that, the recruiter is grabbing fragments — job titles, employer names, first words of bullet points. Anything important that lives low on the page or far to the right is functionally invisible during the scan.

What to do with this: put your strongest, most relevant signals in the top third of page one. Current title that matches the role. Employer that signals prestige or relevance. One line summary that names your specialization. The first 3–4 bullet points under your current role need to do real work — the rest get skimmed.

Career trajectory consistency

What recruiters look for in those 6 seconds is not a perfect career — it is a clear one. Gaps, downward moves, lateral jumps that don't match the storyline — these are the things that trigger the "rejected" signal without the recruiter consciously deciding to reject.

Trajectory matters more than any individual job title. A senior product manager who took a step down to mid-level and is now climbing back up reads as someone who had a setback. A generalist who has jumped between sales, marketing, and operations every two years reads as someone who has not focused. Neither of these are dealbreakers, but both require the recruiter to spend longer than 6 seconds to figure out what is going on — and most will not.

The fix is not to invent a fictional career arc. The fix is to make the arc visible. If your trajectory has detours, name the bet you were making. "Took on Head of Ops to build the post-Series-B operations function" explains why a senior IC took a sideways move. Without that one line of context, the recruiter reads inconsistency.

Achievement specificity — vague vs specific

Two candidates apply for the same role. Both led a sales team. One writes: "Responsible for sales across the DACH region." The other writes: "Closed €1.2M in new business, FY25 (132% of quota). Hired and trained 4 AE's, ramped to productivity in 90 days."

Both bullets occupy the same space on the page. In a 6-second scan, the second one is recognized as real signal. The first is noise. A recruiter skimming at speed treats generic achievements as filler and moves on.

This is true at every level. Specificity is a proxy for impact. Numbers are not required — but outcomes, scope, and stakes are. "Owned onboarding redesign that cut time-to-first-value from 14 days to 4" is specific. "Led onboarding improvements" is not. In a 6-second scan, the difference between these two is the difference between a callback and a pass.

• Vague: scope and responsibility

  "Managed a team of engineers responsible for the payments platform." Tells the recruiter you had a job. Does not tell them what changed because you were in it.

• Specific: outcome and stakes

  "Led 6-engineer team rebuilding payments platform — cut p95 latency from 1.4s to 240ms, freed €2.1M/yr in interchange fees." Same scope, real outcome, real stakes.

• Vague: action without context

  "Drove cross-functional alignment on product roadmap." No mention of what was alignment-blocked, who was involved, or what shipped.

• Specific: mechanism and result

  "Built a quarterly planning ritual with Eng, Sales, and CS — cut roadmap changes mid-quarter by 70% and shipped 4 launches on time in FY25."

ATS keyword filtering shapes the scan

Here is the part most candidates misunderstand: the recruiter running the 6-second scan is usually looking at the same resume the ATS already scored. The ATS acts as a pre-filter — if your resume does not match the job description's keyword profile, it never reaches a human. If it does, the recruiter is reading what an algorithm has already approved.

This means the 6-second scan is not arbitrary. It is checking: does what the ATS flagged on this resume match what I am hiring for? If your resume passed the ATS but reads as off-target during the scan, the recruiter assumes a false positive. Better candidates who match both filters get attention.

This is why matching the job description's keywords is not optional — it is the only way your resume reaches a person. And specificity is what turns the resume that reached a person into the resume that gets contacted.

Formatting that survives the scan

Formatting does not matter to the recruiter — until it gets in the way of the scan. The F-shape assumes an uninterrupted vertical column of readable text. Anything that breaks that column also breaks the scan:

• Two-column layouts

  The left column gets read, the right column gets ignored. Worse: many ATS systems read two-column documents out of order, garbling the content entirely.

• Tables and text boxes

  ATS parses table cells in unpredictable order. Text boxes are frequently invisible to parsers. Content inside them may be unreadable to the algorithm and skipped by the human.

• Contact info in headers or footers

  Many ATS systems ignore headers/footers entirely. If your email is in the header and not the body, the recruiter has no way to contact you even if they want to.

• Image-based PDFs

  A PDF that looks like a designed page but has no selectable text is parsed as a blank document by most ATS systems. The recruiter, if they see it, sees a wall of pixels with no scan-line target.

The formatting that survives: single column, selectable text, conventional section headers (Work Experience, Education, Skills), standard section ordering, and contact info in the body — not the header. Clean, parseable, scannable. The goal is to make the F-pattern easy for the eye, not to win a design award.

Putting it together

The 6-second scan is not the enemy. It is a constraint, and constraints are useful because they force focus. If the recruiter is going to spend 6 seconds on your resume, then those 6 seconds need to answer three questions: What is your current level? Does your background match the role? Have you produced outcomes at that level?

A resume that answers those three questions in the F-shaped reading zone — current title visible, trajectory clear, top-of-page bullets specific — passes the scan. A resume that scatters the answers across a designed layout or hides them in the second half of the second column does not. The recruiter does not need to be unfair for your resume to lose. The structure does the work for them.

Build the resume for the scan, not for the read-through. The read-through happens only after the scan passes — and the scan is unforgiving.