← Back to Blog
· WriteCV Team · 10 min read

How Recruiters Scan Resumes in 6 Seconds (What They Look For)

The exact order recruiters follow during a first-pass scan - and how to make the top third of your resume do all the work.

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 the trash. (For the full breakdown, see our 2026 resume statistics roundup.)

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 on recruiter behavior reveals a consistent scan pattern. Recruiters don't read top-to-bottom like a document. They jump between specific zones.

What Recruiters Look At (In Order)
1
Name and current title - Who is this person and what level are they? Takes about 1 second. If there's no clear title or headline, the recruiter has to figure it out themselves. Most won't.
2
Current company and job title - Where do they work now and what's their role? Recruiters look for recognizable company names and titles that match the open position. About 1-2 seconds.
3
Previous company and title - Career trajectory check. Are they moving up, lateral, or down? Is there a pattern of progression? About 1 second.
4
Skills section scan - Quick keyword check. Do they have the technical stack or domain experience the role requires? About 1 second.
5
Education - Degree, school name, graduation year. For senior roles this gets barely a glance. For new grads it carries more weight. About 0.5-1 second.
6
First bullet of the most recent role - If all the above checked out, the recruiter reads one bullet to gauge quality. This single bullet determines whether they continue reading or move on.

Notice what's not on the list: your summary paragraph (most recruiters skip it), your older roles, your hobbies, your "references available" line. The scan is brutal and efficient.

What Makes a Resume "Instantly Credible"

Credibility isn't about having a perfect background. It's about signal density - how much useful information the recruiter absorbs per second of scanning.

Four things create instant credibility:

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 your headline says "Experienced Software Professional," they have to guess - and guessing costs time they don't have.

Low Credibility
Alex Martinez
Passionate software developer with experience across the full technology stack
High Credibility
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. The first communicates nothing a recruiter can use. For more headline approaches, see our resume headline examples.

2. Recognizable Company Names or Clear Context

If you worked at Google, that company name does heavy lifting. But most people didn't work at FAANG companies - and that's fine. You just need to add context.

No Context
Software Engineer · Acme Corp · 2022-Present
Clear Context
Software Engineer · Acme Corp (B2B SaaS, 200 employees, Series C) · 2022-Present

The parenthetical tells the recruiter: this is a growth-stage B2B company, not a 3-person garage startup and not a Fortune 500 bureaucracy. That context shapes how they interpret everything below.

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. If it's a vague responsibility statement, it registers nothing.

No Signal
Responsible for developing and maintaining backend services and APIs
Strong Signal
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 tells the recruiter something about scale and competence - without them having to read carefully.

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, consistent formatting, and enough white space to let the structure breathe.

This isn't about design. It's about scannability:

Fix Your Top Third: The Checklist

The top third of your resume is everything above the fold - what a recruiter sees without scrolling or looking past the halfway point of the page. This zone determines whether they keep reading.

Top-Third Checklist
Name is the largest text on the page - no logos, no photos, no decorative elements competing for attention
Headline matches the target role - use the exact job title from the posting, not a creative variation
Contact info is one line - city, email, LinkedIn, GitHub. No street address, no phone number paragraph
Skills section is visible without scrolling - if skills are at the bottom of page 2, most recruiters never see them
Most recent job title and company are prominent - bold title, clear company name, dates right-aligned or clearly separated
First bullet contains a number - revenue, users, latency, percentage improvement, team size, anything measurable
No objective statement - replace with a one-line headline or a 2-sentence summary that names your specialty and top result
Enough white space - the top third doesn't feel cramped. There's breathing room between sections.

If your resume passes every item on this checklist, you've optimized for the 6-second scan. The recruiter's eye will land on your name, confirm your level, check your stack, read one strong bullet, and move you forward.

Examples: Strong Top Thirds

Here are three examples of resume top-thirds that survive the 6-second scan.

Example 1: Senior Software Engineer

