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

The verb at the start of a resume bullet tells the reader what you did. "Managed" claims responsibility. "Assisted" describes support. "Reduced" introduces a change you should be able to explain. Choose that opening word for accuracy, then add the evidence that makes the claim useful.

This list is sorted by the kind of contribution each verb describes: ten groups of 15. First decide what a bullet needs to show, then pick the verb that fits your actual work. The examples throughout are illustrative; use your own responsibilities and results.

A resume bullet is a claim about what you did, and the verb is its headline. A candidate who "supported the migration to a new CRM" and one who "led the migration" are describing different responsibilities, even if they worked on the same project.

Match the verb to your ownership. Use "directed" when you made decisions and were accountable for the work; use "assisted" when you contributed to someone else's task. Both can describe valuable experience. Avoid inflating support into leadership or obscuring work you actually owned.

Harvard's resume guide recommends active, specific, fact-based language. That is a writing principle, not an ATS trick. Include the relevant tools and skills from the job's keyword list where they accurately describe your experience; no action verb guarantees a screening result.

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 describe responsibility for people, their work or their development. Make the scope clear: "led a team of six" is more specific than "led a team." For mentoring, explain what you helped someone learn or do; a measured outcome is useful when you have one, but it is not required.

These verbs describe growth or improvement. State what changed and, when you can substantiate it, by how much. "Increased renewal revenue 22% in one year" gives more context than "increased revenue." For a change without a numerical measure, describe the before and after clearly.

These verbs describe less cost, delay, complexity or risk. Connect the action to a concrete change. If you automated a manual task and have reliable records, include the hours it previously took. If the outcome was preventing an error, explain the control you introduced rather than inventing savings.

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 work for sales and account responsibilities. Where disclosure is permitted, quota attainment, deal size or retention can show scope. If figures are confidential or unavailable, describe the customer segment, sales stage and contribution instead. Do not claim revenue you only helped generate as a solo result.

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.

Openers such as "responsible for" can obscure your contribution. Replacing them with the action often makes the bullet shorter and clearer. Name your part in the work, without turning routine responsibilities into exaggerated accomplishments.

The opposite failure is inflation. "Spearheaded," "pioneered" and "transformed" can fit work you originated or substantially changed, but they need evidence. If "processed invoices" describes the task accurately, a more dramatic synonym does not improve it. Match the verb to the responsibility you can explain in an interview. For more revision checks, see common resume mistakes.

A useful pattern is action, task, scope and result. For example: "Automated invoice matching for 300 monthly vendor invoices, cutting month-end close by three days." This is an illustrative sentence, not a result to borrow. Use a number only when you can explain its basis.

Not every job produces clean percentages. When there is no outcome metric, describe scope: how many people, tickets, clients or pages; how often the task occurred; or the size of the budget or caseload. "Fielded 60+ support calls a day across three product lines" is an illustrative way to show workload without claiming a result you did not measure.

You can also describe the change directly: "Combined separate team status reports into one weekly format." Keep each bullet focused on a contribution. If several achievements compete in one sentence, consider splitting it into separate bullets.

Here is the pattern applied. Each "before" is a common type of weak bullet, 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.

Each revision names a contribution and supplies context. Treat these as examples of structure, not permission to change the facts: someone who helped design a checklist should say which part they created rather than claiming the whole onboarding process.

When editing in Roleframe, check each suggested phrase against your own experience before keeping it. Review the exported file too, so the version you send contains the wording you intended.

Use the job posting to choose relevant language. If it asks for "coordinate cross-functional launches" and you did that work, "coordinated" is a clear choice. There is no need to replace an accurate word merely to sound more impressive, or to repeat a phrase you cannot support.

Before sending an application, compare your resume with the specific job description. Keep your historical responsibilities accurate while emphasizing the experience that relates to the role.