The 11-second resume: a teardown
Recruiters scan resumes in an F-pattern for about 11 seconds. Here's what that means for where every word on your resume should go.
Your resume is not being read. It's being scanned — in about 11 seconds, in a predictable shape, by someone who has 400 other resumes open in another tab.
If you design your resume around that reality, you make it through. If you don't, you don't. It really is that simple.
The 11 seconds is real — and so is the F-pattern
The numbers first:
- An August 2025 InterviewPal study pegged the average initial recruiter scan at 11.2 seconds, with a median total review time of 1 minute 34 seconds only after the resume clears that first filter (InterviewPal).
- The original Ladders eye-tracking study, covered by HR Dive, found recruiters spent about 7.4 seconds on the initial screen — an improvement from 6 seconds in an earlier recession-era study (HR Dive).
- The average corporate recruiter is juggling 15–25 open roles and receives 300–500+ resumes per posting (InterviewPal).
So call it somewhere between 7 and 11 seconds. Either way, it's barely enough time to read a paragraph. What's a recruiter actually doing with those seconds?
The Ladders eye-tracking data answers this. Recruiters read in an F-pattern (and sometimes an E-pattern): they sweep across the top line, drop down the left margin, sweep across part of the next line, drop again, and so on (The Ladders eye-tracking study PDF). It's the same pattern Jakob Nielsen documented for web reading in 2006 — humans don't read dense text, they skim it.
On a resume, that means the density of attention is concentrated at the top-left. Everything to the right of the F, and everything below the third or fourth bullet, is effectively unread on the first pass.
The Ladders study also found that the best-performing resumes had:
- Simple, single-column layouts
- Clear section headers and bold job titles
- Bulleted accomplishments, not sentences
- Plenty of white space
And the worst-performing resumes had:
- Cluttered layouts
- Multiple columns
- Long sentences
- Missing or weak section headers
- No white space
None of this is surprising once you've seen the eye-tracking heatmaps. A two-column resume forces the recruiter's eye to fight the F-pattern. A wall-of-text bullet is unread after the fourth or fifth word. A weak job title header is invisible.
What this means, line by line
If you only get an F-pattern and ~11 seconds, here's what each zone of your resume needs to do.
The top strip (sweep #1) — your name, title, and one-line pitch.
This is the most-read real estate on the page. Do not waste it on "123 Main St, phone, email, LinkedIn, GitHub, personal website, Twitter." Recruiters don't need your street address in the first sweep. They need to know who you are and what you do in four words. Example: "Jane Doe — Backend Engineer (Go, distributed systems)". Contact links can go on a second line, smaller.
Sweep #2 — your most recent job title and company.
Bold the title. Put the company and dates on the same line, right-aligned if you want, but don't hide the title. The single biggest mistake junior candidates make here is front-loading the company name ("Acme Corp — Software Engineer Intern") when the role is what the recruiter's eye is actually hunting for. Flip it. Software Engineer Intern — Acme Corp.
The left margin drop (F-pattern descent).
This is where bullets live. The recruiter's eye is dropping down the first 3–5 characters of each bullet. That means the first two words of every bullet have to carry the bullet. Not "Responsible for building…" or "Worked on a team that…" — those first words are dead weight in an F-pattern scan. Lead with a verb and a number: "Shipped checkout redesign, +18% conversion." "Built internal tool, saved ~6 engineer-hours/week."
The partial right-sweep (into each bullet).
The recruiter's eye enters the bullet, reads roughly the first 5–8 words, and bails if it doesn't see a result. That's it. So: verb → what → quantified outcome, in that order, in under 12 words. If the bullet runs onto a second line, the second line is essentially unread on the first pass. Rewrite until it fits on one.
Below the fourth bullet of your top job.
Statistically, mostly unread on the first pass. Use this zone for supporting detail that rewards the second pass (the 1:34 review), not for anything load-bearing. If your best accomplishment is bullet #6 of your most recent role, move it to bullet #1. Seriously.
The audit: take 11 seconds on your own resume
Open your resume. Start a timer. Look at it for exactly 11 seconds, trying to skim in an F-pattern. Then close it and write down, from memory:
- What role is this person applying for?
- What's their most recent job title?
- What's the most impressive thing they've done?
- Is there a number anywhere?
If you can't answer all four from memory, a recruiter can't either — and your resume is getting filtered out before anyone reads the good parts.
The bigger picture
All of this optimization is downstream of a harder truth: in a market where CS grad unemployment is at 6.1%, degrees awarded have more than doubled since 2013, and recruiters are drowning in 300–500 applications per role (Final Round AI), even a perfectly F-pattern-optimized resume is just a ticket to the next round of filtering. It's necessary. It's not sufficient.
The thing that's actually sufficient — in the 11-second world — is sending something besides a resume. A short demo, a company-specific proposal, a pre-built proof you understood the role. That's what breaks out of the pile instead of trying to win it. We've written about that here and here, and it's the entire reason Jobloom exists: research → company-aware proposal → tailored working demo → short recorded walkthrough.
But fix the resume first. 11 seconds is all you get on the first pass. Make every one of them land on the left margin.