The 6-second resume scan: what recruiters actually see
The well-known study found recruiters spend about seven seconds on a resume. Here's where those seconds go — and what to put on the page to land in the right places.

On this page
The Ladders 2018 study that found recruiters spend 7.4 seconds reading a resume has been quoted so often that the number itself is now folklore. But the underlying eye-tracking work — and the follow-up research from SHRM and others — produced findings beyond just the time figure. The data tells you not only how long a recruiter spends but where their eyes go in those seconds. Knowing the attention map changes how you should structure the page.
This post is about that attention map. The well-known seven-second figure is the headline; the spatial distribution of those seconds is the actionable insight.
What the studies actually found
What the studies actually found
3 StatsAverage time spent on a resume in the original 2018 Ladders eye-tracking study.
Of total attention concentrated on six specific resume zones, not spread evenly across the page.
Of recruiters reach Page 2 of a two-page resume. The first page does most of the work.
A few details worth knowing beyond the headline number:
- The 7.4-second average masks a wide distribution. Some resumes get 4 seconds (the fast skip); others get 30+ (the candidate the recruiter actually opens for real). The average is what gates the dashboard decision, not the deep read.
- The "80% on six zones" finding is more useful than the time. Recruiters aren't reading the page sequentially. They're hitting six predictable spots in roughly the same order, every time.
- Page 2 read rates drop sharply. Only about 35% of recruiters reach Page 2 of a two-page resume, and almost none read Page 3. Anything strategically important needs to live on Page 1.
Where the seconds actually go
The eye-tracking heatmaps from the Ladders study (and similar work since) show a consistent pattern. In the first 4–5 seconds, recruiter eyes hit:
Where the seconds go
Attention mapThat's the gatekeeping read. If those four data points pass — name parses correctly, most-recent role aligns with the target, dates show enough experience without obvious gaps, education line clears any minimum requirement — the recruiter spends the remaining 2–3 seconds on the top of the work history bullets. If any one of the four fails, the resume is skimmed past in under five seconds.
The implication for your page layout: those four data points need to be findable in roughly half a second each. Anything that delays their location costs you the slim margin you have to make a positive impression.
What "optimize for the scan" actually means
This isn't an argument for dumbing down your resume. It's an argument for placing the highest-value information in the highest-attention zones. Two columns. The "do this" column is what the scan rewards. The "lose seconds here" column is what gets resumes filtered:
Optimize for the scan vs. fight against it
Page 1 strategy- Name large, contact info adjacent and selectable
- Most-recent title prominent, exactly the title the role parses to
- Dates in standard format, aligned right or consistently positioned
- First bullet under most recent role: the most relevant achievement to the target role
- Skills section visible on Page 1 if you have one
- A two-line objective at the top that says nothing
- Contact info in a footer or design element the parser drops
- Most-recent title buried under a project description
- First bullet under most recent role: generic 'managed cross-functional teams'
- Skills hidden on Page 2
A few of these are subtle:
The two-line objective at the top. "Seeking a challenging role where I can leverage my skills..." sits in the most-attention zone on the entire page and tells the recruiter nothing. By the time the recruiter has finished reading those two lines, two of their seven seconds are gone and they've learned only that you can write a generic objective. Replace with a tight role-and-domain summary, or delete entirely.
Most-recent title buried. Some resumes lead with a project name or a company description before the title. The recruiter scans for "what role does this person currently hold" and has to hunt for it. Put the title in the position where the eye expects to find it: directly under the company name, with the dates.
Skills hidden on Page 2. For technical and skill-driven roles, the skills section is one of the six attention zones. Putting it on Page 2 means most recruiters never see it. Move it to Page 1 — either above the work history (skills-prominent layout) or compactly in a right column (single-column-but-tight layout).
Page 1 strategy in practice
A useful frame: imagine the recruiter only ever reads Page 1, regardless of what's on Page 2. (For 65% of recruiters, this is literally what happens.) What needs to be on Page 1 to make the case for opening the document fully?
- Your name and contact, parseable.
- Your most-recent title, dates, and company.
- The top two or three bullets from your most-recent role, with the most relevant one first.
- A summary, if you have a strong one (≤30 words).
- A skills section, if your role is skill-driven.
If you have all of the above on Page 1 and the recruiter still doesn't open the full document, the issue is either fit (your most-recent role doesn't match the target) or content (the bullets don't communicate strongly enough). Neither is a Page 2 problem.
What the scan rewards
A few patterns that consistently survive the seven-second read:
Clean information hierarchy. Name biggest, section headings second-biggest, role titles third, body text smallest. The eye finds the high-leverage info because the layout points it there.
Consistent formatting per role. Same structure for every job: title line, company line, dates aligned right, bullets below. Variation in structure costs scan time.
Quantified outcomes in the first bullet. "Shipped X with 14% conversion lift" reads in half a second; "Worked on the checkout flow and helped improve conversion" reads in two. The quantified version delivers more information per scan-millisecond.
Selectable text everywhere. Parsed correctly into the dashboard. The recruiter doesn't have to mentally re-read your name because the parsed version got it right.
A summary line that says something specific. "Senior PM in B2B SaaS" tells the reader more in three words than "Results-driven professional with a passion for excellence" tells in fifteen.
What the scan punishes
Conversely:
- Long blocks of unformatted text at the top. Recruiters skip them.
- Dates in non-standard formats that don't parse. The years-of-experience figure on the dashboard goes blank.
- Skill bar graphics. The parser reads them as "image." The recruiter sees "image" in the parsed data and forms a low opinion.
- Aggressive design layouts that bury the title or scramble reading order.
- Page 2-heavy resumes where the strongest material is below the fold.
What this isn't
A few clarifications:
- It's not a recommendation to abandon depth. Page 2 still matters for the 35% of recruiters who reach it, and for the recruiter who actually opens the full document. The point is to win the Page 1 gatekeeping first.
- It's not a one-size-fits-all template. Different roles emphasize different attention zones. Sales emphasizes results and metrics; engineering emphasizes technical depth and stack; design emphasizes the portfolio link.
- It's not advice to over-design. The clearest layouts win. Over-designed resumes draw attention to themselves and away from the content.
The seven-second scan isn't a war the recruiter is waging on you. It's the unavoidable mechanics of triaging hundreds of applications a day. Resumes that work with the scan — putting the right information in the high-attention zones, in formats the parser handles — earn more time per application than resumes that fight against it. The few seconds added up over a hundred applications matter.
More to read
5 min readLinkedIn vs. resume: where each one earns its keep
What LinkedIn does that a resume can't, what a resume does that LinkedIn can't, and how to keep both consistent without duplicating effort.
resumeslinkedin
6 min readResume length: one page or two?
When one page wins, when two pages wins, the experience cutoff most posts get wrong, and what recruiters actually do with page two.
resumesformat
5 min readChronological vs. functional resume: which format wins?
When each format works, when it backfires, and the hybrid case — with the parser-readability and recruiter-trust tradeoffs spelled out.
resumesformat
6 min readATS-friendly resume format: myths vs. what actually breaks the parser
Most ATS formatting advice on the internet is folk wisdom from 2012. Here's what modern parsers actually choke on — and what's been fine for years.
atsresumes