Resume Bullet Points That Actually Work (With Examples)
A strong bullet tells a three-part story in under fifteen words: what you did, how you did it, what happened because of it. Most resumes miss at least two of those parts.
Recruiters spend less than ten seconds per resume on the initial pass. Your bullets are doing the heavy lifting of whether you make the second pass. Here's what makes them work.
The formula
Strong bullets hit three things: a strong verb, a specific action, and a measurable result. Missing any one and the bullet is weaker than it could be.
- Verb first: Shipped, Led, Cut, Built, Grew — not "Responsible for"
- Specific: what did you actually do, in concrete terms
- Quantified: numbers, percentages, timelines, scale — "reduced build time by 40%" beats "improved build times"
Examples by role
Software engineer
Before
Worked on improving database performance and wrote new queries.
After
Optimized 40+ production queries on a 2TB Postgres instance, cutting p95 latency from 840ms to 210ms
Marketing manager
Before
Responsible for content strategy and social media.
After
Grew organic blog traffic from 8K to 47K monthly visits in 10 months via a long-tail keyword strategy
Nurse
Before
Helped patients in a fast-paced ICU environment.
After
Managed 4:1 patient load in 24-bed cardiothoracic ICU; precepted 3 new-grad RNs through competency checkoff
Product manager
Before
Led product launches and worked with engineering.
After
Launched 3 enterprise features used by 60% of $100K+ ARR customers, driving $1.2M in NRR
What to avoid
- Passive voice ("was responsible for") — always active
- Vague scale ("a lot of customers") — either give a real number or drop it
- Adjectives without proof ("impactful project") — show the impact, don't claim it
- Stacking too many numbers — one quantified outcome per bullet is enough; more reads as showing off
Ready to put this into practice?
Build a one-page resume that enforces these rules for you — AI bullet rewriter, ATS match, forced one-page layout.
Try onepage.bio — free