Resume action verbs that actually land

Why verbs decide the read

A recruiter does not read your résumé. Not the way you wrote it, anyway. In the first pass, a recruiter skims it — eyes dropping down the left edge of the page, catching the first word of each bullet, building a fast impression of what you do and how big you do it. That left edge is almost entirely verbs. Which means the verbs are the load-bearing wall of the whole document. Get them right and the skim tells a coherent, impressive story before the recruiter has read a single full sentence. Get them wrong and the skim returns a flat, interchangeable blur that no amount of buried detail can rescue.

I have reviewed more than ten thousand résumés, and the single most common reason a strong candidate reads as average is not a missing skill or a formatting error. It is verb choice. Talented people describe extraordinary work in language so passive and generic that the work disappears. "Responsible for the migration of the company's data infrastructure to the cloud" is, in plain terms, a person who moved an entire company to the cloud, a genuinely hard, high-stakes job. But the sentence opens with a phrase that means nothing, hides the action in a noun ("the migration"), and leaves the reader to do the work of figuring out what actually happened. "Migrated the company's data infrastructure to the cloud, cutting hosting costs 34% and eliminating four hours of weekly downtime" is the same human, the same year of effort, finally legible.

This is the gap this guide closes. Not by handing you a list of two hundred "power words" to sprinkle on at random — that approach produces résumés that sound like a thesaurus had a panic attack — but by teaching you which verb to reach for, why it works, what has to sit behind it, and which verbs to delete on sight. A verb that lands is precise, active, honest, and tethered to a result. Everything below is in service of that one standard.

It helps to understand why the skim falls so hard on the verbs, because once you see the mechanism you can't unsee it. Reading is expensive. A recruiter facing two hundred applications for one role cannot read two hundred résumés word for word, so they don't; they triage. The triage pass is a vertical scan down the left margin, and the brain, hunting for a reason to either keep reading or move on, latches onto the first content word of each line. On an experience bullet, that first word is almost always the verb. So the verb isn't just the first thing read; for many bullets, in that first pass, it's the only thing read. Everything you packed into the back half of the line — the tool, the team size, the percentage — only gets seen if the verb earned the eye's pause. A weak verb means the rest of the bullet, however good, is never reached.

There's a second, slower read that follows for the résumés that survive triage, and the verbs matter there too, in a different way. On the close read, the recruiter is assembling a mental model of what kind of professional this is: a builder, a fixer, an operator, a closer. That model is built largely from the pattern of verbs. A résumé whose verbs cluster in the building group reads as a maker; one whose verbs cluster in the leadership and impact groups reads as an operator. The verbs, in aggregate, are a portrait. Choose them carelessly and the portrait is blurry; choose them deliberately and the recruiter finishes the page knowing exactly what you are. That is the quiet power most people leave on the table.

The anatomy of a verb that lands

Every experience bullet worth keeping has the same three-part skeleton: verb → work → result. The verb names what you did. The middle names the specific thing you did it to. The result proves it mattered. Drop any one of the three and the bullet weakens; drop the result and even a perfect verb collapses into a job description.

Look at the figure above. "Redesigned the checkout flow for mobile, lifting conversion 23%." The verb (redesigned) is active and specific, not "worked on," not "was involved in." The middle (the checkout flow for mobile) is concrete, not "various web properties." The result (lifting conversion 23%) is measurable and attributable. Three parts, one clean line, and a recruiter understands your scope in under two seconds.

Now strip the result: "Redesigned the checkout flow for mobile." Still fine, but it's now a task, not an accomplishment. It tells the reader what you were assigned, not what you changed. The result is what converts a duty into evidence. This is why the verb and the metric are a package deal, and why a guide about verbs keeps circling back to numbers. A strong verb with no result is a promise the bullet never keeps.

It's worth slowing down on the middle of the bullet too, because it's the part people neglect most. "Redesigned the checkout flow for mobile" works because the object is concrete and specific. Compare "Redesigned various user-facing experiences" — same verb, but the object dissolved into vagueness, and with it any sense of what you actually touched. The middle of the bullet is where you earn the reader's trust that you're describing one real thing and not gesturing at a category. Name the system, the page, the program, the account, the dataset. Specificity in the object is what makes the verb believable and the result attributable; without it, even a precise verb floats free of anything the reader can picture.

