The Verb You Choose Is a Claim You'll Be Asked About

Every verb at the start of a resume bullet makes a claim about your position relative to other people: “led” says others followed, “owned” says the outcome was yours to answer for, “supported” says someone else was accountable. These are facts about how the work was organised, not stylistic choices. They are also the part of a resume most easily contradicted by anyone who was there, so pick the verb that matches the arrangement and be ready to describe the arrangement.

Why verbs are the weak point

A number on a resume can be wrong quietly. A verb is wrong loudly, because it implies a specific structure that other people remember differently. If you write that you led a project and the person who actually led it is asked about you, the mismatch is not a matter of interpretation.

AI drafting makes this worse in a specific way. Ask a tool to strengthen a bullet and it will reliably escalate the verb, because stronger verbs are what “stronger bullet” means in the pattern it learned. It has no information about who reported to whom. The escalation is not deception on the tool’s part; it is simply the most probable continuation, and it is one of the most consistent directions in which generated drafts drift.

What the common verbs actually commit you to

Led. You set direction and other people worked to it. If asked, you should be able to name who was on the team, what you decided that they did not, and what happened when there was disagreement. Leading without a formal title is real and common — but you still need the answer.

Owned. You were the person accountable if it went wrong. This is a strong claim and easy to check, because organisations tend to know who owned things. If it went wrong and someone else got the difficult meeting, you did not own it.

Managed. Usually read as people management. If you mean you managed a process, say the process explicitly — “managed the release schedule” rather than “managed releases” — because the ambiguous version will be read as headcount and then corrected in the interview, which is the worst sequence.

Drove, spearheaded, championed. Vague enough that a reader cannot tell whether you had authority or enthusiasm. That vagueness feels safe and is not: an interviewer who cannot tell will ask, and you will end up giving the plain answer anyway. Give it first.

Built, wrote, designed, rebuilt. These describe your hands on the work. They are the most defensible verbs available, because the artefact either exists or it does not, and they are underused. A bullet that says you wrote something specific is stronger evidence of capability than a bullet that says you drove an initiative.

Contributed to, supported, worked on. Honest and often the correct choice. They read as modest, which makes people avoid them, but a page of accurate “worked on” bullets with specific objects beats a page of “led” bullets that fold under one question.

Coordinated, ran, facilitated. Useful middle ground when you had responsibility for something happening without authority over the people doing it. Often the truest description of a junior or cross-team role.

A test for each one

For any verb you are considering, ask: if my former manager were describing this work to a stranger, would they use this verb about me? Not a more flattering one, not a less flattering one — this one.

If you are unsure, that uncertainty is the answer. Move down one step. The cost of understating a verb is that a reader slightly underestimates your seniority; the cost of overstating it is a contradiction in a conversation you cannot control, which is what a reference is actually asked to comment on.

Splitting the difference honestly

Real work often does not fit one verb. You might have designed an approach, persuaded two teams to adopt it, and had no authority over either. The temptation is to compress that into “led cross-team adoption,” which overstates the authority. The alternative is to write two clauses and keep both true: “designed the review process and got it adopted by two teams without formal authority.” Longer, and considerably more interesting to a reader who has done the same kind of work.

Where the bullet has to be short, choose the verb for the part you can most clearly defend and let the specifics carry the rest.

Watch for verb inflation over drafts

Resumes get edited many times, often with a tool involved, and each pass tends to strengthen the language slightly. A bullet that started as “helped migrate” becomes “supported the migration” becomes “delivered the migration” over three rounds, and no single step felt like a change of meaning. This is why it is worth keeping the original plain-language version of each bullet somewhere, in the facts file you wrote before drafting, and comparing the final page against it rather than against the previous draft.

Consistency with everything else

The verb also has to agree with the rest of the entry. “Led” sitting under a coordinator title with a nine-month tenure will make a careful reader pause, and that pause is worse than the modest verb would have been. Where the title genuinely understates the role, there is a decision to make about which title to use rather than trying to fix it with a stronger verb.

The same applies across surfaces. If your resume says you led something and your public profile says you were part of the team that did it, that is a discrepancy sitting in plain view, and keeping one story across all of them removes an avoidable problem.