80 action verbs that make your resume more compelling

Responsible for and helped with are the two phrases that quietly flatten more resumes than anything else. Both are true. Both are safe. Both tell the reader nothing about what happened.

The problem with "responsible for" is structural: it points at your assignment rather than your effect. It's the language of the job posting you answered, not the language of what you did once you got there. A reader deciding whether to interview you needs to know what was different because you were in the seat, and that phrase is specifically designed not to say.

"Helped with" has a second failure on top of that one. It's a hedge. People reach for it when they were part of a team and don't want to overclaim — an honest instinct producing a bad outcome, because it reads as pre-emptive self-minimising. The reader can't tell whether you did the central work or fetched coffee, so they assume the cheaper interpretation. The fix isn't a bigger verb. It's a narrower, more specific scope: name the part you actually did.

Same person, same job, same year. The first version is a duty list; the second is a record. The verbs are carrying some of that — "rebuilt" and "owned" commit to something in a way "responsible for" cannot — but only some.

A verb alone doesn't fix a weak bullet

This is the trap with lists like the one below. Swap the verb in isolation and you get a bullet that sounds more energetic while saying exactly as much as before. "Spearheaded the customer onboarding process" is not an improvement on "responsible for the customer onboarding process." It's the same empty sentence in a louder shirt.

A bullet that works has three parts:

• Verb — what you did.
• Object — what you did it to, named specifically. "The onboarding email sequence," not "processes." The object is where most of the credibility lives, because it's the part that's hard to fake.
• Outcome — what was different afterwards. A number if you have one, a consequence if you don't.

That last point matters more than people expect. Not every bullet has a metric attached, and inventing one is the worst available fix — it's the thing that falls apart fastest in an interview. When there's no number, use a consequence: what got adopted, what stopped happening, what someone else could do afterwards that they couldn't before. Wrote the runbook the on-call rota now works from contains no figures and is still an outcome.

The trap of inflated verbs

"Spearheaded" is the canonical offender. The word means you drove a significant effort forward against resistance. Attached to a two-person task, it reads as somebody straining to make a small thing sound large — and once a reader has caught that once, they start discounting every other line on the page, including the true ones.

That's the real cost. Inflation isn't just embarrassing; it's expensive, because it devalues your genuine achievements by association. A resume where every bullet opens with orchestrated, pioneered, revolutionised or championed reads as insecure. The strongest resumes tend to use plain verbs — built, ran, wrote, fixed, sold — and put the impressive part in the object and the outcome, where it can be checked.

80 verbs, grouped by what they signal

Verbs aren't interchangeable. Each group below makes a different kind of claim, and interviewers read them that way. Decide which claim you're making before you pick the word.

Build and create — 12 verbs

For things that did not exist before you started. The strongest group and the easiest to over-use — if every bullet says "built," the reader can't work out what your actual job was.

• Built · Created · Developed — the plain defaults. Fine for software, processes, teams and documents alike. Use them when the thing actually shipped.
• Designed · Engineered · Prototyped — a claim about how the thing works, not just that it exists. Prototyped is the honest word for something that never reached production, and it's more credible than pretending it did.
• Founded · Established · Launched — first of its kind. A team, a programme, a product line, a partnership. Never use these for a task.
• Authored · Produced · Introduced — documents, content, and things you brought in from outside. Introduced is the accurate verb for a tool or practice you adopted rather than invented.

Lead and own — 12 verbs

These say that someone else's work depended on you. They invite the follow-up "how many people?", so only use them where you can answer it comfortably.

• Led · Managed · Directed — direct accountability. Managed usually implies people or a budget; led can be a project with no reports at all.
• Owned · Oversaw · Chaired — accountable without necessarily managing anyone. Owned is the single most useful word on this list for senior individual contributors.
• Coordinated · Delegated · Supervised — you organised other people's work. Coordinated is accurate and badly undervalued for the very common case of responsibility without authority.
• Mentored · Trained · Recruited — growing other people. Easy to evidence, hard to argue with, and disproportionately rare on early-career resumes.

Improve and optimise — 12 verbs

Something existed and worked worse before you touched it. This group carries a number more naturally than any other, so if you only have one metric on your resume, it usually belongs here.

