How to Write Resume Bullet Points That Actually Impress (With 50+ Examples)
Your bullet points are your resume. Everything else — the header, the formatting, the education section — is context. The bullets are where you either sell yourself or sink yourself. And most people are sinking.
The problem is almost universal: job seekers write about what they were responsible for instead of what they actually accomplished. A list of duties tells the recruiter what your job was. A list of achievements tells them how good you were at it.
The XYZ Formula
Google’s former SVP of People Operations, Laszlo Bock, popularized this formula: “Accomplished [X] by doing [Y], resulting in [Z].”
- X = what you achieved (the action and result)
- Y = how you did it (the method, tool, or approach)
- Z = the measurable outcome (the metric or business impact)
Not every bullet needs all three components, but every bullet needs at least X and either Y or Z. If your bullet has none of these, it’s a duty — not an accomplishment.
Duties vs. Accomplishments: The Core Problem
Here’s the most common pattern on resumes that get ignored:
• Handled customer complaints and inquiries
• Conducted weekly status meetings
• Maintained company database
• Assisted with quarterly reports
Every one of these describes a task assigned to you, not something you achieved. They could apply to anyone in that role. They don’t tell the recruiter why you were good at it.
• Resolved 340+ customer escalations per quarter with 97% satisfaction rating, earning Customer Champion award
• Redesigned sprint planning format adopted by 4 cross-functional teams, cutting meeting time from 2 hours to 45 minutes
• Migrated 2.3M records from legacy Oracle to PostgreSQL with zero data loss during 99.9% uptime window
• Built automated reporting pipeline with Python + Tableau, saving finance team 15 hours per quarter
The Action Verb Rule
Every bullet point should start with a strong action verb. Not “Responsible for,” not “Helped with,” not “Assisted in.” A single, powerful verb that communicates agency and impact.
The verb you choose signals your level. “Helped implement” sounds junior. “Architected and deployed” sounds senior. Same work, completely different impression.
50+ Before-and-After Examples by Industry
Software Engineering
Marketing
Sales
Finance
Product Management
Design
Operations
Human Resources
Customer Success
Data Science
How Many Bullet Points Per Role?
- Current/most recent role: 4–5 bullets. This is your main selling section
- Second most recent: 3–4 bullets
- Older roles (3+ years ago): 2–3 bullets
- Very old roles (7+ years ago): 1–2 bullets or omit entirely
Total across all roles: 12–18 bullets for a one-page resume. If you’re over 20, you’re including filler.
The “I Don’t Have Metrics” Problem
This is the most common objection: “I don’t have access to revenue numbers or ROI data.” You probably have more metrics than you think. Try these:
- Team size: “Led team of 6 engineers”
- Volume: “Processed 500+ customer tickets per week”
- Time saved: “Reduced report generation from 4 hours to 20 minutes”
- Scope: “Managed $2.5M annual budget”
- Frequency: “Conducted 15 user interviews per sprint”
- Adoption: “Tool adopted by 200+ employees company-wide”
- Accuracy: “Maintained 99.8% data accuracy across 3 systems”
- Estimates are fine: “Reduced processing time by approximately 40%”
If you genuinely can’t quantify, describe scope and impact qualitatively: “Implemented new testing protocol adopted as standard across all 8 regional offices.”
Bullet Point Length
The ideal bullet point is one line, two at most. If a bullet runs three lines, it probably contains two separate accomplishments — split it. If it’s a single long sentence, tighten the language.
Common Bullet Point Mistakes
- “Responsible for” — passive, vague, everybody writes this. Replace with a strong verb
- “Helped” / “Assisted” — minimizes your contribution. If you did the work, own it
- “Various” / “Multiple” — be specific. “Various projects” = you can’t remember what you did
- Listing tools without context — “Used Python and SQL” says nothing. “Built ETL pipeline in Python processing 2M daily rows via SQL” says everything
- Buzzword soup — “Leveraged synergistic cross-functional alignment” makes recruiters gag. Write like a human
- Starting every bullet the same way — vary your verbs. Don’t start 4 bullets with “Managed”
The Bullet Point Checklist
Before you submit your resume, run every bullet through this filter:
- Does it start with a strong action verb? (Not “Responsible for”)
- Does it describe an accomplishment, not a duty?
- Does it include at least one number or measurable outcome?
- Could someone else in your exact role have written this, or is it specific to your impact?
- Is it one to two lines max?
- Would your boss or a coworker agree this is accurate?
If a bullet fails more than one of these checks, rewrite it or cut it.
The Bottom Line
Your resume bullet points are the difference between “looks like everyone else” and “let’s interview this person.” Stop listing what you were supposed to do. Start describing what you actually accomplished, how you did it, and what the result was.
Use the XYZ formula. Start with powerful verbs. Include at least one number per bullet. Keep it to one line when possible. And if you’re not sure whether a bullet is strong enough — it probably isn’t.
Are your bullet points actually working?
Upload your resume and get a brutally honest AI audit. We’ll score your bullets, flag vague language, and tell you exactly which ones need rewriting.
Roast My Resume — Free →