What a Hiring Manager Actually Thinks in the First 6 Seconds of Reading Your Resume

Six seconds. That is the number researchers at TheLadders found when they tracked eye movement patterns as recruiters reviewed resumes. Six seconds before they decide whether to read further or move on.

I have spent years on the other side of that decision. I have reviewed resumes for roles across tech, finance, and operations — hundreds at a time during active hiring cycles. And I can tell you: the six-second figure is accurate, but it undersells how much happens in that window. In six seconds, an experienced hiring manager forms a hypothesis about you that will colour everything they read next.

Here is exactly what that process looks like — from the inside.

The 4-Signal Scan: What We Actually Look At

A hiring manager scanning a resume is not reading it. They are pattern-matching against a mental template of what a successful candidate for this role looks like. That template is built from the last three people who succeeded in this role, the job description they wrote, and years of intuition about what signals quality.

The eye goes to four places, in roughly this order:

1. Current title and company.This is the first thing. Before your name fully registers, I am looking at what you are doing right now and where. Not because company prestige is everything — it is not — but because it sets context. It tells me your current level, the type of environment you come from, and whether you are a step up, a lateral move, or a step down for this role. If your current title is “Senior Analyst” and I am hiring a “Director,” I am already doing math about the gap. If your company is a direct competitor or a well-known name in our space, you have my attention. If neither, I keep reading to understand what you actually did.

2. Summary line.Not every resume has one. The ones that do have a 3-second window to earn further reading. The worst summaries are the adjective-heavy ones: “Passionate, results-driven leader with a proven track record of exceeding expectations.” I have read this sentence ten thousand times. It tells me nothing and costs you my goodwill. The best summaries are specific: “10 years in B2B SaaS sales, consistently top 10% quota attainment, closed 3 enterprise deals over $2M in the last 18 months.” That one earns the next thirty seconds.

3. First two bullets of the most recent role.This is where most candidates lose the battle. The first bullet is the most important sentence on your resume. It should be your biggest achievement in that role, quantified, specific, and clearly relevant to the job I am hiring for. Instead, most resumes lead with a duty: “Responsible for managing the sales pipeline and coordinating with internal stakeholders.” That tells me what you were supposed to do. I do not care what you were supposed to do. I care what you actually accomplished.

4. Skills section. A quick scan for technical or domain keywords that I know are required for the role. If we need someone with Salesforce, Python, or IFRS knowledge and it is not visible in your skills section within the first pass, I may assume you do not have it — even if it is buried in a bullet point three roles ago. The skills section is a scanning aid. Use it as one.

What Happens After the 6-Second Scan

If those four signals all check out — right level, compelling summary, strong first bullets, required skills visible — then I give you the two-minute read. This is where the rest of the resume gets scrutinised. And at this stage, a different set of questions takes over.

Does the career trajectory make sense? A logical progression — whether upward, lateral, or deliberately narrowed — signals intentionality. What I am looking for is coherence. Why did you move from company A to company B? The resume itself will not answer that question, but if the moves look erratic or unexplained, I start asking it. Unexplained gaps, sudden drops in title, and four companies in three years all generate internal questions that you will have to answer in the phone screen. A well-structured resume anticipates these questions and provides enough context to neutralise them.

Is there evidence or just assertion?I am looking for the ratio of facts to claims. “Strong communicator” is a claim. “Presented quarterly strategy reviews to C-suite for three years” is evidence. “Collaborative team player” is a claim. “Led cross-functional project with six departments, delivered on time” is evidence. The more evidence, the more credible the resume. The more claims without evidence, the more sceptical I become.

Are the metrics credible?This one is subtle but important. I have become very good at sniffing out metrics that do not add up. If a mid-level marketing manager claims to have “increased revenue by $50M,” I want to understand the mechanism. If a junior developer says they “saved the company $2.3M annually,” I am curious how. Not because I think candidates lie — most do not — but because AI tools and over-eager resume writers inflate and distort numbers routinely. When I see a metric that seems large for the role level, I make a note to probe it. Candidates who cannot explain their own numbers in an interview fail fast.

