WRITING BULLETS
How to Write Quantified Resume Bullet Points
The formula every recruiter-approved bullet point follows — and how to retrofit yours without inventing numbers you can't defend in an interview.
Recruiters scan the bullets under each job for about three seconds. In those three seconds they're looking for a verb, a unit, and a number. "Led a team" is a bullet. "Led a team of 8 engineers to cut deploy time from 45 to 6 minutes, saving the platform team roughly 120 engineering hours per quarter" is a bullet that lands.
This guide walks through the quantified-bullet formula, what "quantification" actually means when you don't have exact numbers, and how to retrofit an existing resume bullet by bullet.
The verb + noun + outcome formula
The quantified-bullet formula is: strong verb + noun + measurable outcome + timeframe. You don't need to count revenue for every bullet; any measurable signal works — users served, meetings run, code reviewed, tickets closed, accuracy improved, time saved, error rate reduced. A bullet with honest numbers in it is better than a bullet with vague superlatives ("significantly improved performance") because vague claims look padded, and padded claims look like lying.
Strong verbs are specific verbs. "Led" is OK; "Drove", "Shipped", "Negotiated", "Scaled", "Cut", "Recovered", "Migrated" are stronger because they imply a specific action. Avoid "Responsible for" entirely — it describes a role, not a contribution.
How to quantify when you don't have exact numbers
Order-of-magnitude is fine. "Roughly a third" is a number. "Around 20 customers" is a number. "Over 1,000 daily users" is a number. Being specific-but-approximate reads as honest; being unspecific-or-round reads as puffed.
If you genuinely can't find a quantifiable outcome, switch to a structural quantifier: team size, project duration, number of stakeholders, scope of system. "Designed the payment integration used across all 4 product lines" is more credible than "Worked on a major payment integration" even with no dollar figure.
When you do have exact numbers, use them — don't round. "Cut p95 latency from 820ms to 210ms" is more believable than "Reduced latency by ~75%" because the specific numbers are unfakeable. Specific reads as honest.
Retrofitting an existing resume
If you're retrofitting an old resume, go line by line and ask two questions per bullet: "How would you measure whether I did this well?" and "What was the order of magnitude of the outcome?" The answers don't need to be precise. Then rewrite the bullet to lead with the outcome, not the activity. Before: "Worked on the checkout flow." After: "Rebuilt the checkout flow in React, cutting cart-abandonment rate from 31% to 22% over Q3."
Three honest tests for each bullet: (1) Could I defend every number in this sentence in an interview? (2) Does the verb describe a specific action, not a job duty? (3) Does the outcome actually matter to a stranger reading 50 resumes? If any of those is "no", rewrite or cut.
Frequently asked questions
How many bullets per role should I have?
Can I use bullets that don't have numbers?
What if my numbers are unimpressive?
Should I use AI tools to write my bullets?
Related guides
Resume action verbs list (2026)
A categorised reference of the strongest verbs to lead each bullet — leadership, technical, growth, operations.
How to write an ATS-parseable resume
Strong bullets only matter if the ATS reads them. The three formatting rules that decide parser behaviour.
ATS Resume Keywords by Industry
Industry-by-industry keyword reference — what to weave into your verbed-and-numbered bullets so the parser scores you correctly.
Ready to apply this to your resume?
Build your resume in the live editor and run it through the free ATS scanner — no sign-up required to start.