The 6-Second Rule: What Recruiters Actually Look At First

You spent hours on your resume. The recruiter spends seconds on it.

Multiple recruiting studies — including eye-tracking research from The Ladders — have found that recruiters spend an average of six to eight seconds scanning a resume before deciding whether it’s worth a second look. Not reading. Scanning. In that window, they’re not evaluating your career story. They’re pattern-matching against a mental checklist: right title, right companies, right timeline, right keywords.

If your resume doesn’t pass that first scan, it doesn’t matter how strong your experience actually is. It gets set aside before anyone reads the details.

Here’s what that scan actually looks like for a data role, and how to design your resume around it.

What recruiters look at, in order

Eye-tracking studies consistently show the same scan pattern, and it’s not top-to-bottom, left-to-right like you’d expect. It’s more like an F-shape:

Your name and current/most recent title — Does this match what they’re hiring for?
Your most recent company and dates — Is this person currently employed? How long did they stay?
Your most recent bullet points — just the first line or two of each
A quick drop down to your skills section — do the tools match the job posting?

Everything else — your earlier roles, your education, your certifications — gets a glance at best on the first pass. It only gets real attention if the top third convinces the recruiter you’re worth a closer look.

This means the top third of your first page is doing almost all the work. If you’re a Data Engineer with your strongest pipeline-architecture project buried in bullet four of your second job, it’s functionally invisible on the first scan.

Designing your resume around the scan, not against it

1. Your title needs to match the job, not just describe your last role

If you were called “Software Engineer II” but did data engineering work, and you’re applying to Data Engineer roles, that title mismatch can cost you the first scan entirely. Recruiters are pattern-matching on titles fast — they’re not stopping to read your bullets to figure out you actually did the job.

Fix: Use a professional title header at the top of your resume — separate from your actual job title in your work history — that states your target role clearly. “Data Engineer | Python, Spark, Airflow, dbt” tells the scanner exactly what to expect before they read a word further.

2. Front-load your strongest bullet, every time

Recruiters read the first line of each bullet point far more carefully than the rest. If your first bullet under a role says “Maintained internal documentation for team processes” and your third bullet says “Rebuilt the core ingestion pipeline, cutting processing time by 40%,” you’ve buried your best evidence where it won’t get seen on the first pass.

Fix: Under every role, order bullets by impact, not chronology. Lead with the outcome that best proves you can do the job you’re applying for.

3. Make your most recent role earn its space

Your most recent job gets read the closest. If you’ve been in that role for two-plus years, it should have your most bullets and your strongest numbers. If your most impressive project happened three roles ago, that’s a sign your resume’s structure — not your experience — is the problem, and you may need to pull that achievement into a “Selected Projects” section near the top instead of leaving it buried in job three.

4. Keep your skills section scannable, not encyclopedic

A wall of 35 tools, frameworks, and languages doesn’t get read — it gets skipped. Recruiters scan skills sections looking for a handful of specific terms from the job posting, not evaluating your full toolkit.

Fix: Group your skills so the ones most relevant to the role you want are first and easiest to spot — for example, listing core languages and frameworks before secondary or “familiar with” tools, rather than one long undifferentiated list.

5. Don’t make them hunt for your dates

Employment dates are one of the first things scanned, because they answer “is this person currently employed, and did they stay anywhere long enough to matter?” If your dates are buried in a small font on the far right, or inconsistent in format across roles, you’re adding friction to a decision that’s already being made in seconds.

Fix: Keep date formatting consistent and clearly visible next to every role — not hidden, not tiny, not a different format for each job.

The bigger point: design for the skim, then reward the read

None of this means dumbing down your resume or removing detail. It means structuring it so the most convincing information is visible in a skim, so you earn the closer read where your full experience gets to matter. A resume that only works if someone reads every line is a resume that mostly doesn’t work at all, because most recruiters never get past the scan.

Once you’ve passed the seven-second test, the rest of your resume — your full project history, your earlier roles, your certifications — gets to do its job. But it only gets that chance if the top third holds up first.

Want the mechanics behind why resumes get filtered before a human even sees them? See our guide on how ATS parsing actually works.