Rst / My / Resume
← Blog

How to Write Resume Bullet Points That Actually Impress (With 50+ Examples)

March 5, 2026  ·  14 min read
The XYZ bullet point formula showing weak resume bullets rewritten into strong accomplishment-driven bullets with action, method, and measurable result

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:

Duties (what most people write)
• Responsible for managing team of developers
• 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.

Accomplishments (what you should write)
• Led team of 8 developers through migration from monolith to microservices, reducing deployment failures 72%
• 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.

Power action verbs for resume bullet points organized by category: leadership, technical, growth, efficiency, analysis, and communication

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

Before
Worked on backend services for the platform.
After
Engineered 12 RESTful microservices handling 4M daily API calls with 99.95% uptime, reducing response latency 40%.
Before
Helped with code reviews.
After
Conducted 200+ code reviews annually, reducing production bugs 35% and establishing team-wide TypeScript style guide.
Before
Responsible for CI/CD pipeline.
After
Automated CI/CD pipeline with GitHub Actions, cutting deployment time from 45 minutes to 8 minutes and enabling 15+ daily releases.

Marketing

Before
Managed social media accounts.
After
Grew Instagram following from 8K to 47K in 9 months by launching UGC campaign and Reels strategy, driving 3.2K monthly site visits.
Before
Created content for the company blog.
After
Published 40+ SEO-optimized articles generating 125K organic visits/month, contributing to 22% of marketing-sourced pipeline.
Before
Ran email marketing campaigns.
After
Redesigned drip campaign sequence with A/B testing, improving open rates from 18% to 34% and conversion rate from 2.1% to 5.8%.

Sales

Before
Responsible for meeting sales targets.
After
Exceeded annual quota by 127% ($2.4M closed) across 35 enterprise accounts, ranking #2 of 28 reps nationally.
Before
Managed customer relationships.
After
Retained 94% of book of business ($8.2M ARR) by implementing quarterly business reviews and proactive renewal outreach.

Finance

Before
Prepared financial models.
After
Built 3-statement LBO model for $450M acquisition, identifying $12M in cost synergies that informed final bid price.
Before
Assisted with budget planning.
After
Led FP&A for $60M operating budget across 4 business units, delivering forecasts within 2% accuracy for 6 consecutive quarters.

Product Management

Before
Managed product roadmap.
After
Defined and shipped 14-feature roadmap for B2B SaaS platform, growing paid user base 38% and reducing churn from 8% to 4.2%.
Before
Worked with engineering on new features.
After
Partnered with 8-person engineering squad to launch self-serve onboarding flow, reducing sales-assisted setup by 60% and saving 120 CSM hours/month.

Design

Before
Designed UI for mobile app.
After
Redesigned checkout flow for iOS app (2M+ downloads), increasing completion rate from 54% to 78% through user testing with 40 participants.

Operations

Before
Improved operational processes.
After
Streamlined order fulfillment pipeline by implementing barcode scanning system, reducing picking errors 89% and cutting average ship time from 3 days to same-day.

Human Resources

Before
Handled full-cycle recruiting.
After
Filled 45 engineering roles in 6 months with 28-day average time-to-hire (vs. 42-day industry benchmark), maintaining 92% 1-year retention rate.

Customer Success

Before
Onboarded new customers.
After
Onboarded 60+ enterprise accounts per quarter with structured 30-60-90 day program, achieving 95% product adoption and NPS of 72.

Data Science

Before
Built machine learning models.
After
Developed churn prediction model (XGBoost, 91% AUC) that identified 2,400 at-risk accounts, enabling retention team to save $3.2M in ARR.

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.

Too long
Spearheaded the development and implementation of a comprehensive customer feedback system utilizing NPS surveys, Zendesk ticket analysis, and monthly focus groups, which resulted in the identification of 15 key product improvement areas and a subsequent 23% improvement in customer satisfaction scores over a 12-month period.
Right length
Built customer feedback system (NPS surveys + Zendesk analysis + focus groups), driving 23% improvement in CSAT over 12 months.

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:

  1. Does it start with a strong action verb? (Not “Responsible for”)
  2. Does it describe an accomplishment, not a duty?
  3. Does it include at least one number or measurable outcome?
  4. Could someone else in your exact role have written this, or is it specific to your impact?
  5. Is it one to two lines max?
  6. 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.

Related Articles
How to Quantify Your Resume Achievements (With Real Examples) → How to Tailor Your Resume for Every Job Application → The Best Resume Format in 2026 → 10 Resume Mistakes That Are Costing You Interviews →

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 →