There's also an order effect worth knowing. Readers remember the first and last thing in a line far more than the middle, the primacy and recency of a single sentence. That's another argument for the verb→work→result shape: it puts your strongest two assets, the action and the outcome, in the two positions the reader actually retains, and tucks the necessary-but-less-memorable detail in the middle where it does its job quietly. Flip the structure, open with the result, say, or bury the verb mid-sentence, and you spend your most valuable real estate on the wrong content. The shape isn't arbitrary; it's tuned to how the line is read and remembered.

The four questions a strong verb answers

When I coach members through their bullets, I run each verb past four questions. If the verb can't answer all four, it's the wrong verb.

• Is it active? Does it describe an action you took, in the active voice? "Led," "built," "negotiated" pass. "Was responsible for," "involved in," "tasked with" fail — they describe a state, not an act.
• Is it specific? Does it name a distinct kind of work? "Optimized" is sharper than "improved"; "negotiated" is sharper than "handled." The more precise the verb, the more the reader learns from one word.
• Is it true? Does it accurately describe your role? "Led" implies you directed others; if you contributed, "contributed to" or "supported" is the honest verb. Inflation is the fastest way to lose credibility in a reference check.
• Does it set up a result? Can a measurable outcome follow naturally? "Reduced," "increased," "accelerated," "cut" practically demand a number. Verbs that invite results are the ones that make the strongest bullets.

The four tiers of action verbs

Not all verbs carry the same weight, and the weight isn't about how impressive the word sounds; it's about the altitude of action it describes. I sort verbs into four tiers. The tier you reach for should match the altitude you actually operated at, which is why the same verb can be perfect on one résumé and dishonest on another.

Tier 1 — Support verbs

These describe contribution to work someone else owned: assisted, supported, coordinated, contributed, participated, aided. They are honest and necessary (a new grad or junior contributor uses them legitimately all the time) but they're the weakest tier because they signal you were near the work, not driving it. The trap is using them when a stronger, truer verb applies. If you actually built the thing, "contributed to building" undersells you. Use support verbs only when support is the literal truth, and pair them hard with a result so the bullet still shows impact: "Supported the year-end audit by reconciling 1,200 vendor accounts, surfacing $90K in duplicate payments."

Tier 2 — Execution verbs

The workhorses: built, created, designed, developed, analyzed, launched, implemented, produced, wrote, tested, automated. These describe hands-on work you personally did, and for individual contributors at every level they are the backbone of the résumé. They're strong precisely because they're concrete — each one names a distinct craft. A great IC résumé is mostly execution verbs, each one closing on a result. Don't apologize for living in this tier; "built" and "shipped" are among the most credible words on any résumé.

Tier 3 — Ownership verbs

These signal you owned an outcome or directed others: led, managed, directed, owned, ran, oversaw, headed, coordinated, championed. They're the language of responsibility, and they're powerful when true and corrosive when not. "Managed" implies you managed people, a budget, or a defined function — not that you happened to be in the room. If you led a project's execution without authority over people, "drove" or "coordinated" is often the more honest and still-strong choice. Reserve "managed" for genuine management so the word keeps its weight across the whole document.

Tier 4 — Impact verbs

The peak: scaled, transformed, restructured, drove, accelerated, grew, doubled, turned around, reinvented. These describe change at the level of an organization, a market, or a number that matters to the business. They're the verbs of senior and executive résumés, and they only land when the result behind them is genuinely large. "Scaled the support org from 4 to 40 while holding CSAT above 95%" earns "scaled." "Scaled my personal productivity" does not — it cheapens a strong verb. Impact verbs are a promise; the metric has to keep it.

The defining feature of Tier-4 verbs is that they imply you changed the trajectory of something, not just its current state. "Improved" describes a better version of the same thing; "transformed" describes a different thing entirely. That's a big claim, and the reason these verbs read as powerful is precisely that they're rarely true: most work, even excellent work, improves rather than transforms. So when you reach for an impact verb, you're implicitly claiming membership in a small group, and a sophisticated reader will check the claim against your evidence immediately. If the evidence is there, a number that genuinely reflects organizational-scale change, the verb is the most powerful word on your page. If it isn't, the verb is the most damaging, because overreaching at the top tier signals a lack of self-awareness about your own altitude, which is itself disqualifying for senior roles. Use these verbs like a scalpel, not a paintbrush: precisely, rarely, and only where the cut is real.

