Hiring managers and recruiters spend about 7 seconds on your CV before deciding whether it's worth a proper read. In those 7 seconds they're scanning for proof (real titles, real numbers, real outcomes), and if they can't find it, your application goes in the no pile before anyone reads it properly.

So if you've been tweaking your CV, sending tailored applications and still not getting picked for interviews, this is almost certainly why. And it's got nothing to do with hacking the ATS.

In 11 years in executive search, I've sat across the table in more than 10,000 interviews and reviewed more than 50,000 CVs. Here's what actually happens in the first few seconds after you hit submit, and how to make sure your CV survives them.

How long do hiring managers spend reading a CV?

At first, they don't read it at all. They skim it, and that skim takes about 7 seconds.

I don't mean they read it quickly. I mean they literally give it a pass in around 7 seconds, and those 7 seconds decide whether you're worth a deeper look or you go in the no pile.

Whatever you put in front of them in those 7 seconds is the whole decision.

Everything else on that page might as well not exist.

Think about the last time you were on a dating app. You're not studying each profile.

You're scanning for two seconds, maybe less, and you're not really looking for a reason to say yes. You're looking for one reason to swipe left and move on.

A recruiter or hiring manager with your CV is doing exactly the same swipe. It's fast, it's unsentimental, and they're hunting for the reason to move you along.

What do recruiters look for in the first 7 seconds of a CV?

They're looking for objective markers: real titles, real numbers, real outcomes and proof that you made something happen.

But most CVs give them the opposite. They get a wall of responsibilities and passive words like "responsible for", "involved in" or, worse, "I helped to".

Here's the thing. A list of responsibilities reads as a risk, because it tells them you were near the work, but not what you actually made happen or achieved.

Take a line like this, which turns up on most CVs:

Responsible for managing a team and improving performance.

Now read it the way a stranger would, in two seconds. It's nothing, right?

It could be written by anyone, for any job. It could be true or it could be completely invented, and they've got no way to tell, so it reads as a risk.

Now take the same person, in the same job, written objectively:

Led a team of eight and cut the defect rate by 22% in six months.

Suddenly there's something to hold on to: a number, an outcome, proof. That's not a bigger claim. It's the same work, written so a stranger can see it.

Objective proof beats subjective process every time.

Which CV phrases get you rejected?

The phrases that get you rejected are the ones that describe your job instead of what you did in it.

  • "Responsible for..." says you were there. It doesn't say you were good.
  • "Involved in..." tells them you were around the project, not what part you played in it.
  • "Helped to..." leaves them wondering who actually did the work.
  • "A demonstrated history of working in..." is the worst offender of the lot.

Please promise me, if you've got "a demonstrated history of working in..." on your CV or your LinkedIn profile, go and delete it right now. Replace it with a proper human sentence about what you've actually done.

Why can't I see what's wrong with my own CV?

You can't see what's wrong with your own CV because you read what you meant to say, not what's actually on the page.

That's the second reason your applications get deleted. Knowing the fix (swap responsibilities for proof) and being able to spot the problem in your own CV are two completely different things.

You've got all the context and the backstory, so you don't see the ambiguity in what you've written. You read "responsible for delivering complex projects" and your brain naturally fills in the gaps: the late nights, the project that nearly went under, the results you turned around, all the blood, sweat and tears that went into that work.

The stranger reading it for 7 seconds sees a passive, subjective sentence that doesn't say what you did.

You're literally reading a different CV to the one they're reading.

So when you sit there editing it, you can't tell which lines are proof and which are noise, because every line feels important to you. Each one carries your sweat equity, and that's the part you can't fix on your own.

What you need is an outside read: someone who only sees what's actually on the paper, the same way a hiring manager would.

That's the whole reason I built the Six Figure CV tool. You upload your CV and it reads it the way a hiring manager does, in seconds, with none of your emotional attachment. It shows you where you're vague, where you're signalling risk and where you've buried the proof that would get you interviews.

Want the objective read you can't give yourself? Score your CV free with Six Figure CV.

Do I need big achievements on my CV if I'm early in my career?

No. Proof was never about seniority. It's about being specific.

I know what some of you are thinking. "That's fine for senior executives with big teams and a P&L, but I'm two years into my career. I haven't run anything huge, so does this even apply to me?"

Thinking that way is the biggest mistake you can make here. Yes, a CEO proves it with a major turnaround or a P&L number, but someone two years in proves it just as well with a real, relevant outcome, like this:

Rebuilt the onboarding documentation and cut new-hire ramp-up time from six weeks to three.

That's proof. It's specific, it's objective, and a stranger can hold on to it in 7 seconds.

The scale changes, but the rule doesn't. Whether you're running a company or you're two years in, they're scanning your CV for exactly the same thing: did this person actually make something happen, or were they just there in the building?

And if you're worried you haven't got any numbers, think about this. Someone working at McDonald's has KPIs. If they've got numbers, so have you.

Nobody gets to skip proof. You've just got to go and find yours.

How do I rewrite my CV so it passes the 7-second scan?

Rewrite every line so it says what you did and proves what changed because of you.

One Line, One Proof is Daniel Langley's rule that every line on your CV must say what you did and prove what changed because of you.

Here's how to put it into practice.

  1. Go through your CV and mark every line that starts with "responsible for", "involved in", "helped" or "worked on". Those are your first rewrites.
  2. For each one, ask yourself what was broken or missing when you arrived, and what it looked like when you left.
  3. Find the number. Your annual reviews, your dashboards, Jira, release notes, sprint reports and your own memory are where it lives.
  4. Put the outcome early in the line, so it shows up in a skim. "Cut the defect rate by 22%" catches the eye, whereas "worked across several teams on quality initiatives" doesn't.
  5. Lead your most recent role with your strongest proof, because that's where most of the 7 seconds get spent.

You've already done the work. It's just not on your CV yet.

What are the most common CV mistakes that cost you interviews?

Most of the CVs that get deleted make one of these five mistakes.

  1. Trying to hack the ATS. Your applications aren't getting deleted because of some keyword trick you haven't cracked yet. They're getting deleted because a person skimmed and found no proof. Spend your time on proof, not hacks.
  2. Listing your duties. Most people hiring already know what goes into a software engineer, customer success or project manager role. Cut the duties and show what you achieved while doing them.
  3. Burying your best result. If your biggest win sits in bullet seven of your third job, it doesn't exist in a 7-second skim. Move it to the top.
  4. Proofreading your own CV and calling it done. You'll fill in the gaps every time. Get an objective outside read before you send it.
  5. Thinking you're too junior for proof. The scale doesn't matter. The specifics do.

The bottom line

Hiring managers spend about 7 seconds on your CV, and in that time they're scanning for proof, not a list of responsibilities. There is no hack, and there never was.

The only real hack is doing genuinely good work in your career and putting it on your CV in a way a stranger can read in seconds.

What's your next step?

If you want to see how your CV holds up before your next interview, try the free Six Figure CV tool. Upload your CV and get an instant score with specific fixes.

And if you want to work on this with me directly, here's where to start.