Jordan Kim
Senior Software Engineer · 7 years · React, TypeScript, Node.js, AWS
Seattle, WA · [email protected] · linkedin.com/in/jordankim
Skills
Frontend: React, Next.js, TypeScript, Tailwind CSS, React Query
Backend: Node.js, Express, PostgreSQL, Redis, GraphQL
Cloud & Tools: AWS (ECS, Lambda, S3, CloudFront), Docker, GitHub Actions, Datadog
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 without infrastructure changes
  • Built real-time notification system processing 500K events/day with WebSockets and Redis pub/sub...

What works: the headline immediately says "Senior Software Engineer, 7 years, React/Node/AWS." The skills section confirms depth. The first bullet has three numbers and shows a migration - a senior-level project. A recruiter knows within 4 seconds that this person is qualified.

Example 2: Product Manager

Priya Sharma
Senior Product Manager · 5 years · B2B SaaS, Growth, Data-Driven
San Francisco, CA · [email protected] · linkedin.com/in/priyasharma
Experience
Senior Product Manager · Metric Labs (analytics platform, 50K+ users)
2023 – Present
  • Owned product roadmap for the 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 and activation flows, improving 7-day retention from 34% to 47%...

What works: headline states the exact role, tenure, and domain. Company context (analytics platform, 50K+ users) tells the recruiter the scale. First bullet has a revenue number. Second bullet has a retention metric. Every element earns its space.

Example 3: New Grad / Early Career

Maya Chen
Software Engineer · Python, React, PostgreSQL · CS @ UC Berkeley 2025
Berkeley, CA · [email protected] · 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
  • Designed and implemented PostgreSQL migration script handling 2M+ records with zero-downtime cutover...

What works: the headline packs role, stack, and school into one line. Even as an intern, the first bullet has numbers (40% reduction, 12-person team). The company name (Stripe) does heavy lifting here, but the quantified impact would work even without a recognizable brand.

For more complete resume examples, see our software engineer resume examples guide.

What Kills a Resume in 6 Seconds

Instant Rejection Triggers
1. No clear job title. If the recruiter can't tell what role you're targeting within 1 second, you're done. "Dynamic professional seeking new opportunities" says nothing.
2. Wall of text. Dense paragraphs with no visual hierarchy. The recruiter's eye bounces off and moves to the next resume.
3. Buried current role. If your most recent job isn't visible in the top third - because you have a 6-line summary, a skills block, certifications, and volunteer work above it - the recruiter never finds what matters.
4. First bullet is a responsibility. "Responsible for managing team projects and deliverables" is a job description, not an achievement. The recruiter sees no evidence of impact and stops reading.
5. Inconsistent formatting. Mixed fonts, random bold/italic, uneven spacing. It signals carelessness. Recruiters notice this unconsciously - the resume just "feels wrong."
6. Photos, logos, or graphics. Decorative elements distract from content and break ATS parsing. Clean text always wins.

The Second Pass: What Happens After 6 Seconds

If your resume survives the first scan, the recruiter spends another 20-30 seconds on a second pass. Here's what changes:

But here's the key insight: the second pass only happens if the first pass succeeded. Everything you optimize should focus on the 6-second scan first. The detailed reading comes later.

The Summary Question

Should you use a summary? It depends on whether your summary does work or takes up space.

A good summary replaces the headline by packing role, specialization, and top achievement into 1-2 sentences. A bad summary is a generic paragraph that a recruiter skips entirely.

Skip This
Highly motivated and results-driven software engineer with a proven track record of delivering innovative solutions in fast-paced environments. Passionate about clean code and continuous learning.
This Works
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. For more examples, see our resume summary examples guide.

Make the Scan Work for You

You can't control how long a recruiter spends on your resume. But you can control what they see in those 6 seconds. The formula is simple:

  1. Clear title that matches the role
  2. Recognizable company or context that establishes credibility
  3. Skills visible without scrolling
  4. First bullet with numbers that prove impact
  5. Clean layout with visual hierarchy

Get these five things right and you've done more than 90% of applicants. The recruiter's eye will find what it's looking for - and your resume makes it to the next round.

Related Resume Examples

Browse all 400+ resume examples →

See how your resume scores

Upload your resume and get an instant ATS compatibility score with actionable improvement suggestions.

Start building your
interview-winning resume

Optimize your resume, improve your ATS score, and land more interviews with WriteCV.