The verb library, grouped by skill

Here is the heart of the guide: a working library organized by the kind of work you're describing, not alphabetically. When you're rewriting a bullet, you know what category of thing you did — you led something, you built something, you fixed something, you sold something — so the library is built to be entered through that door. Each group lists the verbs, then shows what a finished bullet looks like with one of them in place.

Leadership & people

In a bullet: "Mentored 6 junior analysts, three of whom were promoted within 18 months." The verb signals people-development; the result proves it worked. Note that "built" appears in three different groups in this library — "built a team," "built a product," "built a process" — because the strongest verbs are flexible, and context tells the reader which sense you mean.

The leadership group is where calibration matters most, because the verbs sit so close together but mean different things. "Led" implies you set direction and others followed; "managed" implies formal authority over people, budget, or a function; "directed" sits above both, implying strategic command; "coordinated" implies you drove an outcome across people you didn't have authority over. Reach for the one that matches your actual relationship to the work. The classic error is using "managed" for everything, "managed the launch," "managed the relationship," "managed the report," until the word means nothing. If you didn't have direct reports or own a budget on a given line, a more precise verb almost always exists, and it usually reads stronger, not weaker, because it's exact. "Mentored," "coached," and "developed" are quietly among the most valued verbs on a senior résumé, because growing other people is the rarest and most leverage-heavy thing a leader does, and the easiest to prove with a promotion or retention number.

Creating & building

In a bullet: "Built and shipped a self-serve onboarding flow that cut support tickets 41% in the first quarter." Building verbs are the most credible words an IC can use because they're impossible to fake in an interview — you either built it or you didn't, and the follow-up questions will tell.

Within this group there's a subtle hierarchy of specificity. "Developed" and "created" are the safe generalists — they fit almost anything and never read as wrong, but they also never read as memorable. "Architected" and "engineered" carry a connotation of technical depth and system-level thinking; use them when you genuinely designed the structure of something, not when you wrote one piece of it. "Founded" and "established" imply you started something from nothing, which is a strong claim worth making when true and a hollow one when stretched. "Prototyped" is underused and valuable — it signals you take ideas to a testable form fast, which hiring managers prize. And "shipped" deserves special mention: in product and engineering cultures it's almost a values statement, signalling that you finish and release rather than polish forever. One honest "shipped" can do more for a technical résumé than three "developed"s.

Improving & optimizing

In a bullet: "Automated the weekly reconciliation, cutting a 6-hour manual task to 20 minutes." This group practically begs for a before/after number — the verb implies a change, so the reader's first question is "by how much?" Always answer it in the same line.

Reducing & saving

In a bullet: "Reduced cloud spend 34% by rightsizing infrastructure, saving roughly $220K annually." Cost and time reduction is one of the most universally legible accomplishments on any résumé because every hiring manager understands money and hours. If you've saved either, lead with it.

A nuance worth internalizing: reduction verbs are only impressive when the thing reduced was a problem. "Reduced the size of the report" is ambiguous — was the report bloated, or did you cut useful content? "Reduced report generation time from six hours to ten minutes" is unambiguously good because time is always worth saving. When you use a reduction verb, make sure the object is something a reader instinctively wants less of — cost, errors, churn, latency, downtime, manual steps, risk. And mind the framing direction: "cut errors 90%" and "raised accuracy to 99.9%" can describe the identical achievement, but one leads with a reduction verb and one with a growth verb. Choose the framing that produces the cleaner, more intuitive number for that particular fact, and don't be afraid to flip the math to get there.

Growing & increasing

In a bullet: "Grew the qualified pipeline 2.4x in two quarters by rebuilding the inbound nurture sequence." Growth verbs are Tier-4 territory — make sure the number is real and attributable to you, because these are the bullets an interviewer probes hardest.

Selling & influencing

In a bullet: "Negotiated a renewal with the company's largest account, securing a 3-year, $1.2M contract." "Negotiated," "secured," and "closed" are powerful because they imply a result was at stake and you delivered it — the verb itself carries tension the reader wants resolved.

Analyzing & solving

In a bullet: "Diagnosed the root cause of a recurring checkout failure, resolving a defect that had cost an estimated $40K in monthly abandoned carts." Analytical verbs shine when you pair the act of finding something with the value of what you found.

