Most resumes fail on the bullet points. The layout is fine, the spelling is fine, the experience is real — and then each job reads like a copy of the original job description. Recruiters skim past it in six seconds and move on to the next candidate.
This guide covers the formula that actually works, a handful of before/after rewrites across roles, and the three mistakes that make otherwise strong careers look weak on paper. If you only fix your bullets — nothing else — your interview rate usually moves within a week.
What a bullet point is actually competing against
When a recruiter opens your resume, they're not reading it — they're scanning it for reasons to say yes. A typical first-pass is somewhere between six and twelve seconds, and in that window their eyes track to three places: your most recent job title, the first bullet under it, and your top-line education or certification. Everything else is peripheral until one of those three signals tells them you're worth a closer look.
That is the real constraint. Your first bullet under each job has to do more work than any other line on the page. If it reads like "Responsible for managing a team of five engineers", the recruiter's signal is: this person describes their job, not their work. They move on.
The 4-part bullet formula
Every strong resume bullet contains four elements. You can reorder them, you can compress a couple together, but all four have to be there:
- Action — what you actually did. A specific verb: shipped, migrated, closed, diagnosed, designed, negotiated. Not responsible for, not helped, not worked on.
- Scope — the size of the thing you acted on. Team size, budget, request volume, caseload, transaction volume, lines of code, number of customers, document count.
- Method — how you did it. One or two words about the approach, tool, or framework. "Using Python", "on Greenhouse", "via event-driven refactor", "on a 4-therapist rotation".
- Outcome — the measurable result. A number, percentage, dollar amount, or a clearly better state. If you can't cite a number, cite a comparison ("vs team baseline", "across two quarters").
Put them together and you get something like:
Migrated billing service from a synchronous monolith to event-driven architecture (Kafka + Go microservices), cutting P95 latency from 420ms to 180ms across 6 downstream teams.
Action: migrated. Scope: billing service, 6 downstream teams. Method: event-driven, Kafka + Go. Outcome: 420ms → 180ms P95 latency. The recruiter calibrates your seniority, your stack, and your impact in one line.
The 30-second rewrite test
Before you rewrite anything, run each bullet through three questions:
- Would this bullet be true for anyone else with my job title? If yes, it's a job description, not an accomplishment. Rewrite.
- Can the reader picture the scale? If not, add a number. Even a rough one. "A few hundred" is infinitely better than nothing.
- Is there a comparison point? "Improved conversion" is weak. "Lifted checkout conversion from 2.8% to 3.6% over one quarter" is strong. The baseline matters more than the delta.
Before/after rewrites across 6 roles
Software engineer
Before: Responsible for backend services and mentoring junior developers.
After: Led migration of billing service to event-driven architecture (Kafka + Go), cutting P95 latency from 420ms to 180ms across 6 downstream teams; mentored 3 juniors to Senior within 18 months.
Product manager
Before: Worked with engineering and design to launch new features.
After: Launched 4 features on the checkout surface in 2024 (shipping cadence 1/quarter); the bundled shipping estimator drove checkout conversion from 2.8% to 3.6% (+$3.1M annualized GMV).
Nurse (RN, med-surg)
Before: Provided patient care on a busy medical-surgical floor.
After: Staff RN on 32-bed med-surg floor, typical assignment 5-6 patients nights; charge-nurse rotation every third shift. Precepted 4 new-grad RNs through 12-week orientation in 2024; all four cleared competency on first assessment.
Sales (enterprise AE)
Before: Exceeded quota and built strong customer relationships.
After: Carried $1.4M annual quota on mid-market; closed $1.67M in FY24 (119% attainment, #3 of 28 reps). Landed two net-new logos in the manufacturing vertical, each $280k ACV on a 4-month sales cycle.
Teacher (high school math)
Before: Taught algebra and geometry to high school students.
After: Taught 5 sections of Algebra I and Geometry (135 students total) on a 90-minute block schedule; rewrote the Algebra I scope-and-sequence to front-load equation-solving — state-assessment pass rate moved from 71% to 84% in one year, department high.
Designer (product)
Before: Designed user interfaces and collaborated with engineers on new features.
After: Led end-to-end design on the onboarding redesign (from 6-step flow to 3-step); week-1 activation moved from 44% to 61% across 120k new signups in the first month post-launch. Owned the component library migration to Figma variables; reduced dev hand-off questions by ~60% based on the Slack channel volume.
Three mistakes that quietly break bullets
Mistake 1: Leading with tools instead of impact
"Used Python, React, and AWS to build customer-facing features." The tool list is fine — in your skills section. In a bullet, it steals the opening line from the outcome. Put the what and the result first, then mention the tool in passing:
Shipped self-serve refund flow (React + Python/Django + Stripe), cutting support tickets by 1,800/mo and saving an estimated 180 agent-hours/week.
Mistake 2: Using passive voice
"Was responsible for leading the redesign" is instantly weaker than "Led the redesign". Passive voice distances you from the work. Every bullet should start with a past-tense verb you actually did. A quick check: if you can insert "by me" at the end and it reads fine, you're in passive voice.
Mistake 3: Hiding the number mid-sentence
Numbers should land early enough in the bullet that a skimmer catches them. "In a team-wide effort spanning two quarters and many stakeholders, we ultimately managed to improve the conversion rate by roughly 29%" loses the 29% in the crowd. Rewrite with the number near the front:
Drove checkout conversion from 2.8% to 3.6% (+29%) over two quarters via four A/B-tested UX changes.
When you don't have numbers
Some roles genuinely don't produce clean metrics — early career, research, creative work, roles that feed into someone else's pipeline. That doesn't mean write vague bullets. Use scope indicators instead:
- Volume — "Reviewed 180k pages across 4 productions in Relativity" (paralegal).
- Frequency — "Ran weekly design critiques for a 12-person product-design org".
- Comparison — "Outbound sourcing yield 68% of 2024 hires vs team baseline 44%" (recruiter).
- Adoption — "Protocol adopted as clinic standard after 28-patient case series" (PT).
- Geography or segment — "Closed $14.2M across 38 homes in North Austin, $350-600k range" (agent).
Scope is nearly as good as outcome for calibrating a reader. What you can't fall back on is vague adjectives — "excellent", "strong", "high-performing". Every resume has those. They carry zero information.
How many bullets per job?
Rough targets, by recency:
- Current or most recent role: 4-6 bullets. This is where the density should be.
- Previous role (2-5 years ago): 3-4 bullets.
- Roles 5-10 years back: 2-3 bullets, focused on the most transferable wins.
- Roles older than 10 years: 1-2 bullets or a single-line summary, unless they're directly relevant to the target job.
A 12-bullet current job on a resume is a warning sign — it signals the author couldn't prioritize. A 1-bullet current job is the opposite warning sign — either the role is thin or the author isn't selling it. Aim for 4-6 with the strongest first.
Putting it to work
A good practical workflow:
- Pull your current resume into a draft document. For each bullet, write a 1-sentence answer to: "What was the outcome, and how big was it?"
- For bullets where you don't know the number, ask a teammate, dig through Slack, or check your last performance review. Most people have more quantifiable work than they remember.
- Rewrite each bullet against the 4-part formula. Action + Scope + Method + Outcome.
- Run the result through our ATS checker — it flags weak-verb openers, missing numbers, and bullets that are too long to scan. The ATS playground goes further with AI-powered rewrites when you're authenticated.
- If you want tested starting points, the resume examples library has 20+ roles with sample bullets already written against this formula. Start with the one closest to your job and adapt.
Good bullets are not about sounding impressive. They're about being legible in six seconds to someone who has 300 resumes left to read. The formula isn't a style choice; it's what legibility looks like at scale.