Quantifying achievements
'Quantify your achievements' is the most-given resume advice and the least-explained. The reason most people skip it is they don't know where to find numbers when they don't have access to revenue dashboards. Here's the playbook.
Every achievement has a number attached if you look hard enough — time saved, scale handled, percent improved, frequency, headcount, error rate. The trick isn't inventing numbers, it's finding the ones that already exist in the work.
The five number categories
Every achievement falls into one of five number types. (1) Magnitude: how big was the thing you did? (12k events/sec, 1,400 employees, $40M GMV). (2) Improvement: how much did you change a metric? (47% latency reduction, 4 percentage points of conversion). (3) Time: how long did it take or save? (8 weeks, saved 4 hours per week). (4) Scope: how many people, systems, accounts? (12 services, 3 regions, 47 accounts). (5) Frequency: how often did it happen or how often did you do it? (weekly cohort report, 3x daily on-call rotation).
When you don't have access to the numbers
Most people skip quantification because they assume they need revenue data. They don't. If you didn't have access to revenue, the magnitude of the system you worked on is still a number — server count, request volume, user count, team size, regions supported, languages translated. Ask your manager for one number per project; if they can't give you one, the project itself wasn't measured (which is its own signal).
Order-of-magnitude estimates are fine
If you don't have the exact number, an order-of-magnitude estimate is honest enough as long as you're clearly in the right ballpark. 'Roughly 10k requests per second' is fine. '10,247 requests per second' when you don't actually know that is a credibility risk because the false precision is suspicious. When in doubt, round to one significant figure.
Numbers that don't help
Years of experience inside a bullet ('In my 7 years of experience…') is filler. Number of meetings attended. Number of emails sent. Number of slides in a deck. Anything that scales with the calendar instead of with effort. The number has to represent something a reasonable observer would call an achievement.
What to do if your role is genuinely unmeasurable
Some roles are. The fix isn't to make up numbers; it's to switch to time-saved or scope phrasing. 'Reduced the weekly status report from 3 hours to 30 minutes by templating the recurring sections.' 'Owned the onboarding for every new hire across 4 teams.' Both have numbers. Neither is revenue.
Side by side
Reduced weekly invoicing close from 6 hours to 90 minutes by automating the JSON-to-PDF step with a small Python script.
Improved efficiency of monthly invoicing process through automation and process improvements.
Mistakes that get this wrong
- Skipping numbers entirely because revenue data wasn't available
- Inventing numbers — instantly caught in the interview
- False precision (10,247 instead of 'roughly 10k')
- Counting things that don't matter (meetings attended, emails sent)
- Using the same metric twice on the same resume
For every bullet, pick one of the five number types and find the most honest version of it. If you can't find one, the bullet is probably weaker than you think and should be cut or rewritten.
Frequently asked
What if I literally can't share the numbers (NDA, confidential)?
Use orders of magnitude or relative changes. 'Cut latency by ~60%' is fine even if the absolute number is confidential.
Should I use the same currency / units everywhere?
Yes — pick one and stick to it. Mixing $K and $M in the same role looks careless.
Is it OK to say 'led a team of 5' if I never had direct reports?
No — 'led' implies direct management. 'Coordinated' or 'worked alongside' is honest if you didn't manage.
Run your resume through the checker.
Free, no signup. Get a read on whether your resume actually clears the bar this tip is pointing at — in under a minute.