All writing
Resume craft

Action Verbs for Software Engineer Resumes (With Real Bullet Examples)

Built, shipped, debugged, scaled. The verbs that work on an engineering resume, the ones that backfire, and worked examples for each stage of the job.

The Zelume team
Berkeley · 4 students
Aug 9, 2026 · 6 min read

Engineering resumes have their own verb problem

Generic resume advice says "use strong action verbs" and hands you a list built for sales roles. On an engineering resume, "spearheaded" reads as noise. The verbs that land are the ones engineers actually use with each other, because the first serious reader of your resume is often an engineering manager who can smell borrowed vocabulary instantly.

The good news: the honest verbs are also the strong ones. Here they are, grouped by the kind of work.

Building

Built, Developed, Implemented, Designed, Architected, Prototyped, Integrated

"Built" is the workhorse, and it's fine to use it more than once. Reserve "architected" for work where you genuinely made the structural decisions. Claiming architecture for a CRUD feature is the fastest way to lose a technical reader.

  • "Built a REST API in FastAPI serving three internal tools, with 90% test coverage"
  • "Integrated Stripe billing into a Django app, handling webhooks for 4 subscription states"

Shipping and operating

Shipped, Deployed, Released, Automated, Migrated, Containerized, Maintained

These verbs separate people who finish things from people who start them. "Shipped" carries weight precisely because half of all side projects never do.

  • "Shipped a React Native app to both stores; 800 downloads in the first quarter"
  • "Automated the release pipeline with GitHub Actions, cutting deploy time from 40 minutes to 6"

Fixing and improving

Debugged, Optimized, Refactored, Reduced, Profiled, Resolved, Stabilized

Improvement verbs demand numbers more than any other group. "Optimized queries" is a claim. "Cut p95 latency from 1.2s to 300ms" is evidence. If you didn't measure, you can often still count: bugs closed, incidents resolved, build minutes saved.

  • "Profiled and fixed an N+1 query pattern, reducing page load from 4s to 600ms"
  • "Refactored a 3,000-line legacy module into tested services, enabling the next two features to ship in days instead of weeks"

Collaborating (without sounding like a manager)

Reviewed, Documented, Mentored, Paired, Onboarded, Specced

Junior and mid-level resumes often skip these, which is a mistake. "Reviewed ~10 PRs a week" and "Wrote the onboarding doc new hires still use" are real signals of trust on a team.

Verbs that backfire on engineering resumes

VerbWhy it hurts
SpearheadedSales language; engineers don't say this
UtilizedIt means "used," and "used" isn't a resume verb either. Name what you built with the tool
LeveragedSame disease as utilized
CodedReads junior; "built" or "wrote" carry the same meaning with more weight
HelpedThe classic. See the weak words cut list

The pattern every bullet should follow

Verb, then the thing, then the stack in passing, then the number: "Built [thing] with [tools], which [measured outcome]." Not every bullet needs all four parts, but every bullet needs the first two, and your best three bullets should have all four. The main action verbs guide covers the general version of this formula.

One engineering-specific note: your projects are evidence in a way other fields can't match, because the code is public. If your GitHub has real work in it, our free GitHub resume generator reads your repositories and drafts evidence-backed bullets from what you actually shipped, which beats writing them from memory.

The Zelume team
Berkeley · 4 students

Notes on ATS parsing, internship pipelines, and the things we built Zelume to solve.

Keep reading