How to write resume bullet points that show impact

Open your resume and count the bullets that start with "responsible for," "managed," or "worked on." Those lines describe the job you were given. They'd read exactly the same if you'd been mediocre at it, and the person skimming has no way to tell the difference.

This article covers what a strong bullet actually contains, and a stack of before and after rewrites you can copy the pattern from. It also covers how to find a number when you're sure you don't have one, what to do when the work has no metric, and what to cut. Work through your current role first, since that's the section people read most closely and the one where you remember the details.

Most of the advice here comes from Ethan Evans, a retired Amazon VP who spent 15 years there and ran more than 40 "Real Resume Review" episodes where he opens a real person's resume on screen and rewrites it live. Deb Liu, CEO of Ancestry and formerly a VP at Facebook, and Lauren Ipsen, who recruits senior executives at Daversa Partners, fill in the parts about finding and rehearsing your own evidence. Every quote plays the exact moment it was said.

Start with what changed because you were there

Reviewing a technical program manager's resume, Evans walked through the STAR structure that good companies interview with, situation, task, action, result, and pointed out that most people write the first three and stop.

That's the whole rewrite in one sentence. A hiring manager can hand those tasks to anyone. What they're paying for is the outcome you produced with them. So every bullet needs to answer a question that most bullets never get to: what was different afterward?

Evans has a blunt name for the lines that skip it. Going through a resume from a Harvard graduate applying to director of mergers and acquisitions roles, he hit a bullet about "sourcing and executing mergers and acquisitions while cultivating highly strategic partnerships to create vertically integrated capabilities and IP" and called it happy talk.

A few minutes later in the same review he gave the test in a single question: "what job couldn't this be written about?" He then proved the point by rewriting one of the bullets to describe his stepson's job at McDonald's, which worked fine. Run that test on your own lines. If a bullet could sit on the resume of someone two levels below you at a different company, it's telling the reader nothing.

What a strong bullet contains

Four things, in roughly this order.

Reviewing a resume that got its owner a job, Evans said the thing he liked most was that every single bullet opened with a verb: owned, streamlined, delivered, managed, improved, conducted. His read on it was "this is someone who gets shit done," and his guess was that the verbs are what got the interview.

One more constraint worth knowing before you start. Asked how many bullets a job should get, Evans said he has no idea what the right number is, but the key is to "drive to the point": what you were responsible for, what you did, what results and value you created, what skills you learned. If your bullets run several lines each, you need fewer of them, and one-line bullets let you run a few more. Length follows from how fast each line gets to the point.

Rewriting ten real bullets

The patterns below cover almost every weak bullet we see. Find yours, then copy the shape of the rewrite.

Bullets that only describe the job you were given

Bullets that stop just before the result

These are the near misses. There's real work described, the verb is fine, and then the sentence ends right where the interesting part starts. Evans hit one of these on the M&A resume, a bullet that said "aimed at" a revenue target, and stopped cold on it: "Aimed at? Does that mean you did it or not? What were the results? I'm gonna hire somebody who gets results."

Bullets that hide behind big words

How to find the number when you think you don't have one

Most people say their work can't be measured. Usually they've just never sat down and looked for a number. Evans ran into this on a senior product manager's resume, where one bullet happened to mention a billion in revenue and the rest said nothing about outcomes at all.

Work through these questions on each piece of work. One of them almost always produces something.

If this feels uncomfortable, you're not the only one. Plenty of people go blank here because writing down their own results feels like bragging. Deb Liu hears it constantly when she asks people about their self-reviews, and her answer reframes the whole exercise.

The same reframe works on a resume. You're telling someone who wasn't there what happened, which is a different job from talking yourself up. If you keep a running record of your results during the year, this whole section takes twenty minutes instead of a weekend. The evidence log in our raise playbook is the version we recommend keeping, and it feeds your resume, your self-review, and your promotion case from one place.

Make the numbers believable

Numbers do two jobs on a resume. They tell the reader the size of what you did, and they show that you're the kind of person who knows their own results. Evans made the second point on a resume packed with specific figures.

