Why Your Resume Gets Rejected in 6 Seconds (And How to Fix It)
Recruiters spend only seconds on an initial resume scan, and Ladders' eye-tracking research shows where their attention tends to land. The six fixation points, the myth debate, and how to prepare for both scans.
- ats
- job boards
- resume tips
There's a stat that gets thrown around a lot: recruiters spend 6 seconds looking at your resume. Published eye-tracking research puts that first look at only a few seconds, and what happens in those seconds can shape whether a fuller read follows.
But here's a point that often gets overlooked: those seconds aren't random. In Ladders' eye-tracking studies, recruiters' attention followed a recognizable pattern. Once you understand what they tend to look for, and where, you can design your resume to survive that initial glance.
Is the 6-Second Resume Scan a Myth?
No — but the number is slightly off, and the skeptics deserve a straight answer. The "6 seconds" figure comes from Ladders' 2012 eye-tracking study of professional recruiters; when Ladders re-ran the research in 2018 with improved methodology, the measured initial scan was 7.4 seconds. So if you want to be precise: the initial triage scan is real, measured, and takes about seven seconds — not six. (Most articles quoting this stat still say "6" and cite nothing; now you know where the number actually comes from.)
What the skeptics get right: seven seconds is the triage scan, not the whole evaluation. Resumes that survive triage get a real read later — often several minutes. What the skeptics get wrong: concluding the scan doesn't matter. It's the gate everything else sits behind. A resume optimized for the deep read but not the scan may never get the deep read.
What Do Recruiters Look At First? (The 6 Fixation Points)
Ladders' 2012 eye-tracking study reported that recruiter attention isn't spread evenly — roughly 80% of the initial scan landed on six data points:
- Your name
- Current job title and company
- Previous job title and company
- Start and end dates of your current role
- Start and end dates of your previous role
- Education
In the eye-tracking research this post draws on, everything else — the summary, the skills section, hobbies — was skimmed in an F-shaped pattern (a sample-bound finding, not a rule for every recruiter): a horizontal sweep across the top, a shorter sweep below it, then a quick vertical scan down the left edge. In practice, recruiters often look at, roughly in this order:
- Your current or most recent job title — Does it roughly match the role being hired for?
- The company name — Is it recognizable? Is it in a relevant industry?
- Dates — How long were you there? Are there gaps?
- The first 2-3 bullet points under that role — Do they signal relevant experience?
That's the short version. If the top third of your resume doesn't hold a recruiter's attention, the rest may get far less of it.
The Five Fastest Ways to Get Rejected
1. Your job titles don't match
If the role says "Senior Software Engineer" and your resume says "Technology Specialist III," your relevant experience can be harder to recognize in a quick scan. Your company may have used unusual internal titles, but a recruiter skimming for familiar titles may not stop to decode them.
Fix: Use the market-standard title. If your official title was "Technology Specialist III" but you functioned as a Senior Software Engineer, write it as "Senior Software Engineer (Technology Specialist III)" so both the recognizable title and the official one are visible. Employers and background checks can verify titles, so keep the official one in and don't claim a title you didn't hold.
2. Your bullets lead with responsibilities, not results
A common pattern (illustrative example): "Responsible for managing a team of 5 engineers and overseeing sprint planning."
That tells a reader what your job description said. It doesn't tell them what you actually did. Compare:
"Led a 5-person engineering team that shipped the company's payment processing system 3 weeks ahead of schedule, reducing transaction failures by 40%." (Illustrative example only. Use achievements and figures that are true for you.)
Same role, different signal: the second version points to something concrete that was delivered. Numbers aren't mandatory, but a figure you can back up helps. Only use figures you can substantiate. For example, "Reduced churn by 15%" (illustrative) says more than "worked to improve customer retention."
3. The formatting is fighting the reader
This isn't about "creative" resumes with infographics and pie charts, which are best avoided. It's about basic readability. Two-column layouts can trip up some ATS parsers. Dense paragraphs instead of bullets make scanning harder. Tiny fonts used to cram everything onto one page can read as a sign that information hasn't been prioritized.
Fix: Single column. Clear section headers. 10.5-11pt font minimum. Bullet points, not paragraphs. If it doesn't fit on one page (two max for senior roles), cut the oldest and least relevant experience. Very old, unrelated experience rarely helps.
4. You're keyword-stuffing (or keyword-missing)
Many ATS support keyword search, and recruiters often search on terms from the job description. Some candidates respond by jamming every possible keyword into a "Skills" section at the bottom. The ATS might score you well, but the recruiter who pulls up your resume sees a wall of buzzwords with no context, which can cost you credibility.
The other extreme is also a problem: not having the keywords at all. If the job requires "Kubernetes" and your resume says "container orchestration" but never mentions Kubernetes by name, a literal keyword search may miss it.
Fix: Use keywords naturally within your bullet points. "Migrated 12 microservices to Kubernetes, reducing deployment time from 45 minutes to under 4 minutes." (Illustrative example only; use real figures.) That's a keyword match and a result, which serves both a keyword search and a human reader.
5. There's no clear narrative
This one is subtle, but it can make the difference between a resume that is merely accurate and one that is easy to follow. Your resume should tell a story of upward momentum. Each role should build on the last. If you went from Software Engineer to Senior Engineer to Tech Lead, that's a clear arc. If you went from Software Engineer to Marketing Coordinator to Data Analyst to Project Manager, the recruiter is going to wonder what you actually want to do.
Career changes are fine — but your resume needs to frame the transition intentionally. A brief summary at the top (2-3 lines, not a paragraph) can bridge the gap: "Data analyst with 4 years of engineering experience, bringing a builder's mindset to analytics and business intelligence."
The ATS Layer
For applications routed through an Applicant Tracking System, your resume passes through it before a recruiter sees it. These range from sophisticated (Greenhouse, Lever) to very basic. Here's what trips people up:
- PDF vs. Word: Most modern ATS systems handle PDFs fine. But if you're applying to older, enterprise companies, a .docx is safer. When in doubt, submit both if the system allows it.
- Headers and footers: Some parsers skip content in headers/footers. Put your name and contact info in the body of the document, not the header.
- Tables and text boxes: These frequently get parsed out of order or ignored entirely. Avoid them.
- File naming: Name your file "FirstName_LastName_Resume.pdf" — not "resume_final_v3_REAL.pdf." Recruiters may handle many files, so a clear name helps.
For the full treatment — including the "75% auto-rejected" myth and what ATS ranking actually does — read the complete ATS guide.
How to Pass Both Scans: Human F-Pattern + ATS
The resume that wins is one artifact optimized for two different readers. The good news: their demands barely conflict.
For the 7-second human scan (F-pattern): - Put the six fixation points where the eyes land: clean header, market-standard current title, recognizable company framing, tight dates — all in the top third - Lead each role with your 2-3 strongest result bullets; the F-pattern's left-edge scan catches bullet openings, so front-load the outcome (for example, "Reduced deployment time by [your real figure]%…" rather than "Worked on a project that…") - One page of visual calm: single column, real white space, consistent headers
For the ATS scan: - Mirror the posting's exact keywords inside those same result bullets — context plus match - Standard section names, no tables or text boxes, text-based PDF or .docx - Both acronym and long form on first use
Run a quick check with the free ATS Score tool. It estimates ATS-style compatibility with a heuristic score and points out possible formatting and keyword issues; it cannot confirm how any employer's parser will read your resume. If per-job tailoring is the bottleneck, the AI Resume Builder can suggest bullet rewrites for a specific posting. Review every suggestion and keep only what is true.
The One-Page Myth
If you're early career (roughly under 5 years of experience), one page is a sensible starting point. You may not have enough relevant experience to justify more, and padding it out with filler can work against you. Follow any length guidance in the posting.
If you're mid-to-senior (7+ years), two pages is often fine. What can hurt you is a two-page resume where the second page is filler. Every line should earn its spot.
Three pages? Usually only for fields that expect long histories, such as academic, medical or federal applications. Otherwise, follow the employer's instructions and keep it shorter.
What Actually Matters
After all this, the most important thing about your resume is also the simplest: make it easy to say yes. The recruiter is looking for reasons to move you forward — or reasons to skip you. Don't give them reasons to skip. Match the language of the job description. Lead with your strongest, most relevant experience. Quantify what you can, using only figures you can back up. Keep it clean and scannable.
Your resume doesn't get you the job. It gets you the interview. That's its main job, so optimize for that first.
Related Articles
What Is a Good ATS Score? How to Read a Resume Score
An ATS score describes how well software can read your resume and match it to one job description. Here is how to read the number, what moves it, and what it cannot tell you about an employer's decision.
How to Beat ATS Systems in 2026: The Complete Guide
Learn how Applicant Tracking Systems work in 2026, how resumes can get filtered (and why the 75% auto-reject claim doesn't hold up), and practical strategies to optimize your application.