Managing & coordinating

In a bullet: "Coordinated a 9-person cross-functional team to deliver a platform migration two weeks ahead of schedule." Coordination verbs are perfect for project work where you drove the outcome without formal authority over the people — the honest middle ground between "led" and "supported."

Communicating & teaching

In a bullet: "Authored the API documentation that reduced partner integration time from 3 weeks to 4 days." Communication verbs are undervalued — many people bury the writing, training, and presenting that made them indispensable. Name it, and tie it to who benefited.

Pairing verbs with metrics

A verb is the setup; the metric is the punchline. The whole reason precise verbs matter is that they create a slot a number can drop into — and the bullets that get people interviewed are the ones that fill that slot. You don't need a metric on literally every line, but you need them often enough that the recruiter trusts the rest. A résumé that's all verbs and no numbers reads as motion without proof.

When you don't have a number

Sometimes the result is real but not quantified — you improved something you never measured. Don't fabricate a number; that's a fast way to get caught. Instead, reach for a concrete, verifiable outcome. Three honest substitutes for a hard metric:

• Scope. The size of what you touched: "across 14 markets," "for a 200-person org," "on the company's highest-traffic page." Scope is a kind of number even when there's no percentage.
• Before/after state. A described change without a figure: "replacing a manual spreadsheet process with an automated pipeline," "taking the team from no documentation to a fully maintained wiki."
• Recognition or adoption. Who used it or noticed it: "adopted as the team standard," "cited in the quarterly review," "rolled out to all four regional offices."

The discipline of estimating responsibly is worth learning well — our deeper treatment of turning duties into quantified results lives in the ATS résumé guide, which walks through how recruiters search the parsed text your verbs sit inside.

There's a deeper principle hiding under the verb-plus-metric pairing, and it's worth stating plainly: the metric is not decoration, it's scope. When a recruiter reads "Led a team," the very next question forming in their mind is "how big?" A team of three and a team of thirty are different jobs, and the verb alone can't tell them apart. The number resolves the ambiguity the verb opens. This is why the best bullets feel complete and the worst feel like they're missing something: a verb without a scope leaves a question dangling, and the reader has to either ask it in an interview or, more often, assume the smaller answer. Attach the scope and you control the inference. "Managed a budget" invites the reader to imagine a modest one; "Managed a $4.2M annual budget" tells them exactly how much trust you were given. The number isn't bragging; it's preventing the reader from underestimating you by default.

A practical way to find metrics you didn't think you had: for each bullet, ask the four scope questions. How many? (people, accounts, markets, transactions). How much? (dollars, hours, percentage points). How fast? (time to ship, time saved, cycle length). Compared to what? (the prior state, the team average, the target). Most people have answers to at least one of these for most of their bullets — they've just never written them down because the work felt routine to them. It isn't routine to the reader, who has no idea what you did until you tell them the size of it. Spend twenty minutes pulling old dashboards, performance reviews, and project retros, and you'll usually surface a dozen numbers you'd forgotten you owned.

The verbs and phrases to retire today

Some openers are pure dead weight. They occupy the most valuable real estate on the page — the first word of a bullet — and give the reader nothing. Search your draft for these and replace every one.

The pattern across all of these is the same: they describe your relationship to the work ("responsible for," "involved in") instead of the work itself. The fix is always to name the action. When you delete "responsible for" and the sentence still makes sense, you'll usually find the real verb was sitting right there, buried as a noun: "responsible for the management of the team" was always just "managed the team."

Power words vs. buzzwords

People conflate these constantly, so let's draw the line sharply. A power word is a precise action verb backed by a real result — it shows. A buzzword is an unprovable adjective or cliché that claims. "Reduced churn 18%" is a power phrase. "Results-driven team player" is a buzzword sandwich. The first earns trust; the second spends it.

Buzzwords fail for a specific reason: they assert a quality the reader has no way to verify, and worse, they ask the reader to take your word for something you should be proving. Calling yourself "dynamic" or "passionate" or "detail-oriented" tells the recruiter nothing, because everyone says it — and the candidates with genuine attention to detail demonstrate it through a clean, error-free document, not by claiming it in a line. The cure for a buzzword is always the same: find the evidence the buzzword was gesturing at, and put the evidence on the page instead.