Elsewhere he explains why this works: people believe numbers on resumes because they seem verifiable. He could call your old employer and ask whether you really managed $400M in acquisitions, and they'd say yes or no. He probably won't call. The fact that he could is why people trust a number and skim past an adjective.

Which means the rules for using numbers are mostly about staying defensible.

Show scope and judgment when there's no metric

Some real work doesn't produce a number. Compliance work and early research often don't, and neither does a rewrite that prevented problems nobody ever saw. Those bullets still have to show impact, so show it a different way.

Scope tells the reader how big the thing was. Team size, budget, number of markets, systems touched, revenue supported, how many people depended on it. "Owned the data retention policy for 12 systems and about 4 million user records" says plenty with no outcome metric at all.

Naming the hard call is how you show judgment. Name the tradeoff you chose and what it cost. "Cut two of five planned features to hold the launch date, and shipped on schedule" tells a hiring manager more about your seniority than most metrics do.

Firsts and durability both count. "First security review process the company had," or "the runbook the on-call team still uses three years later." If something you built is still in use after you left, that counts as evidence.

Recognition counts when it's specific. Someone asked you to run the next one, pulled you onto the escalation, or handed you the account. Say who asked and what for.

What doesn't work is dressing up a metric-free bullet with adjectives. "Successfully delivered a highly complex initiative" adds nothing that "delivered the initiative" didn't already say. When you catch yourself reaching for an adjective, go find a fact instead. This matters most in senior roles, where how you position the level of work you do is doing as much for you as the numbers are.

What to cut

Evans's standard for the whole document is that every line has to earn the reader reading on. Anything that doesn't is taking space from something that would.

Cutting has a second benefit. The bullets you keep are the ones the interviewer asks about, which means cutting is how you steer the conversation. Our resume tailoring playbook covers picking those three or four stories first and then editing the file to point at them.

Check your bullets against the stories you'll tell

A bullet is a promise that you can talk about the work for two minutes. So the last check is to say each one out loud.

Take your five strongest bullets and, for each one, tell the story behind it: what the situation was, what you did, what happened, and what you'd do differently. If you can't get through it, either the bullet is overstated or you haven't thought about the work since you did it. Either one is worth fixing now, because you won't get the chance once you're in the interview. Ipsen watches senior candidates figure this out far too late.

"Someone to be missed" is a good phrase to write bullets against. If a line describes work that would have happened anyway without you, it isn't earning its space. Once the spoken versions are solid, the behavioral interview playbook covers structuring them for "tell me about a time" questions, so the same evidence carries your resume and your answers.

Frequently asked questions

How many bullets should each job get?

Evans says there's no ideal number and the real constraint is how fast each line gets to the point. In practice: four to six for your current role, three to four for the one before, one or two for anything older than about ten years. Long multi-line bullets mean you need fewer of them.

What if my results took a whole team?

Most results do, and hiring managers know that. Name the team result and your specific part in it. "Grew the team from 4 to 11 engineers" as the hiring lead is honest even though you weren't the only interviewer. What you can't do is present a team number in a way that implies you did all of it, because that unravels in the first follow-up question.

Is it a problem if I can't share exact figures?

No, and plenty of people can't for confidentiality reasons. Use ratios and relative movement: "cut processing time by 60%," "doubled the active user base," "top quartile of the sales org." Evans reviewed a resume where the person had swapped real figures for XX placeholders and treated that as perfectly fine.

Should the bullet include the whole story?

No. Give the result and one clause about how, then stop. A bullet that explains everything leaves the interviewer nothing to ask, and the questions you invite are the ones you've prepared for.

What about a first job with no real results yet?

Use scope, speed, and firsts. How many of something you handled, how quickly you were given work above your level, anything you built that people still use. Coursework and projects count if you say what came of them, though they should drop off once you have a year of real work.

Do these bullets work for LinkedIn too?

Mostly yes, with one adjustment. LinkedIn is read by people who aren't screening you for a specific job, so lead with the two or three results that make someone want to message you, and keep the rest shorter than on the resume.

The rewrite on one page