How to quantify resume achievements — even when you don't have hard numbers

"Quantify your impact" is the most common resume advice — and the most frustrating when you think you have no numbers. You almost always have more than you think. Here's how to find honest, defensible metrics.

Five prompts to find numbers

• Scale: how many users, requests, records, teammates, services, regions?
• Time: how much faster, sooner, or more frequently?
• Money: revenue added, cost saved, or hours reclaimed × rate.
• Quality: bugs reduced, uptime/accuracy improved, errors dropped.
• Frequency: how often (daily, per release, per quarter)?

Quantify context when you can't quantify the result

If you genuinely can't measure the outcome, quantify the context: "across 3 regions," "for 50k daily users," "in a 6-person team owning 12 services." Scale signals weight even without a percentage.

Honest estimates are fine — fabrication isn't

A reasonable estimate with a clear basis ("~20% faster, based on before/after build times") is legitimate. Inventing a number you can't defend in an interview is not — and it's the one thing you must never do. HMLens's rewrite is zero-fabrication for exactly this reason.

Pair these prompts with the Action + Tech + Impact formula and most "vague duty" bullets become measurable. Run a free score to see which bullets still lack impact.