There's a particular cruelty to the "detail-oriented" claim that illustrates the whole problem. A résumé that says "detail-oriented" while containing a typo, an inconsistent date format, or a misaligned bullet has just disproven its own claim in the act of making it. The recruiter doesn't consciously think "this person isn't detail-oriented" — they just feel a small friction and move on, the claim quietly working against the candidate. The same trap waits inside every self-describing adjective: "strong communicator" in a poorly written bullet, "leader" with no led-anything to show for it, "innovative" describing routine work. The adjective sets an expectation the rest of the page then fails to meet. Verbs and evidence don't have this problem, because they don't claim a quality — they show an action and let the reader draw the conclusion. Always let the reader draw the conclusion; a quality the reader concludes for themselves is believed, while a quality you assert is discounted.

Be especially wary of the buzzwords that have crept into job postings and now boomerang back onto résumés — "synergy," "leverage" as a verb, "thought leadership," "move the needle," "best-in-class," "ninja," "rockstar," "guru." These read as filler at best and as trying-too-hard at worst, and none of them survive the substitution test: replace each with the concrete thing it's standing in for and the sentence improves every time. "Leveraged data to drive decisions" is just "used data to decide" wearing a costume; "Modeled regional churn and recommended a retention play" is what actually happened, and it's stronger because it's specific. Strip the costume off every claim and dress it in evidence instead.

Before & after rewrites

Principles are easy to nod along to and hard to apply to your own bullets. Here are seven real-shaped rewrites across different functions, each one taking a flat line and rebuilding it with a precise verb and a result. Read them as patterns, not scripts.

Notice what changes and what doesn't. The work is the same in every pair — nothing was invented. What changed is that the verb moved to the front, the relationship-phrase ("responsible for," "involved in") disappeared, and a result arrived to close the loop. That's the entire move, repeated. If you want a strategist to run this rewrite across your whole document with you, that's exactly the kind of line-by-line work the Marqee process is built around.

Tense, voice & parallelism

Three small grammar rules quietly separate a polished résumé from an amateur one. None are hard; all are frequently broken.

Tense: past for the past, present for now

Use past tense for every role you've left and for any completed project — even one finished last week in your current job. Use present tense only for ongoing responsibilities in the role you hold right now. The most common error is mixing them inside a single role: "Manage a team of 5. Built the reporting pipeline. Lead weekly planning." Pick a frame per role and hold it. For current roles, many strong résumés use past tense throughout anyway, which sidesteps the mixing problem entirely — completed accomplishments simply read better in past tense.

Voice: active, always

The passive voice is where strong work goes to die. "The migration was led by me" is weaker than "Led the migration" in every way: it's longer, it buries the verb, and it literally puts you at the end of your own sentence. Starting each bullet with the verb forces active voice automatically, which is one more reason the verb-first rule matters. If a bullet ever contains "was," "were," or "by me," rewrite it. The passive voice has exactly one legitimate use on a résumé — when the actor is genuinely irrelevant and the result is the point ("Selected from 400 applicants for...") — and even then, use it sparingly. The default is active, verb-first, every time.

Worth noting too: dropping the subject pronoun is standard and correct on a résumé. You write "Led the migration," not "I led the migration." The implied subject is always you, so the "I" is redundant, and removing it lets the verb sit at the very front of the line where the skim catches it. This is one of the few places where formal grammar bends to the format — résumé bullets are deliberately written as headline-style fragments, not full sentences, precisely so the verb leads. Don't let a word processor's grammar checker talk you into adding the "I" back.

Parallelism: keep the structure consistent

Within a role, every bullet should start the same grammatical way — all past-tense verbs, or all present-tense verbs, never a mix of verbs and noun phrases. Parallel bullets read fast and feel deliberate; non-parallel ones feel sloppy even when the reader can't articulate why. This is also a parsing courtesy: consistent structure helps an applicant tracking system slot your experience into the right fields, a point the résumé formatting guide covers in depth.

Verbs by career level

The right verbs shift as you climb, because the altitude of your work shifts. Using verbs from the wrong level is one of the subtlest tells on a résumé — a new grad whose every bullet starts "Spearheaded" reads as inflated; a director whose bullets all start "Assisted" reads as someone who hasn't grown into the title.

New grads & early career

