Numbers beat adjectives: how to quantify your résumé bullet points
Most résumés describe. The good ones prove.
Here are two bullets for the same job:
- Responsible for improving the sales process and driving strong results.
- Rebuilt the quoting process and closed 150% more revenue in my first 30 days, 250% more by day 90.
Same person. Same work. The first one asks you to trust the adjectives. The second one hands you the receipts and lets you decide. I wrote both of those about myself at different points, and the second version is the one that got me interviews.
I've changed industries three times. Every time, the thing that moved the needle wasn't a longer list of duties. It was putting a number on the work so a stranger could see the size of it in two seconds. This post is how to do that, including when you're convinced you have nothing to count.
Why numbers win
A recruiter gives your résumé about six to seven seconds on the first pass. In that window, adjectives blur together. "Strong," "proven," "results-driven," "detail-oriented" — everyone writes those, so they carry no signal. A number stops the eye because it's specific and it's falsifiable. You wouldn't write "closed 150% more" if you couldn't back it up.
There's a second reason, and it's the one people miss. An applicant tracking system and the human reading behind it are both trying to answer one question: how big was this, really? "Managed a team" could mean two people or two hundred. "Cut costs" could mean forty dollars or four hundred thousand. The number is the only thing that closes that gap. When you leave it out, the reader fills it in with the smallest possible version.
The formula: verb + what you did + the number
You don't need to be clever here. A quantified bullet almost always fits one shape:
Strong action verb → what you did → the measurable result.
- Cut invoice processing time from 5 days to 1 by rebuilding the intake form.
- Trained 12 new hires, 8 of whom were promoted within a year.
- Reduced customer churn 3 points over two quarters.
Notice the numbers aren't always dollars or percentages. Days. Headcount. A count of anything. "From 5 days to 1" is a number. "12 new hires" is a number. You have more of these than you think.
Lead with the verb, not with "Responsible for" or "Tasked with." Those phrases spend your first two words describing the assignment instead of the achievement. Open with what you actually did: built, cut, shipped, closed, trained, fixed, grew.
"But my job doesn't have metrics"
This is the objection I hear most, and I had it myself when I moved out of a hands-on engineering role. You don't have a sales quota, so it feels like there's nothing to count. There almost always is. You just have to go looking for it.
Ask yourself these, one at a time:
- How many? People trained, tickets closed, projects run, accounts handled, reports produced each week, clients supported at once.
- How much? Budget you touched, revenue you influenced, time you saved someone, error rate you brought down.
- How often / how fast? Turned a 3-day task into 1. Went from monthly to weekly. Handled 30 requests a day instead of 20.
- Compared to what? Faster than the old process, higher than last year, ahead of the team average. A comparison is a number even when you don't have a hard figure.
If you genuinely can't measure the outcome, measure the scope. "Supported 40 users across 3 sites" tells a real story even if you can't point to a dollar saved. Scope is a number too.
One honest note: estimate, don't invent. If you know you cut a process roughly in half, "cut it about 50%" is fair and defensible. Making up "increased efficiency 73.4%" is not, and a sharp interviewer will pull that thread until it snaps. A grounded estimate you can explain in the room beats a precise-looking number you can't.
Before and after
Watch what the number does to the same fact:
| Before | After |
|---|---|
| Handled customer support tickets | Resolved ~30 support tickets a day at a 95% first-contact rate |
| Helped migrate the company to new software | Led the migration of 40 users to the new platform in 3 weeks, zero data loss |
| Improved onboarding | Cut new-hire onboarding from 2 weeks to 4 days by writing the missing docs |
| Managed social media | Grew the newsletter from 400 to 2,100 subscribers in 6 months |
The left column could be anyone. The right column is clearly you, and it gives the interviewer something to ask about — which is exactly what you want. Every number is a door into a story you get to tell out loud.
Don't number everything
A résumé where every single line has a percentage starts to read like a spreadsheet, and the eye glazes over again. Aim to quantify your top two or three bullets under each role — the ones that carry the weight. Let the rest describe the context. Contrast is what makes the numbers land. If everything shouts, nothing does.
Where this fits with tailoring
Once you've got a set of quantified bullets, the last step is aiming them. A given job posting cares about some of your numbers more than others. If the role is about efficiency, the "5 days to 1" bullet moves up. If it's about scale, "40 users across 3 sites" leads. Same résumé, reordered so the numbers that matter to this employer sit where the eye lands first.
That reordering is exactly the part that's tedious to do by hand for every application, and it's what ResumAI is built to speed up. It reads the job description, scores how well your résumé lines up, and shows you which of your bullets to pull forward for that specific role — while keeping your search private (your résumé is never shown to other users, and PII is scrubbed before anything reaches a model). The judgment about what's true stays yours. The busywork of re-aiming it for the tenth job this week doesn't have to.
The one thing to do today
Open your résumé. Find the three bullets that describe your best work. For each one, ask: how many, how much, how fast, compared to what? Put the answer in the sentence.
You'll usually find that the work was bigger than the way you'd been describing it. Most people undersell themselves on paper, not the other way around. Give the reader the number and let the number do the arguing.