To write achievements on a CV, make every line say what you did and prove what changed because of you. A line that only describes the job says you were there, but it doesn't say whether you were any good.
That's the one thing stopping most people landing interviews. Your CV describes what you do, instead of proving how well you do it.
I've reviewed more than 50,000 CVs (or resumes, if you're in the States) in 11 years in executive search. And I know you know how good you are at what you do, so it hurts watching someone with less experience land the interviews you should be getting.
In this article, I'll show you the rewriting method that turns every line into proof, how to find that proof even when you're convinced you haven't got any, and what hiring managers actually respond to.
Why isn't my CV getting interviews when I have the experience?
Your CV isn't getting interviews because it describes the job instead of proving your impact. The person reading it already knows what the job involves. What they don't know is whether you're any good at it.
I think most people write their CV on autopilot. You sit down and list what you've done: responsible for managing a team, responsible for delivering projects, responsible for stakeholders.
And look, I get it. Nobody's ever shown you how to write a CV, so you write down what you know, and what you know is doing the job.
For a long time, that worked. Your CV was a career history document that said "I've done X, Y and Z", you ticked the boxes, and you got the interview.
But hiring's changed. The market's changed, and competition is fiercer than ever. For every role you apply for, there are hundreds of project managers, software developers and consultants going for it, all with the same titles, the same duties and the same bullet points.
"Responsible for managing a team" says you were there. It doesn't say you were good.
What separates you is the results. So your CV isn't a career history document anymore. It's a proof document, and right now, it probably isn't proving anything.
Not sure if yours is? Run it through the free Six Figure CV tool. It scores your CV in about a minute and shows you exactly where it's falling short.
How do you turn job duties into achievements on a CV?
You turn job duties into achievements by rewriting each line so it does two things: says what you did, and proves what changed because of you. I call it One Line, One Proof.
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. If a line can't do the second part, it doesn't make the cut.
Let me show you what that looks like. This is what most CVs say:
Responsible for managing the rollout of a new customer booking system.
Here's the same line with One Line, One Proof:
Managed the rollout of a new customer booking system, cutting customer complaints by 30% in the first quarter.
The first one says you were there. The second one says you were good.
That's the rule, and anyone can use it, whatever your level and whatever your job. Go through your CV line by line, and for each one ask, "What changed because of me?" If you can't answer it, rewrite the line or cut it.
How should senior professionals write achievements on a CV?
Senior professionals should make every CV line show three things: how big the responsibility was, what changed, and the number that proves it. I call this the Proof Triangle.
The more senior you are, the higher the stakes, and the more a hiring manager needs to see before they'll take the risk on you.
The Proof Triangle is Daniel Langley's method for senior CV lines: every line shows how big (the budget, team or users you were in charge of), what changed (before you versus after you), and the number that proves it.
Here's an example:
Led a team of six engineers rebuilding the checkout for 2 million users, cutting failed payments by 40% in three months.
- How big: six engineers and 2 million users. That's the scale.
- What changed: cutting failed payments.
- The number: 40% in three months. That's the proof.
Take any side away, and the triangle falls over. Without the scale, the result looks small. Without the change, it's just a job description. And without the number, it's just a claim.
How do you write CV achievements if you don't have any numbers?
Every job has numbers, even if you've never been asked for them. Even the job with the least responsibility in the world has KPIs, some kind of performance measure, and some kind of before and after.
This is where most people get stuck. Not because they don't know they need proof, but because they've convinced themselves they haven't got any.
Now, I know what some of you are thinking.
"But Dan, I haven't got any numbers. I'm not in sales. Nothing I do is measurable."
Think about someone working in McDonald's. They're measured on how many meals they served, how short the wait time was, and how many orders they completed per hour.
If they've got numbers, so have you.
- Developers: uptime, load times, bugs fixed, features shipped.
- Project managers: on time, on budget, and how many people actually used what you delivered.
- Consultants: renewals, retention, or revenue from your clients.
You're not trying to compare yourself to the CEO. You're trying to show why you're the best at what you do, whatever that might be.
Of course, the more senior you are, the bigger those numbers get. But they are there. You've probably just never gone looking for them.
Where do you find the numbers to put on your CV?
You'll find the numbers for your CV in your annual reviews, your dashboards, your project tools and your own memory of what changed. Start with the documents your company already keeps on your performance.
- Your annual reviews and performance objectives
- Your dashboards and reports
- Jira, release notes and sprint reports
- Your own memory
For that last one, ask yourself one question for every role: what was broken when you arrived, and what did it look like when you left?
The gap between those two answers is your proof. Put a number on it wherever you can, even a rough one like "around 20%" or "from weekly to daily".
Can you put achievements on your CV if you're not allowed to share the numbers?
Yes. You might not be able to share sensitive company information, and that's fine, but you can always talk about your own performance, your own metrics, your own KPIs and your own results.
People tell me, "I'm not allowed to share those numbers." And look, that's nonsense.
Use percentages instead of revenue figures, improvements instead of absolute totals, and team or project size instead of company financials. "Grew renewals by 18%" proves your impact without giving away a single confidential figure.
The other thing people say is, "It feels like bragging." I get that.
But it isn't bragging if it's true. It's evidence.
You're not doing it for your ego. You're proving to the person reading your CV that you're worth interviewing, and you're making their decision easier.
What do hiring managers look for on a CV?
Hiring managers look for proof that you're the lowest-risk person to hire. Companies don't hire the best candidate, they hire the lowest-risk one, and your proof is what makes you lower risk.
Let me show you with someone I worked with. He was a digital transformation lead, and he came highly recommended. The word of mouth was the same from everyone: this guy was brilliant.
Then I read his CV, and I was far from impressed. There was no data and no proof, just a long, boring list of things he was responsible for.
Now think about that. I knew he was good at what he did, and his CV still didn't convince me. So what chance did he have with a hiring manager who'd never heard of him?
But that's who's reading your CV: someone with no background, no context, and no understanding of who you are, how good you are, or what you've done.
So we sat down together and went through his projects: what they looked like before, what they looked like after, the metrics, the data and the evidence. We rewrote his CV around it, and he got hired into a six-figure role.
Same person. Same experience. The only thing that changed was the proof.
What are the most common mistakes when writing CV achievements?
The most common mistakes all come back to describing the job instead of proving the result. Here are the ones I see most, with the fix for each.
- Starting lines with "Responsible for". Fix: start with what you did, then add what changed because of you.
- Listing duties the reader already knows. Fix: assume they know the job. Tell them how well you did it.
- Leaving out the scale. Fix: add the team size, budget or number of users so the result has context.
- Saying you have no numbers. Fix: check your reviews, dashboards and reports, and ask what was broken when you arrived and how it looked when you left.
- Hiding results to avoid bragging. Fix: if it's true, it's evidence. Put it on the page.
The bottom line
Your CV isn't a career history document anymore. It's a proof document, and every line should say what you did and prove what changed because of you.
You've already done the work. It's just not on your CV yet. Put the proof there, and getting interviews stops feeling like luck and starts feeling a bit like cheating.
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.