What a Hiring Manager Sees in 30 Seconds

Thirty seconds is generous

I spoke with a hiring manager who's been reviewing resumes for twelve years across three companies. Engineering manager, then director, now VP. Conservatively, she's reviewed over 5,000 resumes. I asked her to walk me through exactly what happens when she opens one.

"Thirty seconds is what I tell people because it sounds reasonable," she said. "The truth is, most resumes get about six to ten seconds on the first pass. I'm not reading. I'm scanning. I'm looking for three or four signals that tell me whether to read more carefully or move on."

The first three seconds: visual pattern

Before she reads a single word, she registers the shape of the document. Is it dense or spacious? Is the formatting consistent? Does it look like a professional document or a wall of text?

"If I open a resume and my eyes don't know where to go, I'm already in a bad mood. Dense paragraphs with no bullet points, inconsistent spacing, three different font sizes -- those aren't content problems, they're presentation problems. And they make me less likely to give the content a fair read."

The resumes that pass this first scan are clean, well-structured, and easy to navigate. They use consistent formatting, reasonable margins, and clear section headers. Nothing fancy -- just organized.

Seconds three through ten: the scan pattern

After the visual check, she follows a consistent scan path. It's not top-to-bottom. It's more like this:

1. Current or most recent job title and company. "This tells me immediately whether this person is at roughly the right level. If I'm hiring a senior engineer and the most recent title is 'Junior Developer,' I'll still read more -- but I'm already wondering about the fit."
2. How long they were there. She glances at the dates. Two-plus years at the most recent role is neutral. Under a year gets a mental note. Over five years with the same title gets a different mental note.
3. The first bullet point under the most recent role. "This is the most important line on the entire resume. If the first bullet is generic -- 'Responsible for managing projects' -- I'm probably done. If it's specific -- 'Led a 6-person team that shipped a payment processing system handling $2M in daily transactions' -- I'm reading the rest."
4. A quick scan down the left margin. She looks at the progression of companies and titles. Is there a coherent career trajectory? Do the companies signal anything (industry experience, company size, brand recognition)?

That's ten seconds. By this point, she's made an initial keep-or-skip decision. About 70% of resumes don't make it past this stage.

What makes her keep reading

I asked her to describe the resumes that survive the ten-second scan. What separates the 30% she keeps reading from the 70% she doesn't?

Specificity. "I want numbers. Revenue, users, team size, percentage improvements, timeline -- anything that grounds the work in reality. 'Improved system performance' means nothing. 'Reduced API latency from 800ms to 120ms, improving user retention by 4%' means everything."

Relevance. "I can tell within seconds whether someone tailored their resume for this role or sent the same thing to 50 companies. If I'm hiring for a backend engineer and the first three bullets are about frontend work, the candidate might be perfectly qualified -- but they're not showing me that."

Clarity. "I shouldn't have to decode your resume. If I'm spending mental energy figuring out what you actually did, I'm spending less energy being impressed by it. Simple, direct language wins every time."

What she skips entirely

Some sections that candidates agonize over barely register during a first-pass scan:

• The objective or summary statement. "I skip these 90% of the time. Most of them are generic fluff. The rare ones that actually say something specific and interesting -- those I read. But I'm not starting there."
• Education (for experienced candidates). "If you have 10 years of relevant experience, I don't care where you went to college. I'll look at education for new grads, but for mid-career and senior candidates, it's almost irrelevant."
• Skills lists without context. "A list that says 'Python, Java, SQL, AWS' tells me you typed those words. It doesn't tell me you can actually use them. I'd rather see those skills embedded in your work experience bullets."
• Hobbies and interests. "I'm sure your marathon running is impressive, but it's not helping me decide whether to interview you."

The things that make her wince

After 5,000 resumes, certain patterns trigger an immediate negative reaction:

Buzzword soup. "Visionary thought leader with a passion for synergistic solutions" -- she's seen variations of this hundreds of times. "These words mean nothing. They tell me the candidate either doesn't know what they actually do, or they think I'm impressed by jargon. I'm not."

Unexplained job hopping. "Three companies in three years without progressively better titles or a clear reason for moving. I'm not ruling them out, but I'm going to ask about it, and the answer better be good."

Typos in prominent places. "A typo in the third bullet of your fourth job? I probably won't notice. A typo in your job title or your summary? That tells me something about attention to detail."

Obvious mismatches. "If you're applying for a data science role and your most recent experience is in retail management with no bridge between the two -- no coursework, no projects, no explanation -- I'm confused about why you applied."

What she actually wants to see

I asked her to describe her ideal resume. Not a dream candidate -- just a well-built resume for a qualified person.

"Clean layout. One page for under 10 years of experience, two pages if needed for more. A headline or current title that matches the role they're applying for. Three to five bullet points per role, each one specific and quantified where possible. A skills section that's honest, not aspirational. No graphics, no photos, no progress bars. And for the love of everything, consistent date formatting."

It sounded simple. It is simple. And yet, she estimated that fewer than 20% of the resumes she reviews meet all of those criteria.

The part that should reassure you

Here's the thing she said that stuck with me most: "I'm not looking for reasons to reject people. I'm looking for reasons to interview them. When I open a resume, I'm hoping it's good. I want it to be the one. My job gets easier when I find strong candidates quickly."

She's not the adversary. The thirty seconds aren't a judgment -- they're a filter. And the filter is looking for exactly what you'd expect: clear evidence that you can do the job, presented in a way that's easy to find.

That's the whole game. Make it easy for the person on the other side to say yes.