How to Quantify Your Resume Bullets When You Do Not Have Numbers
"Add metrics" is the most repeated resume advice and the least actionable. Here is how to find real numbers in work that was never measured.
Everyone is told to quantify their achievements. Far fewer are told what to do when nobody at the company measured anything, or when the numbers are confidential. The answer is not to invent figures — it is to look in places you have not thought to look.
Six places numbers are hiding
1. Scale
How big was the thing you worked on? Rows in the table, users of the app, tickets in the queue, size of the codebase, number of stores, headcount supported. "Maintained the internal admin tool" becomes "Maintained the internal admin tool used daily by 300+ operations staff across 22 warehouses."
2. Frequency
How often did it happen? Daily reports, weekly releases, monthly closes. "Automated the reconciliation report" becomes "Automated a reconciliation report that ran manually every Monday, saving roughly 6 hours a week."
3. Time
Before and after durations are almost always knowable, even approximately. Deployment took two hours and now takes fifteen minutes. Onboarding a new client took three weeks and now takes four days.
4. Team and stakeholders
How many people did you work with, coordinate, review or mentor? "Led a team" is weak; "Led a team of 5 engineers across 2 time zones" is specific and verifiable in an interview.
5. Money
Budget owned, cost saved, revenue influenced, sponsorship raised, licence fees avoided. If exact figures are confidential, use a band: "reduced monthly cloud spend by roughly 30%" is fine and defensible.
6. Quality
Defect counts, uptime, test coverage, customer satisfaction, error rate. "Improved the pipeline's reliability" becomes "Cut pipeline failure rate from ~8% to under 1% over two quarters."
A formula that works
Action verb + what you did + the tool or method + the measurable result.
Worked on improving the checkout page.
Rebuilt the checkout page in React with lazy-loaded payment widgets, cutting load time from 4.1s to 1.6s and reducing cart abandonment by 12%.
When you genuinely cannot measure it
Some work resists numbers — a migration nobody benchmarked, a policy you wrote, a process you documented. In those cases, describe the scope and the consequence instead. "Wrote the onboarding runbook now used for every new backend hire" carries weight without a single digit.
One caution: never invent a number you could not defend. If a bullet says 40%, expect to be asked how it was measured. A vaguer but honest claim beats a precise one you cannot support.
Approximation is allowed
You do not need audited figures. "~", "roughly", "over" and "more than" are all acceptable, and recruiters read them as normal. "Handled roughly 50 support tickets a week" is a real, useful number even though you never counted precisely.