Recruiters don't read resumes. They scan them. Eye-tracking studies consistently show the first pass takes 6-7 seconds. In that window, a recruiter decides whether your resume goes into the "maybe" pile or gets skipped.
This isn't laziness. A recruiter reviewing 200 applications for a single role literally cannot read each one. They've trained themselves to spot patterns - and your resume either matches those patterns or it doesn't.
Here's what they actually look at, in what order, and how to make sure your resume survives the scan.
The 6-Second Scan Order
Eye-tracking research reveals a consistent scan pattern. Recruiters don't read top-to-bottom. They jump between specific zones.
| Order | What They Look At | Time |
|---|---|---|
| 1 | Name and current title | ~1 second |
| 2 | Current company and job title | ~1-2 seconds |
| 3 | Previous company and title (career trajectory check) | ~1 second |
| 4 | Skills section scan | ~1 second |
| 5 | Education | ~0.5-1 second |
| 6 | First bullet of most recent role | Determines if they keep reading |
Notice what's not on the list: your summary paragraph (most recruiters skip it), your older roles, your hobbies, your "references available" line.
What Makes a Resume "Instantly Credible"
Credibility is about signal density - how much useful information the recruiter absorbs per second.
1. A Clear Title That Matches the Role
If a recruiter is hiring a "Senior Backend Engineer" and your headline says "Senior Backend Engineer," that's an instant match. If it says "Experienced Software Professional," they have to guess.
| Low Credibility | High Credibility |
|---|---|
| Alex Martinez - Passionate software developer with experience across the full technology stack | Alex Martinez - Senior Backend Engineer · 6 years · Python, Go, AWS, distributed systems |
The second version communicates role, seniority, tenure, and core stack in one line.
2. Recognizable Company or Clear Context
You don't need FAANG on your resume. You just need to add context for companies that aren't household names.
| No Context | Clear Context |
|---|---|
| Software Engineer · Acme Corp · 2022-Present | Software Engineer · Acme Corp (B2B SaaS, 200 employees, Series C) · 2022-Present |
The parenthetical tells the recruiter: this is a growth-stage B2B company. That context shapes how they interpret everything below it.
3. Numbers in Your First Bullet
The first bullet of your most recent role is the single most-read sentence on your resume after your name and title. If it contains a number, the recruiter's brain registers impact.
| No Signal | Strong Signal |
|---|---|
| Responsible for developing and maintaining backend services and APIs | Built REST API layer serving 2M requests/day across 12 microservices, reducing p95 latency from 340ms to 90ms |
The second version contains four numbers. Each one signals scale and competence without requiring careful reading.
4. Visual Clarity and White Space
Dense wall-of-text resumes fail the scan because the eye has nowhere to land. Recruiters need visual anchors.
- Section headers should be bold or uppercase - visible from arm's length
- Job titles and company names should be visually distinct from bullet text
- Bullets should be 1-2 lines, not 3-4 line paragraphs
- Margins should be at least 0.5 inches
Fix Your Top Third: The Checklist
The top third of your resume is everything above the fold - what a recruiter sees without scrolling. This zone determines whether they keep reading.
- ☐ Name is the largest text on the page
- ☐ Headline matches the target role - use the exact job title from the posting
- ☐ Contact info is one line - city, email, LinkedIn, GitHub. No street address.
- ☐ Skills section is visible without scrolling
- ☐ Most recent job title and company are prominent
- ☐ First bullet contains a number - revenue, users, latency, percentage, team size
- ☐ No objective statement - replace with a one-line headline or 2-sentence summary
- ☐ Enough white space - the top third doesn't feel cramped
Examples: Strong Top Thirds
Senior Software Engineer
Jordan Kim
Senior Software Engineer · 7 years · React, TypeScript, Node.js, AWS
Seattle, WA · jordan@email.com · linkedin.com/in/jordankim
Skills
Frontend: React, Next.js, TypeScript, Tailwind CSS, React Query
Backend: Node.js, Express, PostgreSQL, Redis, GraphQL
Cloud: AWS (ECS, Lambda, S3, CloudFront), Docker, GitHub Actions
Experience
Senior Software Engineer · StreamLine (B2B SaaS, Series B) | 2022 - Present
- Led migration of monolithic Rails app to React + Node.js microservices,
reducing page load time by 60% and supporting 3x user growth
- Built real-time notification system processing 500K events/day...
What works: headline says "Senior Software Engineer, 7 years, React/Node/AWS" instantly. First bullet has three numbers and shows a migration - a senior-level project.
Product Manager
Priya Sharma
Senior Product Manager · 5 years · B2B SaaS, Growth, Data-Driven
San Francisco, CA · priya@email.com · linkedin.com/in/priyasharma
Experience
Senior Product Manager · Metric Labs (analytics platform, 50K+ users) | 2023 - Present
- Owned product roadmap for core analytics dashboard - shipped 4 major features
in 12 months that increased paid conversion by 22% ($1.8M ARR impact)
- Ran 15 A/B tests across onboarding flows, improving 7-day retention from 34% to 47%
What works: company context (analytics platform, 50K+ users) establishes scale. First bullet has a revenue number. Second has a retention metric.
New Grad
Maya Chen
Software Engineer · Python, React, PostgreSQL · CS @ UC Berkeley 2025
Berkeley, CA · maya@email.com · github.com/mayachen
Experience
Software Engineering Intern · Stripe | Summer 2024
- Built internal tool for payment dispute resolution that reduced manual review
time by 40% for a team of 12 operations specialists
- Implemented PostgreSQL migration script handling 2M+ records with zero-downtime cutover
What works: headline packs role, stack, and school into one line. Even as an intern, the first bullet has numbers. Quantified impact works with or without a recognizable brand.
What Kills a Resume in 6 Seconds
- No clear job title - "Dynamic professional seeking new opportunities" says nothing
- Wall of text - dense paragraphs with no visual hierarchy; the recruiter's eye bounces off
- Buried current role - if your most recent job isn't in the top third, the recruiter never finds it
- First bullet is a responsibility - "Responsible for managing team projects" is a job description, not an achievement
- Inconsistent formatting - mixed fonts, random bold/italic, uneven spacing signals carelessness
- Photos, logos, or graphics - distract from content and break ATS parsing
What Happens After 6 Seconds
If your resume survives the first scan, the recruiter spends another 20-30 seconds on a second pass:
- Reads 2-3 more bullets from recent roles, looking for consistent impact
- Checks tenure - how long you stayed at each company
- Looks for gaps - unexplained gaps longer than 6 months get noticed
- Checks skills match more carefully - not just the right category, but specific tools
But the second pass only happens if the first pass succeeded. Optimize for the 6-second scan first. Everything else comes later.
The Summary Question
Should you use a summary? Only if it does work.
| Skip This | This Works |
|---|---|
| "Highly motivated and results-driven software engineer with a proven track record of delivering innovative solutions in fast-paced environments." | "Backend engineer specializing in high-throughput APIs and distributed systems. Most recently built the payment processing pipeline at Acme (12M transactions/month, 99.99% uptime)." |
If you can't write a summary with specific numbers and a clear specialization, skip it and use a one-line headline instead.
The Formula
You can't control how long a recruiter spends on your resume. But you can control what they see in those 6 seconds.
- Clear title that matches the role
- Recognizable company or context that establishes credibility
- Skills visible without scrolling
- First bullet with numbers that prove impact
- Clean layout with visual hierarchy
Get these five things right and you've done more than 90% of applicants.
Want to see how your resume scores on these exact dimensions? WriteCV gives you an honest ATS score with per-bullet feedback in 30 seconds.
Top comments (0)