"Quantify your achievements" is the most common — and most frustrating — piece of resume advice. Frustrating because most people genuinely don't know the exact numbers from their last role. The good news: you don't always need precise numbers to write a strong, quantified-feeling bullet. Here's how to find, estimate, or substitute metrics for any role.
Why quantification matters
Bullets with numbers outperform bullets without numbers in two specific ways:
- ATS keyword density: numbers count as content, increasing your bullet's "specificity score" in many ATS engines
- Recruiter dwell time: a number stops the eye. "Reduced cycle time by 30%" gets read; "Improved efficiency" gets skimmed past
Studies show resumes with quantified achievements get 30-40% more callbacks than equivalent resumes without numbers. The effect is consistent across industries.
The 4 categories of "quantification"
Most candidates think "quantify" means "add a percentage." It's broader than that. Strong bullets quantify in any of these dimensions:
1. Scale
How big? How many? How much?
- "Managed $40M annual budget" (dollar scale)
- "Led team of 12 engineers across 3 time zones" (people scale)
- "Maintained ETL pipeline processing 200K records/hour" (volume scale)
- "Owned product used by 250K monthly active users" (audience scale)
2. Improvement
Before vs after — even rough estimates work.
- "Reduced month-end close from 12 days to 5 days"
- "Cut p99 API latency from 800ms to 120ms"
- "Improved customer NPS from 32 to 58 over 18 months"
3. Speed
How fast? How quick?
- "Shipped MVP in 6 weeks vs 12-week original estimate"
- "Onboarded 25 enterprise customers in first 90 days"
- "Reduced incident response time from 45 min to 8 min"
4. Frequency
How often? How regularly?
- "Delivered weekly board-pack reports for 18 consecutive months"
- "Conducted 50+ customer interviews over 4 quarters"
- "Shipped 3 major product releases per quarter"
Where to find numbers you forgot you knew
If you can't remember exact metrics, try these sources:
1. Old performance reviews
Annual reviews, mid-year check-ins, or self-assessment forms often quote specific metrics tied to your work.
2. LinkedIn endorsements / recommendations
Recommendations sometimes mention specific projects with numbers. "Tanzeel led the M&A integration that delivered $4M in synergies."
3. Internal documents you saved
Slide decks, project retros, status reports, OKR documents. Search Google Drive / SharePoint / Notion for old files.
4. Email archives
Search emails for "thank you," "great work," "celebrating." Often these come with specific numbers attached.
5. Company blog / press releases
If your work was significant enough to be mentioned externally, the press release or blog post will have public-facing numbers.
6. Slack / Teams archives
Search for celebration emojis, "🎉," "shipped," "launched." Conversations around these often have numbers.
How to ethically estimate when you have no records
If you genuinely can't find exact numbers, careful estimation is acceptable:
The "size signal" approach
You don't need to know "$2.3M revenue impact." You can write "multi-million dollar revenue impact" or "low-seven-figure revenue impact." This is honest, avoids over-claiming, and still conveys scale.
The "team size" approach
If you led a team but don't remember exact size, give a range: "team of 8-12 across 4 functions." Honest if approximate, more concrete than "managed a team."
The "duration" approach
You always know roughly how long something took: "delivered initiative across 18-month roadmap" is precise enough.
The "frequency" approach
"Conducted weekly stakeholder reviews" — you know if it was weekly or monthly. Use that.
What NOT to do
Don't fabricate exact numbers
"Reduced costs by 23.7%" when you actually have no idea is a lie waiting to be exposed in interviews. Use ranges or qualitative scale instead.
Don't pad weak bullets with irrelevant numbers
"Worked 50+ hours per week" is a number, but it's not an achievement. Numbers should describe IMPACT, not effort.
Don't use numbers without context
"Generated $500K in revenue" — is that good? Bad? Compared to what? "Generated $500K in revenue, exceeding quota by 35%" is much stronger.
The XYZ format multiplies quantification impact
Quantification combined with the XYZ format ("Accomplished X by doing Y, with Z impact") produces the highest-performing resume bullets:
Weak (no number):
"Was responsible for improving customer satisfaction across the team."
Quantified but verbose (STAR-style on resume):
"When the company faced declining customer satisfaction scores in 2024, I was tasked with launching a new customer success initiative. I rebuilt our onboarding process and introduced a quarterly check-in cadence with all enterprise customers, resulting in NPS improvement from 32 to 58 over 18 months."
Quantified XYZ (best for resumes):
"Improved enterprise NPS from 32 to 58 over 18 months by rebuilding onboarding and instituting quarterly check-ins."
Same achievement. Half the words. Outcome leads. Numbers visible immediately.
Quick exercise
Take 5 minutes to do this for your most recent role:
- Pick your top 3 accomplishments from that role
- For each, ask: "What did this affect — and how much?"
- Find or estimate one number per accomplishment (scale, improvement, speed, or frequency)
- Rewrite each bullet in XYZ format with the number
You'll likely find that 60-80% of your bullets can be quantified with information you already have. The other 20-40% become candidates for ranges or qualitative scale.
Use our free Bullet Rewriter to score each bullet and see the gaps.
→ Rewrite your bullets free with STAR / XYZ / PAR templates