Resume bullet points examples: before and after

Why most resume bullets are too vague

Hiring managers read dozens of resumes for a single role. A bullet like 'Responsible for managing social media accounts' tells them nothing about scale, impact or skill level. It could describe a part-time intern or a team lead overseeing a seven-figure ad budget.

The fix is a three-part structure: action verb, scope (team size, budget, volume, geography, time frame), and result (a number, a percentage, a named outcome). When all three are present, the reader can picture the job and judge whether your experience matches theirs.

The action, scope, result formula

Action is the verb that opens the bullet. It should be specific and past tense for previous roles, present tense for your current one. Scope answers 'how much' or 'how many'. Result answers 'so what'.

Use this template as a starting point: [Strong verb] + [what you acted on] + [scope detail] + [measurable result]. Not every bullet will have a hard number, but every bullet should have at least a qualitative result if a quantitative one is not available.

• Action: Led, Reduced, Built, Negotiated, Automated, Launched, Trained, Audited
• Scope: across 12 markets, for a team of 8, covering a $2M budget, over 18 months
• Result: cutting processing time by 40%, generating $300K in new revenue, reducing churn by 15 percentage points

Before and after examples by role

The examples below cover five common roles. Each shows the original bullet, the problem with it, and a rewritten version using the formula.

1. Marketing coordinator | Before: 'Helped with email campaigns.' | Problem: No action, no scope, no result. | After: 'Wrote and scheduled 24 monthly email campaigns for a 45,000-subscriber list, lifting average open rates from 18% to 26% over one year.'
2. Software engineer | Before: 'Worked on backend services.' | Problem: Passive, no context, no outcome. | After: 'Refactored three legacy REST APIs serving 2 million daily requests, reducing average response time from 420 ms to 95 ms.'
3. Sales representative | Before: 'Exceeded sales targets.' | Problem: Vague claim with no numbers. | After: 'Closed $1.4M in new business in FY 2025, finishing 118% of quota and ranking second on a 22-person team.'
4. Operations manager | Before: 'Managed warehouse staff.' | Problem: No scope, no result. | After: 'Supervised a 34-person warehouse team across two shifts, reducing pick-and-pack error rate from 4.2% to 0.9% in six months.'
5. Customer success manager | Before: 'Improved customer satisfaction.' | Problem: No metric, no method. | After: 'Redesigned the 90-day onboarding journey for mid-market accounts, raising NPS from 31 to 58 across a portfolio of 60 clients.'

What to do when you have no numbers

Not every role produces clean metrics. If you cannot find a number, use a qualitative result that is still specific. Name the stakeholder who benefited, the process that changed, or the problem that no longer exists.

You can also estimate honestly. If you handled roughly 80 support tickets a week, say so. If your project covered three countries, say three countries. Ranges are acceptable: 'reduced onboarding time by an estimated 30 to 40 percent based on team feedback.' Estimates are far stronger than nothing, as long as you can defend them in an interview.

Another option is to describe scope alone when result data is unavailable. 'Managed vendor relationships across 11 suppliers in the UK and Ireland' is more useful than 'Managed vendor relationships' even without a result attached.

Tailoring bullets to the job description

A bullet that is strong on its own can still miss if it does not reflect the language of the posting. Applicant tracking systems in 2026 still parse for keyword matches before a human reads the file. If the job description says 'cross-functional collaboration' and your bullet says 'worked with other teams', you may be filtered out even though the experience is identical.

Read the posting carefully and mirror its phrasing where it is accurate to your experience. Do not copy phrases that do not apply. Change 'coordinated with stakeholders' to 'partnered with product, legal and finance stakeholders to launch three compliance features on schedule' if that is what you actually did.

Break-In Bad's resume enhancement conversation asks you up to 20 questions about your experience and rewrites each bullet to match the specific job you are applying for, using only facts you confirm. It checks every line against what you said and keeps your original on file, so nothing is invented or exaggerated.

Common mistakes to fix before you submit

Even well-intentioned bullets often carry a few recurring errors. Catching these before submission takes less than ten minutes and meaningfully improves how the resume reads.

• Starting with 'Responsible for' or 'Duties included': replace with a direct action verb
• Using the same verb repeatedly: vary across Led, Built, Reduced, Negotiated, Launched, Trained
• Burying the result at the end of a long sentence: move the number earlier if it is strong
• Listing tasks without outcomes: add 'resulting in', 'which reduced', or 'enabling' to connect action to impact
• Using jargon the reader may not know: spell out acronyms on first use and avoid internal project names
• Writing bullets longer than two lines: split them or cut the weakest detail