Most people write their CV the way they would write a timeline.
Start at the beginning. List what they did. Move forward in time. End with the most recent role. Maybe add some bullet points under each job. Maybe bold a few things. Send it off.
That approach produces an accurate document. It is not, however, a useful one.
The purpose of a CV is not to record your career. It is to make an argument. The argument is: I am the right person for this specific role, and here is the evidence.
When you write a timeline, you leave the argument up to the reader. Most readers will not make it. They will skim, see nothing that immediately connects to what they are looking for, and move on.
Why the record approach fails
A record tells the reader what you did. A positioning document tells the reader what you can do — at the level this role requires, in the context this organisation operates in, with the specific type of impact they need.
Those are different documents. They use the same raw material, but they organise it differently, emphasise different things, and cut different things.
The record approach keeps everything because everything happened. The positioning approach cuts anything that does not serve the argument — even impressive things, even things you are proud of.
That is counterintuitive. But it is the difference between a CV that gets read and one that does not.
What an argument looks like in practice
Take this bullet point: "Managed a team of five and oversaw delivery of the annual report."
That is a record. It says what you did. It does not tell the reader anything about the quality of the outcome, the scale of the challenge, or what it required of you specifically.
Now take this: "Led a team of five through the organisation's first fully digital annual report, coordinating across three departments to a board deadline. Delivered ahead of schedule despite a mid-project change in the reporting framework."
That is the beginning of an argument. It says: I manage people, I navigate cross-functional complexity, I deliver under pressure, and I adapt when conditions change. Those are the things the reader can assess against the job description.
The role of the job description
Every version of your CV should be built in relation to a specific job description. Not a generic version of the role — that specific job description, at that specific organisation, at that specific level.
Read the job description. Identify the three to five things they most need from the person in this role. Then ask yourself: what in my history is the most compelling evidence of each of those things?
That evidence is what goes in. Everything else is context, filler, or distraction.
What to cut
Cut chronology that predates your relevant experience. If you are applying for a senior management role, your Saturday job at seventeen is not doing any work. It is just taking up space and making the reader scroll further.
Cut responsibilities that were standard for your grade. If everyone at your level managed a budget, saying you managed a budget is not a differentiator. It is noise.
Cut anything that does not connect to the role you are applying for. You might have done extraordinary work in a context that is entirely unrelated to this job. That work still belongs on your CV — but it needs fewer words than the work that directly speaks to what this employer needs.
The test for a strong bullet point
For each bullet point on your CV, ask: if someone read only this line, would they know what changed because of you?
Not what you were responsible for. What changed. What improved. What was delivered. What risk was managed. What decision was made well.
If the answer is no — if the bullet point could have been written without you in it — rewrite it.
Your career happened. Your CV should be evidence that it mattered.