"Responsible for managing customer accounts." "Handled reporting." "Assisted with onboarding." Duty statements like these describe a job description, not a person. They tell a reader what your role was supposed to involve, but nothing about what actually happened when you did it. Numbers fix that — as long as they're real.
The six dimensions where numbers hide
When people say "I don't have metrics," they usually mean they don't have revenue figures. But quantification comes in more shapes than dollars. Look at your work through six lenses:
- Scope — how many accounts, users, systems, or reports you owned. "Managed reporting" becomes "owned weekly reporting across four business units."
- Time — how long something took, or how much faster it got. "Reduced month-end close from nine days to five."
- Volume — throughput. Tickets resolved, records processed, deployments shipped per week.
- Cost — money saved or avoided, budget administered, waste removed.
- Quality — error rates, rework, satisfaction, defects caught before release.
- Frequency — cadence and consistency. "Ran a daily standup for a team of eight" says more than "participated in meetings."
Most duties can be measured on at least one of these. You rarely need all six — one concrete dimension turns a vague line into something a reader can picture.
Finding honest numbers when you think you have none
The figures exist; they're just not written down yet. Reconstruct them from the trail your work left behind:
- Count the artifacts. Old dashboards, ticket queues, sprint boards, invoices, and calendars hold real counts. How many clients were on your list? How many tickets sat in your queue in a typical week?
- Estimate from cadence. If you did something weekly for two years, that's roughly a hundred repetitions. "Processed payroll biweekly for 60 employees" is a defensible number built from routine.
- Ask what changed. Before/after comparisons are the strongest lines you can write. What was broken or slow when you arrived, and what did it look like when you left?
When you estimate, estimate conservatively and be ready to explain how you got there. "Approximately 40 support tickets a week" that you can reconstruct beats a precise-sounding figure you invented. If you round, round down.
When there's no clean metric
Some real, valuable work doesn't reduce to a number, and forcing one makes it look fake. If you rewrote a tangled onboarding process, the honest win might be "restructured onboarding docs that new hires now use without escalating to the team" — an outcome, not a percentage. Describe the scope you touched and the result you produced in plain terms. A specific qualitative outcome reads as more trustworthy than a suspiciously round statistic.
The line to never cross: don't invent figures. A made-up efficiency number collapses the moment an interviewer asks how you measured it, and it takes your credibility with it.
Keep the raw material as you go
The reason quantifying is hard in a job search is that you're doing archaeology under deadline — digging for numbers about work you finished years ago. The fix is to capture them while they're fresh. Keeping a running record of projects, scope, and results — a Memory Board of your own evidence — means that when a posting asks for a specific accomplishment, you're pulling from a file instead of straining to remember. FilterProof is built around that habit, but a plain document works too. The point is the same: back every number with something real, written down before you needed it.