A recruiter gives your resume about 7.4 seconds (The Ladders). In that window they are not reading your degree or your company logo. They are skimming the first bullet under your most recent job. If it says "worked on the payment system," they move on. That one line decides more than your title does.
So treat bullets as the highest-leverage real estate on the page. There is a formula, and once you see it you cannot unsee the weak version.
The four-part formula
Action verb, what you built, the tech, the outcome. Drop any part and the line sags.
"Worked on the payment system" has none of them. "Built a Python payment service handling millions in transactions yearly at 99.99% uptime, cutting failures 40%" has all four and tells a whole story in a line. The point is not length, it is that nobody else could have written the second one about themselves.
Before and after
- "Developed APIs" becomes "Built 12 FastAPI endpoints for 50K daily users, response time 800ms to 120ms."
- "Made UI components" becomes "Built a React component library across 4 teams, dev time down 30%, 98 Lighthouse a11y."
- "Set up CI/CD" becomes "GitHub Actions pipeline with auto test and deploy, weekly releases to daily."
- "Built data pipelines" becomes "Airflow pipelines, 50M records/day from 12 sources, freshness 24h to 15min."
The numbers you swear you don't have
The most common excuse is "I don't have metrics." You do, they're just unrecorded. Your dashboards hold before-and-after latency, error rates, uptime. Git and Jira hold PRs, issues, release frequency. Your PM knows the user count, finance knows revenue, infra knows the cloud bill. Ask; "I'm updating my resume" is a normal reason. When a figure is genuinely gone, round honestly: "thousands of users," "around 40% faster." Tailored, quantified bullets lift callbacks about 30% (Jobscan).
| Impact type | Counts | Example |
|---|---|---|
| Performance | latency, throughput | "p95 2s to 200ms with Redis" |
| Scale | users, requests, data | "50M records/day from 12 sources" |
| Quality | bugs, coverage | "coverage 35% to 85%, bugs down 60%" |
| Business | revenue, cost | "cloud spend down ~25%" |
Lead with the strongest; money and scale beat volume. "Wrote 200 tests" is fine but less rare than "cut deploys 90%."
Verbs decide the first impression
| Use | Neutral | Avoid |
|---|---|---|
| Built, Designed, Led, Migrated, Cut | Developed, Maintained | Responsible for |
| Automated, Scaled, Shipped | Supported, Contributed | Worked on, Helped with |
The verb is the first word a skim catches. "Responsible for the API" describes a job; "Cut API latency 85%" describes you.
Count by level
Three to four bullets for early-career roles, five to six for recent mid and senior ones, fewer for old jobs. Lead each role with its strongest line. Skip the self-ratings ("Python 9/10" means nothing) and the unrelated trophies. Every bullet earns its row or gets cut. Early-career with no work metrics still counts: stars on a project, a top hackathon finish, merged PRs, hours saved by an intern automation. Same shape, action, what, number.
Key takeaways
- Bullets, not credentials, win the 7-second skim.
- Formula: verb, what, tech, outcome. Drop one and it weakens.
- You have metrics, in dashboards, Git, and people's heads; round honestly.
- Lead with strong verbs and your biggest number.
FAQ
What is the formula for a strong resume bullet?
Action verb plus what you built plus the technology plus a measurable outcome. "Built a FastAPI service for 50K users, latency 800ms to 120ms" beats "worked on APIs" because all four parts are present.
What if I don't have any numbers?
You do, unrecorded. Pull latency and uptime from monitoring, PR counts from Git, user and revenue figures from your PM or finance. When precise data is gone, an honest estimate beats a vague verb.
How many bullets per job?
Three to four early-career, five to six for recent roles, two to three for jobs older than seven years. Lead with the strongest result in each role.
Not sure which bullets are weak? Get a Resume Roast for line-by-line feedback, or run an ATS check for keyword match.