A practical guide
Plenty of useful work does not come with a percentage. You can still show what changed, what you did, and what the team did, without inventing a figure to make the line look finished.
"Responsible for the platform." "Worked on reporting." "Helped with the roadmap." Lines like these are common on a tech CV or resume because the job really did contain those duties, and because nobody handed you a tidy result. A reviewer still cannot see what changed because you were there. Advice that says every bullet needs a percentage then pushes people to invent one. A made-up figure is worse than a plain sentence. It is a claim you may be asked to defend.
Keep thisIf you did not count it, do not print it. A true change in the work is stronger than a percentage you reverse-engineered.
Job Bank, the Government of Canada's employment service, tells applicants to show achievements rather than only list duties, and to use real numbers where they have them. It also warns against vague lines such as being "responsible for" an improvement, and against overstating results. The number is welcome when it is firm. It is not a costume for work that was real in another way.
01
A duty is the work the role exists to do. An achievement is a change in that work which you can describe: something became faster to understand, a repeated failure stopped, a decision held without a fresh meeting, a colleague could do a thing that used to require you, a risk was named before it shipped. The change does not need a unit. It needs a before and an after that a stranger can picture.
If the honest after is "the work continued as it always had", you have a duty. Put the duty in a short line so the role is recognisable, and do not dress it as a triumph. Most jobs are mostly duties. You are looking for the few moments when your judgement changed the outcome, not for a way to inflate the rest.
Three tests keep the sentence honest:
This is the same evidence a supporting statement needs, and the same evidence an interview will ask you to talk through. If you are writing to published criteria, the supporting statement guide shows where each example sits. If you are deciding whether a thin match is worth an application, apply, clarify, or skip comes first. Do not manufacture an achievement to fill a gap.
02
Sit with one role, not your whole career. Answer in notes. You are collecting material, not drafting the CV yet. Skip any prompt that does not bring a real scene back.
Twenty minutes on one job is enough to find two or three scenes. More time usually produces padding. When a scene is fuzzy, look for the trace before you write the bullet. Memory inflates. The ticket does not.
03
The left-hand line is the sort of duty statement that fills a CV and tells a reviewer almost nothing. The right-hand line is one true change. These are illustrative. They are models for shape, not details you should borrow.
Duty lineResponsible for the onboarding of new engineers.
What changedWatched two new engineers get stuck on the same access token, then wrote the steps down. The next starter shipped a small fix in their first week without asking three people where to begin.
There is no percentage. There is a repeated snag, an action, and a difference the next time. If the next starter still got stuck, you do not get to write the last sentence. You write the smaller truth: you documented the token steps after seeing two people hit them.
Duty lineResponsible for weekly reporting for the operations team.
What changedReplaced a Monday spreadsheet that three managers edited by hand with one query and a short note on what had changed. The meeting started from the note instead of from reconciling three versions.
You do not need to claim the meeting became "50 per cent shorter" unless you timed it and are happy to say how. "Started from the note instead of from reconciling versions" is something you saw. If you did time it, and you trust the timing, then the number can go in. Inventing the timing because the sentence looks bare is the failure this guide is trying to prevent.
Duty lineResponsible for the roadmap and stakeholder communication.
What changedCut two promised features after sitting in on support calls, and wrote the reason in a note sales could send without booking a new meeting each time a customer asked.
The achievement is the cut and the note, not "owned the roadmap". A roadmap is a duty. A decision that other people could explain without you is a change. If sales still called you for every conversation, say what you did write, and stop before the claim about the meetings.
The National Careers Service, the government's careers advice service in England, describes STAR as situation, task, action, and result. On a CV the result can be a sentence, and the situation can be a clause. You do not need the full four-part story in every bullet. You do need the action to be yours and the result to be real. Keep a longer version of the same scene for an interview. The bullet is the reminder, not the script.
04
"We" is the honest pronoun when the work was shared. It becomes useless when the reader cannot see what you did. Hiring managers in tech expect shared systems. They still need your slice, because they are hiring you and not the team.
Use two beats. Name the team result in plain language, then the piece that was yours. Do not attach the team's outcome to your name, and do not shrink your piece into "supported" or "helped" if you can say the action.
Too vagueWe improved reliability across the checkout service.
Too muchI improved reliability across the checkout service.
Yours and theirsFailed releases were interrupting checkout. I added a check that blocked a deploy when the migration had not run, and I wrote the rollback note the team used the next time a release failed.
Illustrative. If you did not add the check, do not take it. If you do not know whether releases failed less often afterwards, do not say they did. "I added a check and wrote the note" can stand on its own. The team's wider result can stay with the team.
The same split applies when the work was a pair, a squad, or a project with an agency. "Partnered with" is a start only if the next clause is a verb you performed: wrote, decided, queried, cut, documented, refused, shipped. If your contribution was attendance, say you took part and do not reach for a result.
05
Use a number when you counted it, a stranger can understand it without a private dashboard, and you are willing to be asked how you counted. Good raw counts are often already in the work: how many people used the runbook, how many services the on-call rota covered, how often the report went out, how many engineers you unblocked, how long a task took before and after you timed both. Job Bank's point stands. A real count is easier to trust than a vague improvement.
Leave the number out when:
Percentages are a particular trap, because they look precise and hide the base. "Cut failed jobs" is weaker than "failed jobs on that pipeline went from most mornings to rare", if that is what you observed, and it is stronger than "reduced failures by 40 per cent" if you never calculated 40. Do not convert a hunch into a ratio on the way to the page.
If you rewrite a set of bullets, keep the old CV labelled and send one version at a time. Otherwise you cannot tell whether clearer evidence is what led to interviews. Rewriting the lines does not require a new tool. Comparing them does require not mixing the versions up.
For the file itself, put the new lines in ordinary text, under a role a person can scan. The screening software guide covers layout. Evidence that sits in a graphic is evidence a reviewer may never see.
06
Pick one role. Answer the prompts in notes, then rewrite three duty lines. Copy the sheet or print it and write on the lines. If a line needs a number you do not have, stop and write the change in words.
Job title and employer, as they should appear on the CV.
What people stopped asking, what I wrote down, what broke and what changed, or what I said no to.
The verb I performed. The result I will not claim.
A ticket, note, query, or release. Not attached. Just real.
07
Then write a clear duty, with the tools and the scope, and stop. "Built and maintained the internal admin API in Python and PostgreSQL" tells the truth. Adding "which transformed efficiency" tells a story you do not have. One honest duty line is safer than three inflated ones.
Only if you can say from what, to what, in language you believe. "Reduced" with no from and to is a shrug. "The Monday meeting stopped opening with three conflicting spreadsheets" is a reduction you witnessed.
No. A role needs enough duty for a stranger to see what the job was, and a few lines that show judgement. Four achievements and no description of the work is as thin as a list of duties. Two strong changes beside a plain scope is a good shape.
Yes, when you state it as the team's and then say what you did inside it. No, when you place the figure next to "I" and you could not reproduce the count or defend your share of it.
08
Sources checked 10 November 2026. Write only what you could say to someone who saw the work.