• Improved · Optimised · Upgraded — the general case, and weak on their own. Always attach the measure or the reader will assume there wasn't one.
• Reduced · Increased · Accelerated — directional verbs that all but demand a figure. Used without one, they read as though you left the number out because it was unimpressive.
• Automated · Streamlined · Simplified — you removed work. Say what the work was and how much of it disappeared; "streamlined" alone is close to meaningless.
• Consolidated · Standardised · Refactored — you unified things that had drifted apart. A strong signal for anyone who has worked somewhere messy, which is most places.

Analyse and investigate — 12 verbs

Claims about finding out what's true. These are the ones people quietly downgrade to "looked at" in conversation, which is a shame, because the analysis is often where the value was.

• Analysed · Researched · Investigated — the defaults. Say what you analysed and what you concluded; an analysis with no conclusion isn't an achievement, it's an activity.
• Evaluated · Audited · Benchmarked — comparison against a standard or an alternative. Useful for vendor selection, code quality, compliance and competitive work.
• Measured · Modelled · Segmented — quantitative work. Name the method and the dataset, because the method is the part that transfers to a new job.
• Tested · Diagnosed · Mapped — finding the cause or the shape of something. Diagnosed is a strong verb for anyone whose job involves fixing what other people broke.

Communicate and influence — 12 verbs

These describe getting other people to do or believe something. Hardest group to evidence, most valuable when you can.

• Presented · Briefed · Pitched — one-to-many. Always name the audience; presenting to your own team and presenting to a board are different jobs.
• Persuaded · Negotiated · Advocated — you changed an outcome that somebody else controlled. Very strong if you name what actually changed as a result.
• Advised · Facilitated · Aligned — you moved a group toward a decision. "Aligned" is corporate but precise when three teams genuinely disagreed and then didn't.
• Wrote · Documented · Translated — making things legible to other people. Translated is for turning technical detail into something a non-specialist can act on. It's a real skill and almost nobody claims it.

Deliver and execute — 12 verbs

Nothing on a resume is worth more than evidence that you finish things. This group is unglamorous and consistently under-used, which is exactly why it stands out.

• Delivered · Shipped · Executed — it went out of the door, on a date. Include the date or the scale, ideally both.
• Implemented · Deployed · Migrated — putting someone else's system or decision into practice. Migrations are genuinely hard and badly under-claimed; say what moved and how much of it.
• Integrated · Scaled · Restored — connecting things and keeping them standing under load. Restored is the incident verb: name what was down and for how long.
• Resolved · Maintained · Processed — the steady-state verbs, weakest of this group on their own. Pair them with volume or reliability: what you handled, how much of it, how consistently.

Grow and win — 8 verbs

Commercial outcomes. If your work touches revenue, retention or partnerships, use this group, because it maps directly onto how the business already measures itself.

• Grew · Expanded — growth over time. Always give a from and a to; "grew the account base" without figures reads as evasive in a commercial role.
• Sold · Closed · Won — you got the yes. Name the deal size and the cycle length, since a six-figure deal over nine months and a small one over a week are different skills.
• Sourced · Secured · Retained — bringing it in from outside and keeping it: leads, funding, partners, suppliers, customers. Retention is often worth more than acquisition and hardly anyone puts it on a resume.

How to actually use the list

Don't open this page and swap eighty verbs into eighty bullets. The list is a diagnostic, not a thesaurus. Read your resume and ask, group by group, what you are claiming.

1. Label each bullet with its group. If a bullet doesn't fit any of the seven, it's probably a duty rather than an achievement. Rewrite it or cut it.
2. Check the balance against the job you want. A senior engineer whose bullets are all "led" and no "built" is describing a manager's resume. A manager whose bullets are all "built" is describing the job they had two promotions ago.
3. Never start two consecutive bullets with the same verb. It's the cheapest fix on this page and it makes a resume read noticeably better within one pass.
4. Keep tense consistent — past tense throughout previous roles, present tense for your current one. Mixed tenses inside a single role is one of the most common small errors, and it's the kind readers notice without knowing why.

The one-minute check

Take the three bullets you'd most want a hiring manager to read and answer three questions about each: what did I do, to what, and what was different afterwards?

If you can answer all three, your verb is probably fine already. If you can only answer the first, no word from any list will save the bullet — the problem isn't vocabulary, it's that you haven't yet decided what the achievement was. That decision is the actual work, and it's the reason a strong bullet takes ten minutes rather than ten seconds.