Do I recognise myself or my best people in this candidate? This is the most honest and least comfortable part of the process to admit. Every hiring manager has a mental model of what success looks like in their team. Some of that is legitimate pattern-matching: people who have worked in similar environments, handled similar problems, built similar systems. Some of it is bias. The best hiring managers work hard to separate the two. But the pattern-matching is real and it affects decisions. If your background mirrors someone who has succeeded in this organisation, that works in your favour.

The Specific Things That Stop Me Mid-Scan

These are the things that make me slow down — not always to reject, but to flag for further investigation.

Unexplained short tenures. One role under a year is fine — layoffs happen, startups fold, circumstances change. Two or three short tenures in a row raises a question. I am not necessarily going to reject you for it, but I am going to ask about it. If your resume does not give me any context, the narrative I construct in my head may not be the one you would choose.

Generic language in the summary. As I mentioned: if your summary sounds like it could be for any role in any industry, it is doing nothing for you. A strong summary is role-specific. It references the kind of work I am hiring for, not just the general category of professional you consider yourself to be.

No dates on education. Some candidates remove graduation dates to obscure age. I understand why. But the absence of dates draws more attention than the dates themselves. An experienced hire with a 1998 graduation date is not going to be rejected for that reason — but a mysteriously undated degree makes me wonder what you are hiding.

Duties disguised as achievements.“Managed a team of five engineers” is a duty. “Managed a team of five engineers to ship a complete platform rewrite in eight months with 40% fewer bugs than the previous version” is an achievement. The difference is what happened as a result of your management. Every bullet should answer: what did you do AND what was the result?

Obvious keyword stuffing.I know what ATS optimisation is. I know candidates add keywords to get past automated screening. What I cannot forgive is when the keyword stuffing is so heavy that the bullets stop making grammatical sense. “Leveraged agile methodologies to drive stakeholder-aligned outcomes via data-driven cross-functional collaboration” is a sentence that contains four keywords and no meaning. If your resume reads like that, I assume you used an AI tool and did not bother to edit it.

How to Write a Resume That Passes the 6-Second Test

Understanding the scan is half the battle. Here is how to engineer your resume around it.

Lead with your most relevant title.If you have held multiple roles, ensure the most relevant one is at the top. If you have the right title but a less recognisable company, consider adding a brief context line: “Apex Analytics — B2B data platform, 200-person scale-up (Series B).” This gives me the frame I need to evaluate your experience correctly.

Make the first bullet your best bullet. Do not build up to your biggest achievement. Lead with it. If the most impressive thing you accomplished in your last role was item three on your bullet list, move it to item one.

Write a role-specific summary.Not “dynamic leader,” but “Head of Growth with 8 years in early-stage SaaS, three 0-to-1 product launches, Series A to C experience.” If your summary could be submitted to three different roles unchanged, it is not specific enough.

Keep skills visible and scannable. A simple bulleted or comma-separated list near the top or bottom of your resume. Do not bury technical skills inside experience bullets where they can be missed on first pass.

Pre-answer the narrative questions.If you have a gap, a short tenure, or an industry change, a single line of context can do more work than you realise. “Left to care for a family member — returned to work full-time in March 2025” or “Startup acquired by Oracle — role eliminated in restructure” closes the question before I have to ask it.

The Uncomfortable Truth About Subjectivity

Here is what resume guides rarely admit: hiring decisions have a subjective element that no amount of keyword optimisation can fully overcome. The hiring manager's own career trajectory, their team's current dynamics, the internal candidate they are comparing you against, the mood they are in — all of these factors influence the reading.

What you can control is everything structural: the quality of your evidence, the clarity of your trajectory, the relevance of your language, the strength of your opening. Make it impossible to say no on the structural grounds. Then the subjective factors have less room to work against you.

A well-crafted resume does not guarantee an interview. But a poorly crafted one — one that loses the 6-second scan — guarantees you will not get one, regardless of how good you actually are.

This is why we built the Hiring Manager Persona feature in Resume Builder. After the AI tailors your resume, you can run it through a simulated hiring manager review — modelled on the specific archetype of person who would fill the role in the job description. It gives you the kind of first impression, concerns, and phone screen questions a real hiring manager would likely raise. Not to game the process, but to spot the weaknesses before the real person does.