Almost every bad resume bullet I've ever read has the same shape. It starts with "Responsible for" or "Helped with." It describes a task. It doesn't tell me what changed because of you.
Almost every good resume bullet I've ever read has the opposite shape. It describes an outcome. It often contains a number. It sounds like something the team would have noticed if you'd left.
This guide is the bridge. Start with the pattern, then the 28 before/after examples across six functions.
Duty vs. achievement: the difference
A duty is what the job description said. An achievement is what happened because you showed up.
Responsible for managing the company's social media accounts and posting content on a daily basis.
Grew Instagram following from 4k to 38k in 14 months through a shift to short-form native video — CPA on brand campaigns dropped 62%.
The first sentence could be copied from a job description. The second could only be written by the person who did the work.
The bullet pattern that works
The pattern I teach is three components, in this order:
- Action verb — what you did (past tense for old jobs, present for current).
- Object — what you did it to, with context.
- Outcome — what changed, ideally with a number.
[Verb] [thing] [how/why] — [what changed].
Example: Redesigned the onboarding flow to surface the 'invite team' step earlier — activation rate up 18%.
Three things to notice:
- The verb is load-bearing. Don't start with "Worked on" or "Helped with."
- The "how" is where your choices show up. "Redesigned the onboarding flow" is generic; "Redesigned the onboarding flow to surface the invite-team step earlier" tells me you had a hypothesis.
- The outcome validates the choice. Without it, I'm taking your word for it.
What if my work doesn't have numbers?
Most work has numbers attached — people just don't notice them. Try this list of questions. One or two of them will give you a metric:
- Time: How long did it take before? After? Saved per week? Per person?
- Money: Budget you managed. Cost saved. Revenue generated or protected. Contract value.
- People: Team size led. Direct reports. Cross-functional stakeholders. Students taught.
- Volume: Tickets handled, users served, requests processed, features shipped, documents drafted.
- Percentage change: Anything you improved, by how much? Even "reduced by 1/3" is a number.
- Ranking: Top X% of sellers. #2 out of 18 analysts. Highest-rated TA that semester.
- Before/after: Didn't exist before you → exists now. Was broken → works. Took three people → takes one.
If genuinely no number applies, describe the scope or the mechanism. "Led the first end-to-end localization of the product across six languages, coordinating vendor translators and in-house review" — no hard number, still clearly substantial work.
Examples: Engineering
Worked on the payments system.
Led migration of the payments service from monolith to a dedicated service — p99 checkout latency dropped from 840ms to 220ms, and failed transactions fell 41%.
Responsible for writing tests.
Introduced integration-test coverage to the billing module (0 → 74%), catching three production-bound bugs before release during the first quarter.
Fixed bugs reported by QA.
Cleared a 4-year bug backlog (162 issues) across the inventory service — median time-to-fix from 72 days to 9.
Helped with code reviews.
Owned the team's PR review rotation; review-to-merge time fell from 2.3 days to under 6 hours.
Wrote documentation.
Documented the auth service from scratch — new-hire onboarding time for the subsystem dropped from ~2 weeks to ~3 days (tracked across 8 hires).
Worked on performance improvements.
Profiled and rewrote the search index pipeline in Rust — throughput 18× higher, hardware footprint cut in half.
Examples: Design
Designed the checkout flow.
Redesigned the checkout flow to reduce steps from 5 to 2 — conversion up 11%, mobile conversion up 19%.
Responsible for the design system.
Built and shipped the company's first design system — adopted by 4 product teams, design-to-dev handoff time cut by ~40%.
Worked with the research team.
Partnered with research on 12 rounds of usability testing for the onboarding redesign; task-success rate rose from 58% → 91%.
Created marketing visuals.
Art-directed a 9-asset campaign for the Q3 launch — ad CTR 2.4× the prior quarter's average at the same spend.
Did accessibility work.
Led the WCAG 2.2 AA audit across 140 screens; closed 312 issues, unblocking contracts with two government customers.
Examples: Marketing
Ran email campaigns.
Ran lifecycle email program covering 8 touchpoints — open rate 44% (industry avg 22%), contributing $1.2M in pipeline.
Managed social.
Grew company Twitter from 8k to 61k followers in 18 months; inbound demo requests from Twitter up 4.2×.
Wrote blog posts.
Authored 24 SEO-targeted posts in a single year; organic traffic to the blog 3.1× YoY, two posts ranking #1 for target terms.
Helped with webinars.
Produced and hosted 14 partner webinars averaging 420 attendees; attributed MQLs 38% above target.
Managed paid ads.
Rebuilt the paid search portfolio around intent-stage keywords — blended CAC down 34% over two quarters on a $2.4M annual budget.
Examples: Sales & CS
Met my sales targets.
Hit 128% of quota three quarters running; closed the largest deal in the region ($640k ACV).
Handled accounts.
Managed a book of 34 enterprise accounts (~$18M ARR); net revenue retention 118% in FY24.
Onboarded customers.
Redesigned the first-30-day onboarding playbook — median time-to-first-value from 22 to 9 days, 90-day churn down 37%.
Worked on renewals.
Ran the mid-market renewal desk — 94% gross retention on $12M book, 4 points above the prior year.
Examples: Ops & Finance
Handled monthly close.
Cut monthly close from 11 to 5 business days by restructuring the intercompany reconciliation process.
Managed vendors.
Renegotiated a $3.2M/year cloud contract — 28% savings locked for 24 months, same SLAs.
Ran payroll.
Owned semi-monthly payroll for 620 employees across 8 states — zero late payments, zero reclass corrections over 24 cycles.
Built financial models.
Built the three-statement driver model used for Series C; post-investment, actuals within 4% of model through first four quarters.
Examples: Support
Answered tickets.
Handled ~110 tickets/week at 96% CSAT; top-3 ticket-solver on the team for three consecutive quarters.
Wrote help articles.
Authored 34 help-center articles covering the top 20 inbound topics — ticket deflection from those topics up 41%.
Escalated bugs.
Partnered with engineering on triage for high-severity issues — median resolution time from 9 to 2.5 days across P1/P2 tickets.
Drafting new bullets? The editor fits them for you
LuckyResume scales your page as you write — add the bullet, move on. The layout takes care of itself.
Common bullet mistakes
1. Fabricated precision
Do not write "Increased efficiency by 37.2%" unless you actually measured it. "Increased efficiency by roughly a third" or "Cut report-generation time in half" is both more honest and more credible.
2. Stacking verbs
"Built, maintained, scaled, deployed, architected…" — pick one. Verb-stacking is what people do when they don't know what the accomplishment was.
3. Passive voice
"The new dashboard was built, with involvement from multiple teams." Who built it? You or not? Say so.
4. Adjectives doing the heavy lifting
"Delivered a very successful campaign" — "very successful" is empty without a number. Either add the number or rewrite without the adjective.
5. Bullets about team accomplishments with no you in them
"The team shipped X." Fine — but what did you do? Led the spec? Wrote the backend? Coordinated QA? Name your role.
The short version
- Start every bullet with a verb.
- End every bullet with an outcome.
- If you don't have a number, describe scope or mechanism.
- Don't invent precision. Honest round numbers beat fake exact ones.
- The reader should be able to tell what would have been worse if you weren't there.