How to write resume bullets that actually get callbacks
Most resume bullets describe what you did. The ones that get callbacks describe what changed because you did it. Here is how to write the second kind.
Most resume bullets describe what someone did. The bullets that get callbacks describe what changed because they did it. That's the whole game. Once you see the difference, you can't unsee it, and your resume gets shorter, sharper, and far more useful to the person reading it.
Here is the version of this advice that actually works.
The two-bullet test
Read these out loud:
The first one tells a recruiter you had a job. The second one tells them what they get if they hire you. The lift here matters: a jump from 0% to 0% retention on 0 signups/month is the kind of number a hiring manager underlines.
The second bullet is also shorter on the page in the sense that matters: a tired hiring manager only has to read one line to decide you're worth a 30-minute call.
The shape: action, scope, outcome
Every bullet that earns a callback has three parts, in some order.
- Action. A verb you'd say in a meeting. Built. Cut. Shipped. Migrated. Negotiated.
- Scope. The thing you affected and how big it was. One service, one team, $4M ARR.
- Outcome. The number, percentage, time saved, or risk eliminated.
If you only have two of those three, the bullet is still better than 80% of bullets you'll see. If you have one of them, you're describing a job description, not a person.
Five rewrites, side by side
Look for the move in each pair. The pattern shows up over and over once you start watching for it.
1. From "responsible for" to "owned, with a result"
2. From "helped" to "shipped"
"Helped" is a hedge. If you really only helped, name what part you owned. The team will be fine. The recruiter wants to know what you can do for them.
3. From feature list to behavior change
4. From soft to specific
"Improved team collaboration" is a feeling. "Eliminated two meetings" is a thing the reader can picture. Pictures get callbacks. Feelings don't.
5. From task list to single best result
One strong outcome beats three vague ones. If you can only fit four bullets per role, make every bullet do real work.
"But I don't have numbers"
Almost everyone says this. Almost everyone is wrong about it. You probably have at least one of:
- Time. How long did the old way take? How long did the new way take?
- Volume. How many tickets, customers, dollars, deploys, students, or events?
- People. How many people on the team you led, mentored, hired, or unblocked?
- Frequency. Daily, weekly, the first time anyone had done it at the company.
- Range. "Across 4 product lines" is a number. "For our top 20 accounts" is a number.
If you genuinely can't quantify the outcome, quantify the scope. "Owned billing for a 7-person engineering org" beats "owned billing" every time, even with no outcome attached.
The 30-second pass
Before you ship a resume, do this. Read every bullet and ask: so what? If the answer is obvious, the bullet is doing its job. If the answer is "I don't know," cut the bullet or rewrite it until it earns its line.
Most resumes have 25 to 35 bullets. If 5 of them pass the so-what test cleanly, you'll outperform 90% of the inbox.
Paste a bullet from your resume.
Live scored on the three things that matter: action verb, scope, outcome.
One more thing about ATS
ATS (the resume software companies use to screen applications) gets blamed for a lot of rejections it didn't cause. Most ATS systems just parse your resume into fields and search for keywords. They are not secretly ranking your bullet writing. A clean, plain-text-friendly resume with the job's actual keywords in your real bullets will pass almost all of them. Don't write for the robot. Write for the human who reads after the robot waves you through.
Now go open your resume and rewrite three bullets. You'll feel the difference by the second one.