Resume Bullet Points: Turning Duties Into Evidence (Formula + 20 Examples)

Open your resume and count how many bullets begin with "Responsible for". Each one is a job description masquerading as an accomplishment — it says what the role was supposed to involve, not what happened because you were in it. Recruiters read hundreds of these; they've learned that duty-bullets carry no information, so their eyes slide off them.

The upgrade isn't fancier verbs. It's a different claim: evidence that you, specifically, moved something.

The formula: Action → Object → Outcome

[Verb] [what, with what scope] [, outcome with a number]

• Verb, past tense, specific. "Led", "built", "cut", "negotiated", "shipped" — not "helped with", "was involved in", "supported".
• Scope makes it credible. "Managed a budget" vs "managed a €2M budget" vs "managed a €2M budget across 4 vendors" — each added scope raises believability and seniority signal.
• Outcome makes it evidence. What changed because you did this? Faster, cheaper, more revenue, fewer errors, higher retention. When outcomes weren't measured, scope carries the bullet alone — that's still far ahead of a duty.

One bullet, one claim. Two accomplishments crammed into one line each get half-read.

Twenty before / after pairs

Software engineering

• ❌ Responsible for maintaining the front-end codebase
• ✅ Migrated a 120-component React codebase to TypeScript over 6 months with zero release freezes
• ❌ Worked on performance improvements
• ✅ Cut p95 page load from 4.1s to 1.8s by lazy-loading and code-splitting the dashboard

Product

• ❌ Involved in the product roadmap process
• ✅ Ran quarterly roadmap planning for a 3-squad product line, shipping 9 of 11 committed epics
• ❌ Responsible for user research
• ✅ Interviewed 40 churned customers, turning 3 recurring blockers into fixes that cut churn 15%

Marketing

• ❌ Managed social media accounts
• ✅ Grew LinkedIn from 2k to 30k followers in 14 months, driving 20% of inbound demo requests
• ❌ Helped with email campaigns
• ✅ Rebuilt the onboarding email sequence, lifting activation 9 points across 12k monthly signups

Sales

• ❌ Responsible for the DACH territory
• ✅ Grew DACH ARR from €800k to €2.1M in two years, closing the region's first three enterprise logos
• ❌ Did outreach to prospects
• ✅ Booked 15–20 qualified meetings monthly from cold outreach at a 4% reply-to-meeting rate

Operations

• ❌ Oversaw inventory management
• ✅ Cut stockouts 60% by introducing weekly demand reviews across 3 warehouses and 4k SKUs
• ❌ Handled vendor relationships
• ✅ Renegotiated 12 vendor contracts, saving €180k annually without service-level changes

Finance

• ❌ Responsible for month-end close
• ✅ Led month-end close for a €60M entity, cutting close time from 8 days to 5
• ❌ Prepared financial reports
• ✅ Automated board reporting in Power BI, replacing 20 hours of monthly manual work

Healthcare

• ❌ Provided patient care in the ICU
• ✅ Managed care for 3–4 critical patients per shift in a 20-bed ICU, precepting 6 new nurses
• ❌ Responsible for documentation
• ✅ Led the unit's transition to a new EHR, training 30 staff with zero documentation backlogs

Design

• ❌ Created designs for the mobile app
• ✅ Redesigned checkout across iOS and Android, raising completed purchases 11%
• ❌ Maintained the design system
• ✅ Built a 60-component Figma design system adopted by 5 product teams, halving design-to-dev handoff time

Data

• ❌ Analyzed data for stakeholders
• ✅ Built churn-risk scoring adopted by the CS team, focusing outreach that saved ~€300k ARR
• ❌ Responsible for dashboards
• ✅ Consolidated 14 ad-hoc reports into 3 self-serve dashboards used weekly by 50+ staff

Teaching / career change

• ❌ Taught high school science classes
• ✅ Designed and delivered a curriculum for 150 students across 5 sections, raising pass rates 18%
• ❌ Organized school events
• ✅ Ran a 300-attendee science fair on a €2k budget with 12 volunteer staff, now an annual program

The honesty guardrails

Numbers invite exaggeration, so the interview test applies with force:

• Estimated numbers are fine; invented ones aren't. "~40 weekly users" from memory is honest. A metric you never measured is a trap you'll step into mid-interview.
• Claim your slice. If the team shipped it, "led the migration of…" is true only if you led. "Built the reporting module of a 6-person platform rewrite" is precise, credible, and still impressive.
• Outcome unknown? Say the scope and stop. A true bullet without a number beats a false one with a great one — the false ones are exactly the lines interviewers happen to probe.

Tailoring: which bullets go first

Writing strong bullets is half the work; ordering them per job is the other half — top bullets get read, bullet five gets skimmed. Match the order to each job description's priorities using the same keyword extraction you use everywhere. (Re-ordering and re-wording per job is exactly the mechanical work Job SuitUp's agent proposes line-by-line — with each suggestion needing your approval, because the guardrails above are enforced, not optional.)

FAQ

How many bullets per job? Three to five for recent, relevant roles; one to two for older or less relevant ones. Total resume length follows from relevance, not history.

Every bullet needs a number? No — but every bullet needs a claim. Scope (team size, budget, volume) is a number too, and available for almost any job.

Which verbs should I avoid? "Responsible for", "helped", "assisted", "participated in", "worked on" — all describe proximity to work rather than work. If you truly assisted, name your actual contribution instead.

Should bullets be full sentences? Fragments, no period needed, no "I". Start at the verb: "Cut close time from 8 days to 5."