Lean on Tier-2 execution verbs anchored to coursework, internships, projects, and part-time roles: built, analyzed, coordinated, presented, researched, designed, organized, wrote. Your edge is concrete proof of capability, not scope of authority, so verbs that show you did things beat verbs that claim you ran things. "Built a sentiment-analysis model for a 10,000-tweet dataset as a capstone project" is a stronger new-grad bullet than any leadership verb you'd have to stretch for. We unpack this further in the dedicated guidance for new grads.

Mid-career professionals

Blend execution with ownership: keep built, designed, launched for your craft, and add led, managed, drove, owned as you start to direct projects and people. The mid-career résumé's job is to show the transition from "does great work" to "is trusted with outcomes," and the verb mix is how you signal it. Show a few clearly owned results among your hands-on wins.

Senior leaders & executives

Move toward Tier-3 and Tier-4: directed, scaled, restructured, transformed, drove, grew. At this altitude, the reader assumes you can do the work — what they're evaluating is your effect on people, P&L, and direction. Execution verbs can actually undersell an executive ("built the deck" is beneath a VP's résumé); the bullets should operate at the level of strategy, organization, and number. The executive guidance goes deeper on framing leadership scope.

Verbs by function

Beyond level, certain verbs are native to certain functions. Reaching for the verbs a hiring manager in your field uses every day signals fluency — you sound like an insider, not a tourist. Here's a fast reference for common functions.

A word of caution: native verbs help only when the work behind them is real. Borrowing the vocabulary of a function you've never worked in to seem qualified backfires the moment an interviewer probes — fluency you don't have collapses fast under follow-up questions. Use the insider verb when you've done the insider work. If you're pivoting into a new function, the honest move is to map your real accomplishments onto the new field's language carefully, a transition the career-change guide walks through step by step.

One more reason function-native verbs matter: they help the reader place you instantly. A hiring manager skimming for a product role and seeing "prioritized," "scoped," "validated," and "shipped" recognizes a fellow product person before reading a single full sentence; the verbs alone establish that you speak the language and have done the work. The same résumé full of generic verbs ("handled," "worked on," "managed") forces the reader to do extra interpretation to figure out whether you're actually a product person or just adjacent to one. In a fast skim, that extra interpretation often doesn't happen, and you're passed over not because you're unqualified but because your verbs didn't signal your fluency clearly enough. The native verb is a fast, honest shortcut to recognition — when, and only when, the work behind it is real.

For career changers specifically, the verb is also where you build a bridge. You can't claim the destination field's outcomes if you haven't produced them yet, but you can describe your transferable accomplishments using verbs that resonate in the new field. A teacher moving into corporate training legitimately "designed curricula," "facilitated sessions," and "assessed outcomes" — verbs that read as native to learning-and-development without overclaiming. The trick is to find the genuine overlap in the work and let shared verbs carry the connection, rather than borrowing destination-field verbs for work you never did. Done honestly, the verb is the most natural bridge a pivot has.

Verbs and the applicant tracking system

Here's a truth that saves people a lot of wasted effort: action verbs do not get you through an ATS. Applicant tracking systems match the nouns — the skills, tools, certifications, and titles named in the job posting. "Kubernetes," "financial modeling," "registered nurse," "Salesforce." Your verbs are nearly invisible to the parser. No applicant tracking system has ever shortlisted a candidate because they wrote "spearheaded" instead of "led."

So why does a guide about verbs talk about the ATS at all? Because the two audiences are sequential, and your bullet has to serve both. The parser indexes your résumé so a recruiter can find you by searching for skill nouns. Then a human reads the bullet your noun is sitting inside — and that's where the verb does its work. The verb doesn't win the search; it wins the read that follows the search. The ideal bullet therefore packs the exact skill term from the posting (for the machine) and opens with a precise verb (for the person):

Built a real-time data pipeline in Python and Airflow,
cutting report latency from 6 hours to under 10 minutes.

  ↳ "Python" / "Airflow"  →  the nouns the ATS matches
  ↳ "Built"              →  the verb the recruiter reads
  ↳ "6 hours → 10 min"   →  the result that earns the call

That's the synthesis: don't choose between machine and human, because a well-built bullet doesn't make you choose. Lead with the verb, embed the exact skill noun, close with the number. For the full mechanics of how parsers read your file and how recruiters search it, the ATS résumé guide is the companion piece to this one.

