How to Write Resume Bullets That Prove Impact, Not Duties
Read most resumes and you'll see the same pattern. "Responsible for managing the deployment pipeline." "Worked on the customer onboarding flow." "Involved in migrating services to the cloud."
Every one of those tells the reader what the job was. None of them tells the reader whether you were any good at it.
Once your resume can be parsed, and once it's tailored to the posting, the bullets are where you actually make your case. This post is about writing them so they prove something.
Duties vs impact
A duty describes the role. Anyone who held the same title could write it. An impact bullet describes what changed because you were there.
- Duty: Responsible for the deployment pipeline.
- Impact: Rebuilt the deployment pipeline, cutting release time from two hours to fifteen minutes and letting the team ship daily instead of weekly.
Same job. Only one of them gives a hiring manager a reason to call you.
A simple structure: action, scope, result
Most strong bullets follow the same shape:
- Action: a specific verb for what you did. Built, led, redesigned, reduced, launched, automated.
- Scope: what you did it to, and how big it was. A service handling 2 million requests a day. A team of six. A £400k budget.
- Result: what changed. Faster, cheaper, more reliable, more revenue, fewer complaints.
You don't need all three in every line, but a bullet with none of them is almost always a duty.
"But I don't have numbers"
This is the most common objection, and it's usually not true. You may not have revenue figures, but you probably have some of these:
- Time: how long something took before and after.
- Volume: how many users, requests, tickets, reports or customers.
- Frequency: daily instead of weekly, every release instead of every quarter.
- Scale: team size, number of services, size of the codebase or budget.
- Before and after: "replaced a manual process" is a result even without a percentage.
Estimates are fine as long as you can explain them. "Roughly 30% faster" is honest if you can say in an interview how you know. A precise number you can't back up is worse than no number at all.
Strong verbs, without the thesaurus
"Responsible for", "worked on", "helped with" and "involved in" are the four phrases that most often signal a duty. Replace them with what you actually did. If you led it, say led. If you built it, say built. If you contributed one part of a bigger project, name the part: "designed the caching layer for", not "helped with".
Don't swap in impressive-sounding words just for variety. "Spearheaded" and "orchestrated" add nothing that "led" doesn't, and a page full of them starts to read like a template.
Before and after
- Before: Worked on the reporting dashboard.
After: Built a self-serve reporting dashboard that replaced 12 weekly manual reports for the finance team. - Before: Responsible for customer support tickets.
After: Resolved 40+ support tickets a week and wrote the help articles that cut repeat questions by a third. - Before: Involved in cloud migration.
After: Migrated four legacy services to Azure, retiring on-premise hosting and reducing outages during peak trading.
How many bullets, and in what order
Three to five bullets for recent roles is usually enough; older roles can drop to one or two. Put the strongest bullet first. When you're tailoring, "strongest" means the one that best answers the posting's top requirement.
Getting it done faster
Rewriting every bullet on your resume is slow, and it's hard to judge your own work. When you score your resume against a job in ResumeLens, the suggestions work at bullet level: the original line, a proposed rewrite, and the reason for the change. You keep what's accurate and reject what isn't.
Whichever way you do it, the test is the same as always. Could you explain this bullet out loud in an interview, with the details to back it up? If yes, keep it. If not, rewrite it until you can.