Software Engineer Resume Bullet Points
16 examples, each shown weak and strong
A strong engineering bullet names the system, the constraint it ran under, and what moved after your change: latency, error rate, cost or deploy speed. Reviewers also look for ownership, so say which part you designed or shipped rather than what the team was near.
How to use these
- Every [X%], [N] and [$X] is a blank for your own figure. Fill it from your records, or a careful estimate you could explain in an interview. If you have no number, describe the result in words.
- Only use a bullet for work you actually did. Change the details until it describes your job, not this page.
- The ticks are three plain checks done in code: it opens with an action verb, it has a number, and it says what changed. Strong bullets pass all three; weak ones miss at least one.
Performance and scale
Reviewers want the size of the system and the metric that moved, measured before and after your change.
Weak
Worked on improving performance of backend APIs.
- ✗ Action verb
- ✗ Number
- ✓ Result
Strong
Profiled the checkout API under peak load and added Redis caching for product lookups, cutting p95 latency from [N] ms to [N] ms across [N] daily requests.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Optimized slow database queries.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Rewrote [N] slow PostgreSQL queries using composite indexes and EXPLAIN ANALYZE plans, reducing average report load time by [X%] for [N] internal users.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Responsible for scaling the platform as traffic grew.
- ✗ Action verb
- ✗ Number
- ✓ Result
Strong
Moved the image pipeline from a single server to a queue on AWS SQS and Lambda, absorbing traffic spikes of [N]x normal load and cutting monthly compute cost by [$X].
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Used Python and Docker to build services.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Built a Python ingestion service in Docker on Kubernetes that processes [N] events per second, replacing a nightly batch job and shortening data freshness from [N] hours to [N] minutes.
- ✓ Action verb
- ✓ Number
- ✓ Result
Reliability and incidents
Uptime, incident counts and recovery time show seniority more clearly than another feature launch.
Weak
Was part of the team's on-call schedule for production issues.
- ✗ Action verb
- ✗ Number
- ✗ Result
Strong
Led [N] incident postmortems as on-call engineer and shipped the follow-up fixes, reducing repeat Sev-2 incidents by [X%] over [N] quarters.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Fixed flaky tests in the CI pipeline.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Quarantined and fixed [N] flaky tests in GitHub Actions, raising the main-branch pass rate from [X%] to [X%] and saving engineers about [N] hours a week in reruns.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Helped set up monitoring and alerting.
- ✗ Action verb
- ✗ Number
- ✗ Result
Strong
Instrumented [N] services with Datadog dashboards and SLO-based alerts, cutting mean time to detect from [N] minutes to [N] minutes and noisy pages by [X%].
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Improved error handling in the payments service.
- ✓ Action verb
- ✗ Number
- ✓ Result
Strong
Added idempotency keys and retry backoff to the payments service, eliminating duplicate charges that had cost [$X] in refunds the prior quarter.
- ✓ Action verb
- ✓ Number
- ✓ Result
Migrations and technical debt
A migration bullet should give the size of the move and show that nothing broke for customers.
Weak
Worked on migrating legacy code to microservices.
- ✗ Action verb
- ✗ Number
- ✗ Result
Strong
Migrated [N] endpoints from a Rails monolith to Go services behind feature flags, with zero customer-facing incidents and [X%] lower infrastructure cost per request.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Upgraded the database to a newer version.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Planned and ran a PostgreSQL major-version upgrade for a [N] TB database using logical replication, holding downtime to [N] minutes and avoiding [$X] in extended vendor support fees.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Cleaned up technical debt in the frontend codebase.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Removed [N] lines of dead code and replaced a deprecated state library with React Query, shrinking the JavaScript bundle by [X%] and improving mobile page load.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Responsible for moving the app to TypeScript.
- ✗ Action verb
- ✗ Number
- ✗ Result
Strong
Converted [N] modules to TypeScript in strict mode over [N] sprints, resulting in [X%] fewer runtime type errors reported in Sentry.
- ✓ Action verb
- ✓ Number
- ✓ Result
Shipping and delivery
Show who used the feature and the metric it moved, and say which part was yours if it was a team build.
Weak
Developed new features for the mobile app.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Designed and shipped offline sync for the React Native app as the sole engineer on the feature, raising weekly active use among field staff by [X%].
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Contributed to the CI/CD pipeline.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Rebuilt the deploy pipeline with Terraform and GitHub Actions, taking release frequency from weekly to [N] times a day and cutting rollback time to under [N] minutes.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Wrote unit tests for the codebase.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Wrote integration tests covering [N] critical checkout paths, lifting coverage from [X%] to [X%] and catching [N] regressions before release in the first quarter.
- ✓ Action verb
- ✓ Number
- ✓ Result
Weak
Mentored junior developers on the team.
- ✓ Action verb
- ✗ Number
- ✗ Result
Strong
Mentored [N] junior engineers through code review and pairing, shortening their time to first production deploy from [N] weeks to [N] weeks.
- ✓ Action verb
- ✓ Number
- ✓ Result
Action verbs for software engineer resumes
- Built
- Shipped
- Refactored
- Migrated
- Optimized
- Automated
- Instrumented
- Profiled
- Designed
- Debugged
- Deployed
- Scaled
- Mentored
More in the full list of resume action verbs.
Next steps
Rewrite your own bullet →
The Bullet Surgeon gives one of your lines three rewrites, free.
A complete software engineer resume →
A graded example, with notes on why each line works.
What software engineer reviewers check first →
Common mistakes and specific fixes for this role.
Would they interview you? →
Paste a software engineer posting and five readers vote on your resume.