Here’s the most common excuse we hear:
“I don’t have numbers.”
Almost always, that’s wrong.
What people usually mean is:
- They were never taught to measure impact
- No one handed them a dashboard
- Their work felt indirect
None of that means there were no results.
It just means the results weren’t labeled yet.
This article shows you where numbers actually come from and how to use them without making things up.
Why numbers matter more than ever
ATS systems rank resumes.
Humans skim them.
Numbers help with both.
For ATS:
- Numbers anchor keywords in real context
- They increase confidence signals
For humans:
- Numbers create credibility
- They reduce the need for interpretation
- They answer “so what?” instantly
A resume with no metrics feels vague, even when the work was real.
For help writing the bullet itself, see Writing Achievement-Focused Resume Bullet Points.
What counts as a metric (hint: more than you think)
People think metrics only mean revenue.
That’s lazy thinking.
Metrics include:
- Time
- Volume
- Frequency
- Scope
- Scale
- Change over time
- Before vs after
If something changed because of your work, you can usually measure it.
Category 1: Time-based metrics
These are the easiest to find.
Ask:
- Did something get faster?
- Did delays shrink?
- Did turnaround improve?
Examples:
- Reduced onboarding time by 30%
- Cut reporting cycle from 5 days to 1
- Shipped features 2 weeks faster per release
Even estimates are fine if they’re reasonable.
Don’t guess wildly. Be honest.
Category 2: Volume and scale
How much of something did you touch?
Examples:
- Supported 120+ customers
- Managed backlog of 300+ tickets
- Led projects across 5 teams
- Maintained systems used by 80k users
Scale matters. It signals trust and responsibility.
Category 3: Frequency and repetition
Consistency is a metric.
Examples:
- Ran weekly planning sessions for 12 months
- Delivered monthly reports to leadership
- Supported daily operations for a 24/7 system
This shows reliability, not just one-off wins.
Category 4: Quality and error reduction
Not everything is about growth.
Stability matters too.
Examples:
- Reduced production errors by 25%
- Decreased customer complaints
- Improved data accuracy
Even if no one tracked it formally, you usually know if things got better.
Category 5: Decision impact
This is where many people get stuck.
Ask:
- Did your work influence decisions?
- Did it unblock leadership?
- Did it reduce uncertainty?
Examples:
- Built dashboards used in quarterly planning
- Provided analysis that informed pricing changes
- Created documentation adopted by multiple teams
If decisions changed because of your work, that’s impact.
Before vs after examples
Example 1
Before:
Created reports for leadership
After:
Built weekly reports used by leadership to track performance across 4 teams
Same work. One sounds real.
Example 2
Before:
Helped improve onboarding
After:
Redesigned onboarding process, reducing new hire ramp-up time from 6 weeks to 3
Even if you need to estimate, a concrete number makes the impact real.
What not to do
There are two mistakes that kill trust.
1. Making numbers up
Recruiters can smell this.
If you can’t defend a metric in conversation, don’t use it.
2. Over-precision
Don’t do this:
- Increased revenue by 17.382%
That looks fake.
Round numbers are fine.
3. Using numbers you can’t defend
Any metric on your resume is fair game in an interview. “Reduced costs by 30%” will prompt “How did you measure that?” If you can’t explain your methodology in two sentences, soften the claim or use a range.
Using estimates without lying
Estimates are acceptable when:
- They’re directionally correct
- You can explain how you arrived at them
- They match the scope of the role
Say:
- Approximately
- About
- Roughly
Honesty beats fake precision every time.
How to find your hidden numbers
If you don’t have a dashboard, try these:
- Ask your manager — they often have metrics you’ve never seen
- Check team reports — quarterly reviews, sprint retrospectives, OKR updates
- Estimate from team size and output — “Supported 5 engineers across 3 product launches” is legitimate
- Compare before and after — even informal observations count if they’re honest
Do this, not that
Do this:
- Anchor impact to change
- Use ranges when unsure
- Measure what moved
Not that:
- Avoid numbers entirely
- Inflate results
- Use metrics unrelated to your role
Pair your metrics with strong action verbs for maximum impact.
Where tools help
Resume tools can:
- Flag vague bullets
- Suggest where metrics fit
- Help tighten language
They can’t:
- Know what mattered
- Invent real outcomes
Tools like Resumes Coach work best when you bring the raw truth and let the tool sharpen it.
Final check
Read each bullet and ask:
“What changed because of this?”
If you can’t answer, rewrite the bullet.
If something changed, you have a metric.
You weren’t doing nothing.
You just weren’t measuring it yet.
See which bullets need numbers. Upload your resume to Resumes Coach and get per-bullet scoring that flags vague impact statements — with AI suggestions for adding metrics.