Read these two bullets and notice what your brain does:
- “Responsible for improving the onboarding process.”
- “Cut new-hire ramp-up from 8 weeks to 5 by rebuilding onboarding for a 12-person support team.”
The first is a claim; the second is evidence. Numbers do three jobs at once: they prove the work happened, they communicate its scale, and they make the bullet concrete enough to remember after reading 80 resumes. Yet most resumes contain almost none, usually because of one belief: “my work doesn't have metrics.” That belief is almost always wrong, and this guide is about why.
Four formulas that turn work into numbers
Nearly every strong quantified bullet is one of four shapes. Run each of your existing bullets through them and see which fits:
| Formula | Shape | Example |
|---|---|---|
| Scale | How much / how many / how often you handled | “Processed 120+ vendor invoices weekly across 3 subsidiaries.” |
| Delta | What changed: before → after, or % improvement | “Reduced average ticket response time from 9 hours to 2.” |
| Frequency × duration | A recurring contribution, totaled | “Ran weekly stakeholder reviews for 18 months (70+ sessions) without a missed cycle.” |
| Denominator | Your share of a known whole | “Handled the largest of 5 regional territories: 38% of total accounts.” |
Where the numbers hide when you “don't have any”
- Your tools remember.Ticket systems, CRMs, dashboards, commit history, calendar archives, email folders. “How many X per week?” is usually one search away.
- Time is a metric. How long did the task take before your change? After? Hours saved per week is a universally available delta.
- People are a metric. Team size, users supported, stakeholders coordinated, people trained, attendees served.
- Money is nearer than you think. Budget you touched, contract values you supported, cost of the tool you replaced, revenue of the accounts you serviced.
- Consistency is a metric. Zero missed deadlines across N projects, N months without an SLA breach, 100% audit pass rate. Reliability quantifies beautifully.
The estimation question (read this part carefully)
You won't always have exact figures, and honest estimation is a normal, defensible practice, within rules:
- Estimate inputs you observed, never outcomes you didn't. You can estimate that you handled “~30 client calls a week” because you were there. You cannot estimate that you “increased revenue 20%” if no one measured revenue.
- Round honestly and signal it.“~200 tickets/month” and “40+ accounts” read as truthful precision. Suspiciously exact invented numbers (“increased efficiency 73%”) read as the opposite.
- Apply the interview test.For every number: can you explain, out loud, where it comes from? “Our queue averaged 45–55 tickets a day; I handled roughly a third” survives. A number with no story behind it is a fabrication wearing a costume.
Worked examples
Before
Managed social media accounts for the company.
After
Grew the company's LinkedIn following from 2,100 to 7,800 in 14 months, posting 4× weekly.
Before
Helped train new employees.
After
Onboarded and trained 9 new hires across two seasons; all 9 reached full productivity ahead of the 6-week target.
Before
Improved the monthly reporting process.
After
Automated the monthly board report in Google Sheets, cutting preparation from ~2 days to 3 hours.
Where quantification matters most
You don't need a number in every bullet; that reads like a spreadsheet. Prioritize:
- The first bullet of your current role: the most-read sentence on the page after your title.
- The bullets matching the job posting's top requirements: evidence exactly where the reader is checking for it.
- Your summary's proof point: one number in the summary anchors the whole skim (“…supporting 40+ enterprise accounts”).
Two or three unquantified, qualitative bullets per role are fine. They give the page room to breathe and describe responsibilities numbers can't.