Résumé power verbs, and how to pick one you can defend
Most power verb pages are a wall of three hundred words in a table. You scan it, pick whichever one sounds most senior, and paste it over the front of a bullet you already wrote. The bullet gets a nicer haircut and says exactly what it said before.
The verb is not decoration. It is the claim. "Built" and "contributed to" describe two different amounts of work, and a person who reads résumés all day knows which one you picked and why.
So this list is grouped by what each verb claims, not alphabetically. Pick from the group that matches what you actually did.
The 30-second version
- A verb makes a claim about your role in an outcome. Choose the one that is true, then make it specific.
- Lead every bullet with it. Cut "Responsible for", "Helped with", "Worked on", "Involved in".
- Past tense for everything, including your current job. Consistency reads faster than accuracy about tense.
- Don't repeat a verb inside the same role. Across roles, nobody notices.
- The test: can you follow the verb with a number and a "so that"? If not, the verb is doing work the facts don't support.
Built something that wasn't there before
The strongest group, and the most over-claimed. Use these when the thing did not exist and now it does, and you were the reason.
| Built | Created | Designed | Developed |
| Launched | Introduced | Established | Founded |
| Wrote | Prototyped | Shipped | Architected |
| Drafted | Assembled | Configured | Instrumented |
Good: Built the internal tool the support team now uses to close refund tickets, cutting average handling from 14 minutes to 4.
Weak: Developed innovative solutions for customer-facing challenges.
The second one uses a verb from the same group and claims nothing. No object, no number, no reader can picture it.
Improved something that already existed
Most real work lives here. It is less glamorous than building and often more valuable, and the numbers are usually easier to get.
| Improved | Rewrote | Redesigned | Refactored |
| Streamlined | Consolidated | Automated | Migrated |
| Reduced | Accelerated | Simplified | Standardised |
| Upgraded | Repaired | Restored | Tuned |
These verbs beg for a before and after, so give them one. "Reduced page load from 4.2s to 900ms" is a complete thought. "Improved page performance" is a hope.
Owned or ran it
For work where the achievement was that it kept happening, correctly, without you being chased.
| Managed | Ran | Operated | Maintained |
| Coordinated | Scheduled | Administered | Monitored |
| Tracked | Processed | Handled | Fulfilled |
| Audited | Reconciled | Documented | Enforced |
The trap in this group is that the verbs are true and boring. Rescue them with scale. "Processed 300 invoices a month" beats "Processed invoices" by exactly one number and reads like a different job.
Led people
Reserve these for when people reported to you, or followed you without having to. Everything else belongs in the group below.
| Led | Managed | Mentored | Coached |
| Trained | Supervised | Hired | Onboarded |
| Directed | Delegated | Chaired | Unblocked |
Say the number. "Led four engineers" is a fact. "Led cross-functional teams" is a shape with no size, and the reader assumes the smallest number that would still let you write it.
Worked with people who didn't report to you
The group most people skip, and the one that describes the majority of real influence. There is no shame in it. Pretending it was line management is worse than naming it.
| Partnered | Collaborated | Advised | Consulted |
| Persuaded | Negotiated | Aligned | Facilitated |
| Briefed | Escalated | Represented | Liaised |
Good: Persuaded the platform team to expose two fields we needed, which removed a nightly export job.
That bullet has no authority in it anywhere, and it is more impressive than most bullets that start with "Led".
Figured something out
Analysis, research, investigation. The verb should tell the reader whether you found an answer or produced a document.
| Analysed | Investigated | Diagnosed | Traced |
| Researched | Modelled | Forecast | Benchmarked |
| Measured | Tested | Validated | Surveyed |
| Identified | Isolated | Quantified | Mapped |
"Identified" is the most quietly useful verb on this page and the most wasted. It is only worth anything if you say what happened next. Identifying a problem nobody fixed is a story about the company, not about you.
Moved a number
Use these when you can name the number and the direction. If you can't, use a verb from another group. A growth verb with no figure attached is the fastest way to look like you rounded up.
| Increased | Grew | Raised | Doubled |
| Cut | Lowered | Eliminated | Saved |
| Recovered | Converted | Retained | Won |
| Exceeded | Delivered | Closed | Secured |
Percentages without a base are a known trick and readers treat them as one. "Increased signups 300%" invites the question and "grew signups from 40 to 160 a week" answers it before it is asked. If the real number is small, the percentage will not save you, and the honesty will do more for you than you think.
Explained it to someone
Writing, presenting, teaching, support. Underrated on technical résumés, where people list what they built and never mention that they also got fifty people to use it.
| Wrote | Presented | Explained | Taught |
| Documented | Demonstrated | Published | Translated |
| Answered | Resolved | Supported | Guided |
The phrases to cut, and what to use instead
These are not weak verbs. They are the absence of a verb, wearing one as a coat. Each one is a place where the sentence stopped short of saying what you did.
| Cut this | Because | Try |
|---|---|---|
| Responsible for X | Describes the job description, not you | The verb for what you actually did to X |
| Helped with X | Hides your share of it | Built / Rewrote / Coordinated / Advised |
| Worked on X | True of everyone who was in the room | Name the part that was yours |
| Assisted with X | Same, but smaller | Supported, if support was the job. Otherwise be specific |
| Involved in X | Passive, and it sounds like it | The verb you were avoiding |
| Tasked with X | Says you were assigned it, not that you finished it | Delivered / Completed / Shipped |
| Duties included X | A list of what should have happened | One thing that did happen, with a number |
| Utilised X | A longer word for "used", and readers notice | Used. Or better, the verb for what you used it for |
| Familiar with X | Admits you have not done it | Move it to a skills line, or leave it out |
| Successfully did X | If it failed you would not have listed it | Drop "successfully", keep the result |
"Utilised" deserves its own note. It is the single most common attempt to sound senior by adding syllables, and it is the one most reliably read as padding. Nothing is lost by writing "used", and usually the better fix is to skip the tool entirely: not "utilised Python to build a dashboard", just "built the dashboard the ops team runs on".
Three rules that matter more than the list
Past tense for everything, including the job you have now. It is technically wrong and it reads better. Mixed tense makes a reader stop and work out which role is current, and you do not want to spend anyone's attention on that. Consistency wins.
Never repeat a verb inside one role. Four bullets that all start with "Managed" turn into one bullet by the third line, because the eye stops reading the first word. Vary it inside the role. Across roles, nobody is comparing.
One verb per bullet, at the front. "Designed and built and rolled out" is three claims sharing one set of evidence. Pick the one you can defend and let the rest of the sentence carry the detail.
The only test that matters
Take the verb. Follow it with a number, and then with "so that".
Rewrote the billing reconciliation job, cutting the month-end close from 3 days to 4 hours, so that finance stopped working the first weekend of every month.
If the sentence survives that, the verb is earned. If you find yourself unable to attach a figure or a consequence, that is not a writing problem you can fix with a thesaurus. Either the number exists and you have not gone and found it, or the verb is bigger than the work.
Go and find the number first. Almost everyone can. You remember the ticket queue, the team size, the release cadence, how long the thing took before you touched it. An approximate honest figure beats an exact vague one, and "roughly 200 a month" is a perfectly good thing to write.
Words that promise more than most work delivers
Some verbs carry a size claim on top of the action. They are not banned, they are just expensive. If the story behind the bullet is smaller than the word, the whole résumé pays for it.
| Verb | What it claims | Use it when |
|---|---|---|
| Spearheaded | You started it and drove it against resistance | You did both. Otherwise "Led" or "Started" |
| Pioneered | Nobody in your field had done it | Almost never true. "First at the company" is a different, smaller, still good claim |
| Transformed | The thing is unrecognisable now | You can describe the before and after in one line each |
| Revolutionised | Everyone else changed how they work because of you | Leave it out |
| Orchestrated | Many moving parts, coordinated by you | There were genuinely many parts. Otherwise "Coordinated" |
| Championed | You argued for it and it happened | It happened. Advocating for something that died is not this |
None of these are lies by default. They just get checked. An interviewer who reads "Spearheaded" will ask what the resistance was, and the answer needs to exist.
Common questions
How many different verbs should one résumé use? Enough that no verb repeats inside a role. For most people that is fifteen to twenty-five across the whole document. Chasing a bigger number pushes you toward words you would not say out loud.
Do power verbs help with résumé screening software? Not directly. That software mostly parses your résumé into fields and lets a recruiter search the pile. It is not scoring your verbs. What actually helps is that a specific verb forces you to write a specific sentence, and specific sentences contain the terms a recruiter searches for. The verb is a means, not the target. More on how that screening really works in our tech résumé guide.
Should the verb match the wording in the job posting? Match the vocabulary of the work, not the syntax of the posting. If the posting says "own the deployment pipeline", writing "Owned the deployment pipeline" is honest and readable. Copying a whole phrase from the posting is visible, and it looks like what it is.
What about a résumé with no work experience yet? The same groups apply and the objects get smaller. Coursework, a club, a side project, a part-time job all produce real bullets. "Rebuilt the society's signup form and cut no-shows from 40% to 15%" is a stronger bullet than most people's first job produces, and nobody cares that it was a society.
Is "Managed" a weak verb? No. It is a precise verb that people use imprecisely. Managing four people, a $60k budget, or a release train are three specific claims. Managing "various projects" is the weak part, and the verb was never the problem.
We built Apiva to handle the part after the résumé is done, which is the applying. We read a lot of job postings from the other side of the send button. If you want the numbers behind what employers are actually asking for this month, those are in the monthly market report, drawn from 549,667 live US postings.