This is also why the "ATS resume" panic that circulates online is mostly misdirected energy. People agonize over whether a verb is "ATS-friendly," when no verb is friendlier to a parser than any other — the parser doesn't grade your verbs, it indexes your nouns and your structure. The real ATS risk lives in formatting (tables, text boxes, headers that scramble the parse) and in missing the skill keywords a recruiter searches for, both of which the formatting guide and the ATS guide address directly. Your verbs are a human-facing concern, full stop. Free yourself from the worry that a "wrong" verb will get you auto-rejected by a machine — it won't — and spend that energy choosing the verb that wins the human read, because that's the read that actually decides.

The cleanest mental model is to picture your bullet doing two jobs in sequence. First job, invisible: the parser lifts the skill noun out and files you under it, so that when a recruiter searches for that skill, you appear in the results. Second job, visible: the recruiter, now looking at your line, reads the verb and the result and decides whether to click into your full profile. The noun gets you found; the verb gets you read; the number gets you called. Build every important bullet so it serves all three, and you've stopped fighting the machine and the human against each other and started using each to set up the next.

Strong without exaggerating

The whole project of this guide could be misread as "make everything sound bigger." It isn't. The fastest way to lose a job in a reference check is to have written verbs your former managers wouldn't recognize. The goal is to make true work legible, not to make modest work sound heroic. There's a bright line between the two, and staying on the right side of it is what makes a résumé hold up under scrutiny.

The technique for getting a stronger bullet without lying is counterintuitive but reliable: don't inflate the verb — sharpen the evidence. When a bullet feels weak, the instinct is to swap "helped" for "led." Resist it if "led" isn't true. Instead, keep the honest verb and add specificity until the bullet earns its weight on facts alone.

See the move? The verb stayed honest ("automated" is exactly what you did), but the bullet got dramatically stronger because the evidence sharpened: the tool (SQL), the deliverable (the quarterly sales report), and the result (4 hours saved). You never claimed to have led anything you didn't lead. This is the single most important habit in résumé writing, and it's the one that survives the interview: every verb you can defend, every number you can explain.

The copy-paste verb bank

Here's the full library in one scannable block, organized by intent. Keep this open while you rewrite — when a bullet feels flat, find the verb that names what you actually did, drop it in, and add the result. Remember: pick for accuracy, not for drama, and avoid repeating any single verb more than twice across the whole document.

One last note on the bank: it's a starting point, not a checklist to exhaust. The best résumés use a focused set of fifteen to twenty-five verbs that genuinely match the work, each one closing on a result — not all hundred-plus words above. Range matters, but precision matters more.

Worked example: a bullet, rebuilt

Let's take a single weak bullet and rebuild it in slow motion, so you can see every decision. This is the exact sequence I walk members through when we sit down with their existing résumé. The starting line is one I see in some form on a third of the résumés that cross my desk:

"Responsible for handling the company's email marketing,
 working with the team to improve engagement."

Step one — find the buried verb. "Responsible for" is a dead opener. What did this person actually do? They ran the email program. So the real verb was hiding in plain sight. We promote it to the front and delete the dead phrase: "Ran the company's email marketing."

Step two — kill the second dead phrase. "Working with the team to improve engagement" contains a second weak construction ("working with") and a vague outcome ("improve engagement"). We need to know what was done and what changed. Pressed for detail, the member tells me they rebuilt the segmentation strategy and the open rate climbed. Now we have a real action and a real result.

Step three — name the work specifically. "Improved email marketing" is still a category, not a thing. The specific work was rebuilding how the list was segmented. So: "Ran the company's email marketing and rebuilt the segmentation strategy."

Step four — attach the number. The member checks their old dashboards: open rate went from 14% to 26%, and the program drove a measurable revenue lift. We add the defensible figure: "...lifting average open rate from 14% to 26% and adding an estimated $48K in quarterly attributed revenue."

Step five — check the tier and the honesty. "Ran" is honest — they owned the program without managing people, so "managed a team" would be a stretch and "ran" is exactly right. The numbers are pulled from real dashboards, so they survive a reference check. The verb tier matches a mid-career marketer's altitude. Done.

One bullet, five small decisions, and a line that went from invisible to interview-worthy without inventing a single fact. The work was always there — the rewrite just made it legible. Run that same five-step pass on every bullet you own and the cumulative effect on the whole document is dramatic. This is precisely the line-by-line work a Marqee strategist does with you, on every bullet, before your résumé ever goes out.

