Two candidates do the same job. One writes “Responsible for managing the company blog.” The other writes “Grew blog traffic from 4k to 31k monthly sessions in a year by rebuilding the content plan around search intent.” Same work. Only one of them gets a call.
The difference is not talent at writing. It is that the second bullet answers a question the first one dodges: so what happened? Almost every weak resume bullet is a job description copied from the intranet. Almost every strong one is a small piece of evidence.
The formula
One structure covers most cases:
Strong verb + what you did + the measurable result + how you did it
The order can flex, but all four parts should be present
Leading with the verb keeps the bullet compact and puts the action where the eye lands. Leading with the result works when the number is dramatic enough to stop someone scanning. Both are fine; what matters is that the outcome is in there.
Before and after
Works
- Cut average support response time from 14 hours to 3 by rebuilding ticket triage and adding 22 macros
- Shipped a self-serve onboarding flow that moved trial-to-paid conversion from 4.1% to 6.8% in two quarters
- Led a 4-person team migrating 180 services off a deprecated auth provider with no customer-facing downtime
- Reduced monthly cloud spend by $18k by right-sizing instances and moving cold storage to a cheaper tier
Avoid
- Responsible for handling customer support tickets
- Worked on improving the onboarding experience for new users
- Part of the team that carried out an authentication migration
- Helped with cost optimisation efforts across cloud infrastructure
Notice what changed. The verbs became specific. Vague qualifiers — “helped with”, “worked on”, “part of the team that” — disappeared. And each bullet now contains a number the reader can hold onto.
Finding numbers when the work has none
The most common objection is that the job was not measurable. Usually it was; the measurements just were not framed as achievements at the time. Some places to look:
- Scale
How many users, accounts, tickets, transactions, students, patients, or square metres? “Managed the schedule” becomes “Managed rotas for 45 staff across 3 sites.”
- Time
How long did something take before and after? Hours saved per week, days cut from a close cycle, weeks trimmed from onboarding. Time savings are the most widely available metric and the least used.
- Money
Revenue influenced, costs avoided, budget owned, contract values negotiated. You do not need to have owned the P&L to describe the budget you worked within.
- Frequency and consistency
“Published 3 case studies a month for 18 months” shows reliability, which is itself a selling point for operational roles.
- Before and after states
When nothing was tracked, describe the transition: “from a spreadsheet with no version control to a shared database used by 4 teams.” A qualitative delta beats no delta.
Verbs: pick the one that describes the actual work
Long lists of “power verbs” encourage inflation — people reach for “spearheaded” when they mean “helped”. Pick the accurate verb from a small set instead.
| What you did | Verbs that fit |
|---|---|
| Built something new | Built, shipped, launched, designed, developed, introduced |
| Made something better | Cut, reduced, increased, improved, streamlined, automated |
| Ran or owned something | Led, owned, managed, coordinated, ran, oversaw |
| Fixed or unblocked something | Resolved, debugged, recovered, stabilised, unblocked |
| Influenced people | Persuaded, negotiated, trained, mentored, aligned |
| Found something out | Analysed, investigated, benchmarked, audited, diagnosed |
Two rules on tense: past tense for previous roles, present for the current one, and never mix them inside a single entry. And avoid starting more than two bullets in a row with the same verb — it makes a strong list read as a template.
Length, count, and order
- One to two lines per bullet. A bullet that wraps to three lines is usually two bullets, or one bullet with the context that should have been cut.
- Three to five bullets for recent, relevant roles. One to two for older or unrelated ones.
- Strongest first. Readers skim the first bullet of each job and the first line of each bullet. Put the number where it will be seen.
- No full stops at the end, or full stops on all of them. Either is fine; inconsistency is not.
Team work without stealing credit
Overclaiming is the fastest way to lose a technical interview, but hedging so heavily that your contribution vanishes is just as costly. Name your specific role in the collective result.
Attribution
Works
- Owned the payments integration in a 6-person replatform that lifted checkout completion by 12%
- Wrote the migration tooling used by 4 teams to move 180 services with no downtime
Avoid
- Replatformed checkout, lifting completion by 12% (as part of a team of six)
- Was involved in a large-scale migration project alongside several other teams
The pattern is: state the piece you owned, then the result the whole thing produced. You get credit for the impact without claiming the whole project.
A five-minute audit
Read every bullet on your resume and ask three questions. Any bullet that fails all three should be cut or rewritten:
- Does it contain a number, a scale, or a clear before-and-after?
- Would a peer in my field find it non-obvious — or does it just describe the job title?
- Could I talk about it for two minutes if asked?
- Does it use vocabulary the target job description uses?
- Is it under two lines?
Most people find that a third of their bullets are duties rather than achievements. Cutting them makes the resume shorter and stronger at the same time — which is usually what a “make it one page” instruction actually requires.
Frequently asked questions
How many bullet points should each job have on a resume?
Three to five for your recent and most relevant roles, one to two for older or less relevant ones. Consistency matters less than relevance — it is fine for your current job to have five bullets and a role from eight years ago to have one.
What if my work genuinely cannot be quantified?
Look for scale (how many people, accounts, or items), time (how much faster or more often), or a before-and-after state (from an untracked spreadsheet to a shared system used by four teams). A described transition is far stronger than a duty, even without a percentage.
Should resume bullet points be full sentences?
No. Drop the leading “I” and any articles you can spare, and start with a verb: “Cut onboarding time from 6 weeks to 2 by scripting environment setup.” Keep punctuation consistent across all bullets, whether or not you end them with full stops.
Is it dishonest to estimate metrics on a resume?
Not if the estimate is reasonable and you can explain how you arrived at it. Signalling the approximation — “~5 hours a week”, “roughly 200 accounts” — is honest and specific. Inventing a precise figure you cannot defend in an interview is the thing to avoid.