What Recruiters Actually Read on Your Resume (And What They Skip)

The often-cited figure is that recruiters spend six to eight seconds on a resume during the first pass — verify the current research before publishing, but the order of magnitude is right. That number gets quoted to scare candidates, but it shouldn't. Six seconds is plenty of time if your resume is built for how recruiters actually read it.

The problem is most resumes are built for how candidates think recruiters read them. Those are different things.

What the first pass actually looks like

When a resume comes across our desk — whether through an ATS, a referral, or a direct application — the first scan answers three questions, in this order:

Is this person in the right ballpark for the role? Title, current employer, years of experience. If the answer is no, the resume goes in the maybe-later pile and we move on.

Does anything jump off the page? A recognizable employer. A specific accomplishment with a number attached. A skill listed in the job description. A credential that matters for the role.

Is there a reason to keep reading? This is the question that decides whether the resume gets a real read or a polite pass.

Notice what's not on that list. We're not reading your objective statement. We're not parsing your soft-skills section. We're not weighing whether your hobbies make you well-rounded. Not in the first pass, and often not in the second either.

What gets read

Job titles get read. Always. They're the fastest signal of where you've been and where you might fit. If your title doesn't reflect what you actually did — say, your company called you a "Solutions Specialist" but you were really running operations — that's worth a conversation with your manager about getting it formally updated, or a clarifying line beneath the title.

Company names get read, especially recognizable ones. If your last employer is a name we know, that's a credibility shortcut. If it isn't, a one-line description of the company helps — "regional logistics firm, 200 employees" tells us more than the company name alone.

Bullets with numbers get read. "Managed inventory" gets skimmed. "Reduced inventory variance from 8% to 1.5% across three warehouses" gets read twice. The number doesn't have to be impressive in absolute terms — it has to be specific. Specificity signals that you actually did the thing, rather than describing what your job was supposed to involve.

The most recent role gets the deepest read. Older roles get progressively less attention. This is why front-loading your strongest, most relevant experience matters more than chronological purity. If your most impressive work was three jobs ago, the resume needs to surface that early — in the summary, in a "selected accomplishments" section, somewhere above the fold.

What gets skipped

Objective statements. Almost always. They tell us what you want, and at the first-pass stage we're trying to decide whether to invest more time in you. A short professional summary that tells us what you bring is a different animal and worth keeping.

Generic skills lists. "Microsoft Office. Team player. Strong communicator." These take up space without adding signal. If a skill matters for the role, it should appear in the context of how you used it.

Long paragraphs. Anywhere. The format itself signals that we'll have to work to extract the information, and at six seconds, we won't.

References. We assume you have them. If we want them, we'll ask.

Anything older than fifteen years, in most cases. Your first job out of college matters less and less as your career progresses. If it's not load-bearing for the story your resume is telling, let it go.

What gets your resume passed over

Three things, mostly.

Typos and formatting inconsistencies. Not because we're pedants, but because the resume is the work sample. If you didn't catch that "manger" should be "manager," what does that say about the attention you'd bring to the actual job?

A mismatch between the resume and the role. If you're applying for a senior analyst position and your resume reads like a junior coordinator's, we assume you misread the posting. We don't assume you're being modest.

Unexplained gaps or job-hopping without context. The gap itself isn't disqualifying — life happens, and most recruiters know it. But unexplained gaps invite assumptions, and assumptions usually trend negative. A one-line note ("relocated for spouse's job," "caregiving for family member," "completed certification program") closes the loop.

The rewrite that matters

If you're going to spend an hour on your resume this week, spend it on two things.

First, read your most recent role description as if you were a stranger. Does it tell that stranger what you actually did, what changed because of you, and what scale you operated at? If not, rewrite the bullets until it does.

Second, look at the job posting for the role you most want. Pull out the five most important phrases — the ones that appear in the requirements and qualifications. Then check whether those phrases, or close equivalents, appear naturally in your resume. If they don't, you're invisible to both the ATS and the recruiter.

Everything else is polish. These two things are the work.

Stat to verify before publishing:

• Six-to-eight second resume review figure (originally from a Ladders study, often updated — check current research)