The difference between a forgettable resume bullet and one that makes a recruiter stop scrolling is almost always one thing: a specific, strong action verb followed by a quantified result.
"Responsible for backend development" → forgettable. "Rebuilt the payment processing backend, reducing transaction failures from 4.2% to 0.1%" → stops the scroll.
Here are 200 action verbs organized by what they communicate, with examples of how to use them.
Category 1: Built / Created / Shipped
Use when describing systems, features, or tools you built from scratch.
Verbs: Architected, Built, Constructed, Created, Designed, Developed, Engineered, Established, Implemented, Launched, Prototyped, Shipped, Spun up, Stood up, Wrote
Weak: Responsible for developing new features. Strong: Engineered a real-time notification system serving 2M+ users, reducing notification latency from 8 seconds to under 200ms.
Weak: Worked on the mobile app. Strong: Built the iOS onboarding flow from scratch, reducing drop-off rate by 34% in the first 30 days.
Category 2: Improved / Optimized
Use when describing performance improvements, efficiency gains, or quality increases.
Verbs: Accelerated, Boosted, Compressed, Decreased, Enhanced, Halved, Improved, Minimized, Optimized, Reduced, Refactored, Sped up, Streamlined, Trimmed, Tuned
Weak: Improved app performance. Strong: Optimized database query patterns using connection pooling and index tuning, reducing p99 API response time from 2.3s to 380ms.
Weak: Made the CI pipeline faster. Strong: Refactored the CI pipeline to run test suites in parallel, reducing build time from 22 minutes to 6 minutes.
Category 3: Led / Owned / Drove
Use when describing ownership, leadership, or driving projects to completion.
Verbs: Championed, Drove, Guided, Led, Managed, Mentored, Owned, Pioneered, Spearheaded, Steered
Weak: Was involved in migrating to the cloud. Strong: Led the migration of 14 microservices from on-prem to AWS, completing on schedule with zero production incidents.
Weak: Helped with technical direction. Strong: Drove the adoption of TypeScript across 3 frontend codebases, reducing runtime errors by 40% and improving developer onboarding time.
Category 4: Solved / Fixed / Debugged
Use when describing problems you investigated and resolved.
Verbs: Debugged, Diagnosed, Eliminated, Fixed, Identified, Investigated, Mitigated, Patched, Remediated, Resolved, Resolved, Stabilized, Triaged
Weak: Fixed bugs in the authentication system. Strong: Diagnosed and patched a race condition in the OAuth token refresh flow that was causing 0.8% of login attempts to silently fail.
Weak: Helped resolve an outage. Strong: Identified a memory leak in the image processing service causing weekly OOM crashes; patching it reduced service restarts from 7/week to zero.
Category 5: Scaled / Grew
Use when describing systems or teams you helped scale.
Verbs: Expanded, Extended, Grew, Horizontally scaled, Migrated, Scaled, Sharded, Supported growth of
Weak: Worked on scaling the database. Strong: Sharded the user database to support 10x growth, scaling from 5M to 50M records without downtime.
Category 6: Designed / Architected
Use when describing system design, API design, or architectural decisions.
Verbs: Architected, Defined, Designed, Drafted, Established, Formalized, Laid out, Mapped, Modeled, Planned, Proposed, Scoped, Structured
Weak: Designed the API. Strong: Designed a RESTful API consumed by 4 downstream teams, with full OpenAPI documentation and versioning strategy that reduced breaking changes by 80%.
Category 7: Collaborated / Partnered
Use when describing cross-functional work or team collaboration.
Verbs: Collaborated, Coordinated, Facilitated, Partnered, Synchronized, Unified, Worked alongside
Note: Use these verbs sparingly on a software engineer resume — every bullet should ideally have a strong individual ownership verb. Use collaboration verbs when the cross-functional nature of the work is itself the achievement.
Weak: Collaborated with PM and design. Strong: Partnered with product and design to define technical requirements for a new search feature, reducing discovery-to-implementation rework by 60%.
Category 8: Automated / Streamlined
Use when describing process improvements, tooling, or automation work.
Verbs: Automated, Codified, Eliminated, Formalized, Integrated, Standardized, Streamlined, Systematized, Templated
Weak: Automated some deployment tasks. Strong: Automated the staging deployment pipeline, eliminating 2 hours of manual work per release and reducing deployment errors from 1 in 5 to zero.
Category 9: Mentored / Taught
Use for senior and staff-level resumes to demonstrate leadership and investment in others.
Verbs: Coached, Cultivated, Guided, Mentored, Onboarded, Supported, Trained
Weak: Helped junior engineers. Strong: Mentored 3 junior engineers through their first production deployments; all three were promoted within 18 months.
Category 10: Researched / Evaluated
Use when describing technical spikes, vendor evaluations, or technical decision-making.
Verbs: Analyzed, Assessed, Benchmarked, Compared, Evaluated, Investigated, Prototyped, Researched, Vetted
Weak: Evaluated different database options. Strong: Benchmarked 4 database solutions (PostgreSQL, DynamoDB, Cassandra, MongoDB) for a time-series data use case; recommendation adopted saved $40K/year in infrastructure costs.
The Formula That Makes Any Verb Work
A strong verb alone isn't enough. The formula is:
[Verb] + [What] + [Result]
Every bullet that follows this formula is stronger than one that doesn't. The verb gets the recruiter's attention. The "what" provides context. The result provides proof.
| Without result | With result | |---|---| | Refactored the authentication system | Refactored the authentication system, reducing login time from 1.8s to 400ms | | Optimized SQL queries | Optimized 12 critical SQL queries, reducing database CPU utilization by 35% | | Built a CI/CD pipeline | Built a CI/CD pipeline from scratch that cut deploy time from 45 minutes to 8 |
What to Avoid
"Responsible for" — This is passive. It says you were assigned to something, not that you accomplished it. Replace with any ownership verb.
"Helped with" — Unless your role was genuinely supporting, find the specific thing you did and own it. "Helped build" → "Built [specific component]."
"Worked on" — Too vague. What did you specifically do?
"Involved in" — Never use this on a resume. It communicates no ownership whatsoever.
"Assisted" — Use only when accurate (junior roles, support functions). If you actually did the work, use an ownership verb.
Use CareerLift's resume analyzer to check your resume bullets against these patterns and get specific suggestions for stronger verbs and missing metrics.