How to put numbers on your work when you think you have none
The advice is always quantify your impact, which is useless if your job never came with a dashboard. Here is where the numbers actually hide.
7 min read
Quantify your achievements is the most repeated piece of resume advice there is, and the least actionable. Most people did not work somewhere that measured their contribution. Nobody handed you a figure for how much better the process got after you fixed it.
So people either skip it, or invent something, which is worse. Both are avoidable, because there are almost always real numbers available. They are just not the ones the advice implies.
Six places a real number hides
1. Count the thing itself
Not the improvement, just the volume. How many tickets, students, invoices, patients, articles, stores, accounts. This needs no measurement system, only memory, and it immediately tells a reader what size of job it was.
Handled customer queries becomes handled around 40 support tickets a day. Nothing improved in that sentence except the reader's understanding.
2. Count the people
Team size, how many you trained, how many stakeholders, how many departments. Coordinating across two teams and across nine are different jobs and the number is the only way to say which.
3. Use time
How long something took before and after. This is the easiest number to recover honestly, because people remember durations. A report that took a morning and now takes ten minutes is a real result and you do not need a system to know it.
4. Use money, even approximately
Budget managed, value of contracts, cost of the thing you bought or avoided buying. If you handled a budget, the figure is on a document somewhere and you are allowed to know it.
5. Count the frequency
Daily, weekly, monthly, how many cycles. Ran the monthly close for three entities tells a reader more than ran the close, and it is available to anybody who did the job.
6. Ask what stopped happening
This is the one people miss. If you fixed something, there was a complaint, an escalation, a manual step, a recurring error. It stopped. That is your result even if nobody put a figure on it.
Removed a duplicate approval step that was adding about a day to every claim is a quantified achievement, and nobody measured anything to produce it.
What it looks like applied
| No number | A real number, found |
|---|---|
| Managed the company's social media accounts | Ran four accounts posting daily, taking the combined following from about 3,000 to 11,000 in a year |
| Responsible for processing invoices | Processed around 600 invoices a month across two entities, cutting the approval cycle from five days to two |
| Helped improve the onboarding process | Rewrote onboarding for a team of 30, replacing a half-day shadowing session with a checklist new joiners now finish in about an hour |
| Taught undergraduate tutorials | Taught weekly tutorials to four groups of 15, covering two modules across the year |
| Worked on improving site performance | Cut the homepage load from about 4 seconds to 1.5, mostly by deferring third-party scripts |
The rules that keep this honest
- Approximate openly. Around, about, roughly. A reader trusts an approximation far more than a suspiciously precise 23.7%, and you can defend it in an interview.
- Never invent a figure you cannot explain. The question in the interview is always how did you measure that, and there is no recovering from not knowing.
- Do not quantify everything. A resume where all twelve bullets carry a percentage reads as fabricated. Three or four strong numbers beat twelve weak ones.
- Take credit for your part, not the team's result. If revenue doubled while you were one of forty people, say what you did, not what the company achieved.
- A plain statement beats a fake number. If nothing is countable, say what changed in words. That is still an achievement; it is just not arithmetic.
When there is genuinely nothing
It happens, particularly in a first job or a short stint. In that case say what you were trusted with and what you learned to do, concretely. Trusted to run the Saturday shift alone after two months is not a number and it tells a reader something real.
What does not work is reaching for a percentage because an article said to. A reader who hires regularly can spot an invented figure quickly, and once they have spotted one they stop believing the rest of the page.
Questions people ask
- How do I quantify my resume if I have no metrics?
- Count the thing itself rather than the improvement: volume, people, time, money, frequency. Those need no measurement system, only memory, and they tell a reader what size of job it was.
- Is it acceptable to estimate numbers on a resume?
- Yes, as long as you say so and can explain how you arrived at it. Around 600 invoices a month is credible and defensible. A precise figure you cannot account for in an interview is not.
- Should every bullet have a number?
- No. A resume where every line carries a percentage reads as invented. Three or four genuine numbers in the right places do more than a dozen forced ones.
- What if the result was the team's, not mine?
- Describe your part. A reader is trying to work out what you would do for them, and claiming a company-wide outcome you contributed a fraction of tends to read as the opposite of confidence.
Want this done for your resume?
Upload it and see the text a parser pulls out, what a recruiter notices first, and the lines worth rewriting.
Check my resume →First one free · no account
Read next
- Action verbs, and why a longer list will not help youEvery list of 200 power verbs makes the same mistake. The verb was never the problem; the missing object of the sentence was.6 min
- Your resume looks fine and you are still not getting interviewsSix reasons, roughly in the order they are likely to be yours. Most people start fixing the last one.7 min
- Writing your first resume for campus placementsEverybody in the queue has the same degree and the same empty experience section. What separates the shortlist is what you did with your own time.7 min