Resume Guides
How to Quantify Achievements When You Don’t Have Numbers
“Quantify your achievements” is the most repeated resume advice there is, and the least useful, because it never explains what to do when nobody tracked anything. Here is where the numbers actually are.
Why Numbers Work
A number converts a claim into evidence. “Improved the onboarding process” asks the reader to take your word for it and gives them no sense of whether you improved it for five people or five thousand. “Cut onboarding time from 3 weeks to 4 days across 200 new hires annually” requires no trust at all — it just states what happened.
This also solves a problem you cannot solve any other way: it establishes scale. Two candidates with identical job titles may have operated in worlds an order of magnitude apart. Only numbers reveal which one you were.
Five Questions That Find Numbers
When a bullet has no metric, run it through these:
- How many? People, clients, projects, tickets, articles, units, systems, students, patients.
- How often? Daily, weekly, per shift, per quarter. Frequency is a measurement.
- How big? Budget, revenue, headcount, audience size, data volume, geography.
- How long? Duration, timeline, how much faster than before, how far ahead of schedule.
- How much better? Before and after, on any axis you can honestly measure.
Most bullets that seem unquantifiable answer at least two of these once someone actually asks.
Before and After: A Role With No KPIs
Before (administrator, “nothing to measure”)
“Managed office operations and supported the team with scheduling and vendor coordination.”
After (same job, questions answered)
“Ran operations for a 45-person office across 2 sites, coordinating 12 vendor contracts worth £180k annually and renegotiating 3 of them to cut recurring costs by 15%.”
Nobody handed this person a dashboard. The numbers were already in the job — headcount, sites, contracts, contract value — and simply were not written down.
Where to Look for Figures You Forgot
- Old performance reviews. Managers write down numbers you never noticed.
- Your own calendar and inbox. Volume, cadence, and scope are recorded there whether you tracked them or not.
- Team dashboards and reports you contributed to, even if the metric was not “yours”.
- Project documentation — scope statements almost always contain a size or a timeline.
- Ask a former colleague. People remember the scale of shared work surprisingly well.
When Honestly No Number Exists
Sometimes there really is nothing to count, and the correct move is scope and constraint instead of a fabricated metric. “Rebuilt the compliance process during a regulator audit with a two-week deadline and no downtime” contains no percentage and is still concrete, specific, and difficult. Constraint is its own form of evidence.
The Line You Should Not Cross
- Do not invent precision. “Increased efficiency by 47.3%” when nobody measured anything is a fabrication that a single follow-up question will expose.
- Do not claim team results as solely yours. “Contributed to” and “led” are different words, and interviewers ask which one it was.
- Do not attach a number to a bullet where it does not belong just to have one. Forced metrics read as forced.
- Do not use a figure you cannot explain. If you cannot say where it came from and how it was calculated, it should not be on the page.
The purpose of quantifying is credibility. A number you cannot defend achieves the exact opposite of the thing you were trying to do.
Frequently Asked Questions
What if my role genuinely has no metrics?
Almost every role has countable things even when it has no KPIs: how many, how often, how large, how long, how many people. Scale and frequency are measurements even when outcomes are not tracked formally.
Is it acceptable to estimate?
Yes, if the estimate is honest and you can defend it in an interview. 'Approximately 200 tickets per month' is fine if that is genuinely your typical volume. Inventing a precise figure you cannot explain is not.
What if I cannot share exact figures for confidentiality reasons?
Use ranges or relative terms: 'a multi-million dollar portfolio', 'a team of 15+', 'reduced processing time by roughly a third'. Approximation is far better than silence, and employers understand confidentiality.
Should every bullet have a number?
No. A resume where every line ends in a percentage reads as manufactured. Aim for numbers in your strongest two or three bullets per role, and let the others carry context and scope instead.
What if the result was bad or the project failed?
Then measure what you can honestly claim: what you delivered, at what scale, under what constraint. 'Delivered a full migration for 40 services in 6 weeks' is true regardless of what happened to the product afterwards.