Action Verbs for a Resume: 150 Sorted by What They Prove

Recruiters skim the left edge of your resume. The first word of each bullet is often the only word that gets read on the first pass, which means the verb is carrying the entire claim. "Managed" says you were in charge. "Assisted" says you were nearby. "Reduced" says something got measurably better because of you.

Most action verb lists dump 185 words on you alphabetically and let you scan the wall hoping something fits. That gets the order of operations backwards. You should first decide what each bullet is trying to prove, then pick the verb that makes that exact claim. So this list is sorted by claim. Ten groups, 15 verbs each, and each group answers one question a hiring manager actually asks about you.

A resume bullet is a claim about what you did, and the verb is the claim's headline. Everything after it is evidence. Get the verb wrong and the evidence lands on the wrong claim. A candidate who "supported the migration to a new CRM" and a candidate who "led the migration to a new CRM" might have sat at the same desk, but they are describing two different jobs.

The verb also sets your level of ownership, and hiring managers read it that way. "Directed" or "architected" signals you owned the outcome. "Assisted" signals you supported someone who did. Both are legitimate claims. The failure mode is mismatch, either inflating support work into leadership you cannot defend in the interview, or describing genuine ownership with a verb that undersells it.

One more reason to keep verbs plain rather than ornate. Applicant tracking system (ATS) filters mostly match on nouns, the skills and tools in the job's keyword list. But screening software increasingly reads meaning as well as literal keywords, and a plain verb attached to a concrete object gives it something to match. "Optimized SQL queries, cutting report load time in half" is legible to software and humans alike. "Drove process excellence" is legible to neither.

Pick the group first. Ask what this bullet proves about you, find the matching claim, then choose the verb that fits your actual role in the work. Every verb below is past tense, which is correct for previous jobs and for completed accomplishments in your current one.

These verbs claim creation. Use them when there is a thing, a system, a document, a program, a product, that exists because of you. The trap here is claiming solo creation for team output, so if five people built it, say what part you built.

These verbs claim responsibility for other humans, their work, their growth, or both. "Led" needs an object with a size ("led a team of six"), and "mentored" or "coached" should point at a result the mentee achieved, or it reads as decoration.

These verbs claim that a number went up on your watch. They demand a measurement more than any other group. "Increased revenue" is half a bullet; "increased renewal revenue 22% in one year" is a claim a hiring manager can weigh.

These verbs claim that a number went down, and they are quietly the most persuasive group on the list because saving money and preventing disasters is what most managers get judged on. If you automated a manual task, say what it used to cost in hours.

These verbs claim judgment. They tell a hiring manager you were trusted to choose, and they matter most for senior roles where the job is deciding, then delegating the doing. Reserve them for calls that were genuinely yours to make.

These verbs claim you turned raw information into an answer. They work hardest when paired with the decision your analysis enabled. "Analyzed churn data" is an activity; "analyzed churn data and identified the onboarding step where 60% of cancellations started" is a finding.

These verbs claim you moved other people with words. They need an audience and a stake to land. "Presented to leadership" says little; "presented the pricing proposal that leadership approved for the 2026 rollout" says you were in the room and it mattered.

These verbs claim revenue. In sales and account roles they are the whole resume, and the attached number should almost always be quota attainment, deal size, or retention. A sales bullet without a figure reads like a sales rep without a pipeline.

These verbs claim reliability at scale. They shine in operations, admin, and project coordination roles where the achievement is that nothing broke. Attach volume and accuracy, such as how many events, invoices, or shipments, and how often they went out on time.

These verbs claim service, and they are honest ones for support roles, healthcare, education, and any customer-facing job. "Assisted" is accurate when the work truly was support. The dishonest move is dressing support work up as ownership; the self-defeating move is using "assisted" for work you actually ran.

Some openers make no claim at all. They describe proximity to work rather than a contribution to it, and a hiring manager reading "responsible for" learns only that the task existed somewhere near you. Current resume guidance is blunt on this point, and so is every recruiter I have compared notes with. Cut these and replace each one with a verb that names what you personally did.

The opposite failure is inflation. "Spearheaded," "pioneered," and "transformed" are fine words for work you genuinely originated, and red flags when they decorate routine tasks. A resume where every bullet spearheads something reads like a costume, and the interview is where costumes come off. Match the verb to your real level of responsibility and you never have to remember what you claimed. Vague openers sit high on the list of resume mistakes that quietly cost interviews, mostly because they waste the only words a skimming recruiter reads.

A strong verb starts the claim; a number finishes it. The pattern that works is simple. Verb, then what you did, then the scope, then the outcome with a measurement. "Automated invoice matching for 300 monthly vendor invoices, cutting month-end close by three days" hits all four beats in one line.

Not every job produces clean percentages, and you should never invent one. When you have no metric, quantify the scope instead. How many people, tickets, clients, or pages. How often. How big the budget or the caseload. "Fielded 60+ support calls a day across three product lines" contains no outcome metric, yet it tells a hiring manager exactly how much work you carried. Frequency and volume are numbers too.

If a percentage is genuinely unknowable, describe the before and after states. "Standardized six teams' status reports into one weekly format, replacing four separate spreadsheets" measures nothing and still proves a change happened. Keep each bullet to one claim; if you are stacking three achievements into one line, you likely need another bullet, and there is a sensible cap per job.

Here is the pattern applied. Each "before" is a real type of bullet I see constantly, and each "after" swaps a proximity phrase for a claim verb and finishes the sentence with scope or a result. The numbers are illustrative; yours must be true.

Notice what changed in every row. The verb moved from proximity to contribution, a number or a scope appeared, and the bullet became something an interviewer can ask about, which is the point. Every line on your resume is a future interview question, and a claim verb plus a real number is a question you want to be asked.

Rewriting twenty bullets this way is slow work, and it is where an editor with a copilot earns its keep. In Roleframe, Remi reads the analysis of your resume, proposes a rewrite for the bullet you are on, and shows a word-by-word diff you approve or discard. The words stay yours, which matters, because a verb you did not choose is a claim you may not be able to defend.

One last adjustment separates a good verb from the right one. Job postings repeat their own vocabulary, and when a posting says "coordinate cross-functional launches" four times, "coordinated" beats a fancier synonym on your resume, provided it accurately describes what you did. Screening software and skimming recruiters both reward the employer's own terms.

This is a per-job decision rather than a one-time rewrite. Before you send an application, check your resume against the specific job description and swap verbs where the posting's language and your honest experience overlap. Plain, recognizable verbs travel well across postings; ornate ones rarely match anything.