Beyond the résumé: stay consistent

Your résumé is not the only place a hiring manager reads your verbs. Increasingly, the first thing they see is your LinkedIn profile — pulled up the moment a referral mentions your name or a recruiter sources you for a role. When the strong, specific verbs on your résumé collide with a LinkedIn profile full of "responsible for" and "team player," the inconsistency reads as carelessness, and the weaker surface drags down the stronger one. The verb discipline you've just learned has to travel across every surface where your story is told.

LinkedIn

LinkedIn rewards the same verb-first, result-anchored bullets your résumé uses, with one twist: the platform's own search indexes your profile text, so the skill nouns matter even more there. Mirror your strongest résumé bullets into your experience section, keep the verbs precise, and let the headline and About section carry the narrative. A profile that opens every role with "Responsible for" is leaving both recruiter impressions and search visibility on the table.

Cover letters and the referral pitch

A cover letter is not the place to repeat your bullets verbatim, but it is the place to extend the same voice — active, specific, result-anchored — into prose. The strongest cover letters take one or two of your best accomplishments and tell the short story behind them, using the same precise verbs. The same is true of the message that asks someone for a referral: when you describe your own work to a potential referrer, the verbs that make your résumé legible make your pitch credible. This is the side-door work — referrals and warm introductions — where how you describe yourself in a single paragraph can decide whether someone is willing to put their name behind you. Our guide to asking for a referral goes deep on that exact message, and the cold-email guide applies the same verb discipline to reaching a hiring manager directly.

Interview stories

The verbs you chose carry forward into the interview, because every strong bullet is the seed of a story you'll be asked to tell. "Led the rollout of a new CRM to 60 reps" is not just a résumé line — it's the prompt for a behavioral answer about how you actually drove that rollout. If your verb claimed more than you did, the interview is where it unravels; if your verb was honest and specific, the interview is where it pays off, because you can tell the real story behind it with confidence. The connection between résumé verbs and interview answers is direct, which is why the behavioral-interview guide is the natural next read after this one.

The 6-step verb audit

Before you submit anything, run this pass. It takes about ten minutes and catches the issues that quietly flatten an otherwise strong résumé.

1. Read only the first word of every bullet, top to bottom. Does the left edge tell a coherent, active story on its own? If you hit "Responsible," "Helped," or "Worked," fix that bullet first — those are the dead openers.
2. Count your repeats. If "Managed" or "Led" appears more than twice, swap the extras for a truer, more specific verb. Repetition reads as a blur and caps how impressive the whole document feels.
3. Check every verb for a result. Each experience bullet should close on a number, a scope, or a concrete outcome. Flag any bullet that's all verb and no proof, and add the evidence or cut the line.
4. Hunt the buzzwords. Search for "results-driven," "dynamic," "detail-oriented," "team player," "passionate," "hard-working." Delete each one and replace the claim with the evidence underneath it.
5. Verify the tier. Does each verb honestly match your altitude? No "spearheaded" on solo coursework; no timid "assisted" on work you owned. Climb only as high as the truth allows.
6. Run the reference-check test. For every verb, ask whether your last manager would nod or wince. If they'd wince, dial the verb back to the truth and sharpen the evidence instead.

That sequence — read the edge, kill the repeats, demand a result, hunt buzzwords, verify the tier, pass the honesty test — is the difference between a résumé that reads as motion and one that reads as impact. When you want a second set of expert eyes on it, the Marqee resource library and our strategists are built for exactly this. And for the tooling side of the same job, the Résumé Tailor helps you align verbs and skill nouns to a specific posting fast.

Do this work once and it pays you back on every application for the rest of your search, because the discipline transfers. You stop reaching for the dramatic synonym and start reaching for the exact one. You stop claiming qualities and start showing evidence. You stop describing your relationship to the work and start describing the work. None of it requires a bigger vocabulary — it requires a more honest, more precise one, applied consistently. That's the whole craft, and it's learnable in an afternoon and improvable forever.

Frequently asked questions

Written by Marqee Editorial, Lead Career Strategist at Marqee. For more on building a résumé that wins both the parser and the person, read the ATS résumé guide and the résumé formatting guide, or explore the full resource library.