Two candidates did the same job. One set of resume bullet points gets screened out in seven seconds, and the other gets the call.
The difference isn’t the work. It’s that one set describes what the person was responsible for, while the other describes what changed because they were there. Hiring managers can’t act on responsibility. However, they can act on proof.
The fix: write every bullet as “Accomplished X, as measured by Y, by doing Z.” Result first, number second, method third.
Why duty lists lose the seven-second scan
Recruiters don’t read your resume. They scan it. Ladders’ 2018 eye-tracking study put the initial screen at an average of 7.4 seconds, and most of that budget goes to your title, your company, and your dates.
Whatever is left has to land in about two seconds. So a line like “Responsible for managing the quarterly reporting process” spends that budget telling a screener something they already assumed from your job title. They gave you the title. Of course you were responsible for it.
A duty list also flattens everyone. Seniority vanishes: “responsible for” reads identically whether you did the bare minimum or rebuilt the entire function. That’s why strong candidates lose to weaker ones who write better. The screener isn’t comparing careers, because at that speed nobody can. They’re comparing sentences. I’ve written before about how hiring managers actually decide, and it lands in the same place: being obvious beats being impressive.
The formula behind resume bullet points that get read
Laszlo Bock ran hiring at Google as its Senior Vice President of People Operations. In 2014, he published his personal formula for a resume, and it’s still the cleanest structure anyone has put in writing:
Accomplished [X], as measured by [Y], by doing [Z].
Three parts, each doing a specific job:
- X is the outcome. Not the task you were assigned, but the thing that was different afterward. Revenue, cycle time, error rate, retention, cost.
- Y is the number that proves it. A percentage, a dollar figure, a headcount, a duration. Anything a skeptic could check.
- Z is how you did it. The decision, the method, the call you made. This is where your judgment shows up.
Notice the order. Most people write Z first, because that’s the part they actually remember doing. But a screener needs X to decide whether to keep reading, so X goes first every time.
Directionally truthful: what to do when nobody tracked a number
Here’s where this falls apart for most people. They understand the formula fine. Then they stare at a bullet and think: I don’t have a number for this. Nobody measured it. I’d be making it up.
What you’re looking for is something directionally truthful. You don’t need accuracy. Instead, you need to be in the right ballpark, and you need to be able to defend how you got there.
So reconstruct it. When you don’t know the exact figure, ask:
- How many people were on the team, and how often did the thing happen?
- What did it take before you changed it, and what did it take after?
- What was the budget you touched, even roughly?
- If it had broken, what would that have cost?
A bullet that says “cut a four-hour weekly report to about 30 minutes” holds up even though nobody logged it, because you can walk through the arithmetic in the interview. That isn’t inflation. That’s estimation, and every hiring manager does it daily.
One rule, though: never write a number you can’t defend out loud. If you can’t reconstruct it on the spot, cut it and use scale instead. Team size, budget size, number of markets, volume handled. Scale is a number too.
Z is where seniority shows up
Most people treat the third part as filler. It isn’t. Z is the only place your resume shows judgment rather than output, and it’s usually what separates a senior bullet from a mid-level one.
The question I ask in sessions: were you the admitting nurse, or were you House? If somebody handed you the problem already diagnosed, as in “our fraud rate is too high, go fix it,” then you executed. That’s fine, but it’s a different story. Alternatively, if you asked why the fraud rate was high, ran the tests, and found a cause nobody had named, that belongs in Z.
Compare these:
- “…by implementing the new fraud rules engine.”
- “…by tracing 60% of chargebacks to a single checkout flow and rebuilding that path first.”
Same project. Yet only the second one proves you diagnosed something. That’s the difference between reading as a doer and reading as someone ready for the level above the one you’re in now.
Before and after, across three functions
Engineering
Before: “Responsible for improving application performance.”
After: “Cut median API response time 40%, from 820ms to 490ms, by adding read replicas and removing three redundant service calls.”
Marketing
Before: “Managed email campaigns for the company newsletter.”
After: “Grew newsletter-driven pipeline 22% in two quarters by segmenting the list by lifecycle stage and cutting send volume in half.”
Operations
Before: “Oversaw vendor relationships and contract renewals.”
After: “Saved roughly $180K a year across 14 vendor contracts by consolidating overlapping tools and renegotiating three renewals in one quarter.”
None of these rewrites required a bigger job. In each pair, the underlying work is identical. Nevertheless, only the “after” gives a screener something they can repeat to a hiring manager in a hallway.
Your 20-minute pass
Here’s the pass I run with clients on their resume bullet points. Do this today, not this weekend:
- Open your resume and read only the first bullet under each role. Those are the lines that get scanned.
- Circle every one starting with “Responsible for,” “Managed,” “Helped,” “Worked on,” or “Supported.” Those are duty lines.
- Rewrite the top two using the formula. Two, not twelve, because momentum matters more than completeness here.
- Say each rewrite out loud and ask whether you could defend the number for 30 seconds. If not, swap it for scale.
- Check that your resume summary promises what your new bullets now deliver.
Across the 250+ mid-career tech professionals I’ve placed, this is the most common rewrite in my practice, and it’s almost never a case of someone lacking results. They have the results. Therefore the real problem is a formatting habit picked up from whatever resume template they downloaded last, and habits like that are cheap to break.
Frequently asked questions
How many resume bullet points should each role have?
Three to five for your current and most recent role, then two to three for older ones. Depth belongs where the relevance is.
Does every bullet need a number?
No. Aim for a number in the first bullet of each role and in roughly half the rest. A resume where every single line carries a statistic starts to read as padded.
What if my work genuinely can’t be measured?
Use scale instead of impact: team size, budget, user count, number of markets, volume handled. “Supported 40 engineers across three time zones” tells a screener far more than “supported the engineering org.”
Should I use the same bullets for every application?
Keep the same facts, but reorder them. Move the bullet matching the job’s top requirement to the top of that role. Rewriting from scratch each time wastes hours, whereas resequencing takes two minutes.
Do these rules still apply for a career change?
More than ever. When your titles don’t match the target role, your bullets are the only place you can show outcomes that transfer.
What to do next
If you want to see where your search is actually leaking, take the RHINO quiz. Five minutes, no email required.
If your resume keeps getting scanned and skipped, read 7 Resume Mistakes That Kill Your Callbacks in Tech next. It covers the six other habits doing the same damage as a duty list.
If you would rather have someone read your resume line by line and tell you which bullets to fix first, book a free strategy call.