How to Write Resume Bullet Points With Metrics

The structure

Verb + what you did + how + the result. The result is the part that makes it a bullet worth reading; the 'how' is what makes it credible.

Where numbers hide in any job

• Volume — how many of the thing you handled per day, week or year
• Time — how long it took before and after you changed it
• Money — cost, revenue, budget, savings, spend you controlled
• People — team size, stakeholders, users, customers, students
• Quality — error rate, defect count, complaints, satisfaction, audit findings
• Frequency — releases, campaigns, reports, cycles you ran
• Range — geographies, branches, product lines, systems

Estimating honestly

You won't have exact figures for work from four years ago, and nobody expects an audit. Reconstruct defensibly: if you handled roughly 15 tickets a day for two years, '~7,000 tickets' is fair. Use approximation markers ('about', '~') and never state a precise-looking number you can't explain.

When there's genuinely no number

Some work resists measurement. Then use scope or consequence instead: what would have gone wrong without you, who depended on it, what changed structurally. 'First person in the team to document the deployment process; it's still the runbook used for every release' has no percentage and is a strong bullet.

How many bullets per role

Three to five for your current role, two to three for the one before, one or two for older ones. A role from eight years ago with six bullets signals that you peaked early.

Start with the right verb

Built, rebuilt, led, owned, cut, raised, shipped, negotiated, automated, migrated, recovered. Avoid: worked on, helped with, was responsible for, assisted, involved in, handled — all of them hide whether you did the thing or watched it happen.