How to Quantify Your Impact When You Don't Have the Metrics
You don't need a dashboard to put numbers on your work. A few honest estimates, ranges, and proxies turn vague duties into evidence a hiring manager believes.
The most common objection to "put a number on it" is honest: I never tracked the number. You ran the migration, mentored the intern, cleaned up the backlog — but nobody handed you a metric on the way out. That's fine. Quantifying impact is about giving the reader a sense of scale, not producing an audited figure.
Estimate a range, then defend the floor
You almost always know enough to bracket the truth. You don't remember the exact support-ticket drop, but you know it was "a lot fewer" and you know the team size. Pick a conservative range and lead with the low end.
If someone challenges the number in an interview, you can defend the floor without flinching — that's the whole point of estimating conservatively.
Use proxies when the outcome is fuzzy
When you can't measure the result, measure the work. Scope, frequency, and audience are all legitimate numbers:
- Scope — "owned 3 of the 7 services behind checkout."
- Frequency — "ran the release every Thursday for a year."
- Audience — "documentation used by ~200 engineers across 4 teams."
None of these claim an outcome you can't prove. They just replace "worked on things" with a picture of the load you carried.
Run Score → Impact on any role and it flags bullets with no quantifier — then suggests a proxy (scope, frequency, or audience) you can defend.
