How to Write CV Achievements That Prove Your Impact
A duty tells a reader what your job contained. An achievement lets them picture what changed because you were there.
Most CVs describe work accurately and still undersell it. “Managed deployment pipelines” may be true, but it leaves the reader with no sense of scale, difficulty, or result. Strong achievement bullets tell a short, checkable story: what was wrong, what you changed, and what improved.
Start with the change, not the task
A task is an assignment. An achievement is the outcome of making a decision inside that assignment. Ask: what was slower, riskier, more expensive, or less reliable before I touched it?
Shows impact: Cut the nightly data refresh from 90 to 22 minutes by rebuilding 41 duplicated SQL views as tested dbt models.
Only names a duty: Maintained SQL views and data refresh jobs.
Use the problem → action → result pattern
You do not need a dramatic story. One sentence is enough when each part earns its place. Name the problem briefly, make your contribution clear, then attach the result to the thing it measured.
- Problem: what constraint, failure, backlog, or uncertainty existed?
- Action: what did you personally decide, build, change, or lead?
- Result: what moved—time, cost, reliability, volume, quality, adoption, or risk?
Numbers make a claim easier to trust
Use numbers you can defend. Counts, percentages, time saved, revenue protected, users served, incidents reduced, and deadlines met are all useful. A rough number is acceptable when you label it honestly; an invented precision is not.
Keep the story yours
A CV achievement should survive a follow-up question. If a team delivered the result, say what you owned. If the number belongs to a wider programme, do not imply you produced it alone. Credibility is more valuable than a larger-looking bullet.
Accurate ownership: Led the migration plan for 12 services; the team completed the cutover with no customer-visible downtime.
Overclaims: Migrated the entire platform with zero downtime.
Tailor which achievements appear first
You do not need to rewrite every bullet for every application. Put the two or three achievements closest to the target job near the top of the relevant role, then keep supporting evidence underneath. Relevance is often a structural edit before it is a wording edit.
Need a tighter opening paragraph first? How to write a CV summary
Using AI for wording without inventing experience: AI resume bullet points, honestly
Use your existing CV as the source, then check which achievements prove the target job’s requirements. Review your CV
Before you send it
- Does each bullet say what changed, not only what you were responsible for?
- Can you explain every number in a screening call?
- Is your personal contribution clear when the result was shared?
- Are the most relevant achievements visible in the first screen?
Frequently asked questions
How many achievements should a CV include?
Usually two to four strong bullets per recent role. Fewer specific achievements are easier to read and defend than a long list of vague responsibilities.
What if my work had no measurable result?
Use a concrete proof point: scale, audience, deadline, system adopted, process replaced, or risk removed. Do not invent a percentage.
Should every CV bullet be an achievement?
No. A role still needs enough context to show what you did. Prioritise achievement-led bullets for work most relevant to the target job.