How to Write Resume Bullets That Get Interviews
Most bullets describe what you were responsible for. Interviews come from bullets that describe what changed because you were there. Here's the difference, mechanically.
Here is the single most common bullet point on earth:
• Responsible for managing the company's social media accounts.
It's not badly written. It's just inert. It tells a reader what you were assigned, which is a fact about your employer's org chart, not about you. Everyone who has ever held that job could write that line, which means it distinguishes you from precisely nobody.
Now the same job, written as a change:
• Grew Instagram from 4k to 27k followers in 11 months by shifting from daily product posts to a weekly customer-story series — which now drives ~18% of site traffic.
Same person. Same job. One of these gets a call.
Why do duty bullets fail?
Because a resume is not a job description — it's an argument. The claim is "hiring me will be good for you", and a duty bullet contains no evidence for that claim. It establishes only that you were present.
Recruiters and hiring managers read for delta. What was different afterwards? Was something faster, cheaper, bigger, safer, more reliable, less manual? A bullet with no delta is a bullet with nothing to react to, and it slides past the eye without registering.
What is the XYZ formula?
The most reliable structure — popularised as a Google recruiting guideline and since adopted almost everywhere — is:
Accomplished [X], as measured by [Y], by doing [Z].
It's a good formula not because it's magic, but because of what it forces. You cannot complete the sentence without naming an outcome, a measurement, and a method. And those three things happen to be exactly what an interviewer is going to ask you about anyway. A bullet written this way is a pre-answered interview question.
| Component | The question it answers | Example |
|---|---|---|
| X — the outcome | What actually changed? | Cut support ticket volume |
| Y — the measure | How much, and how do you know? | by 31% (1,200 → 830/month) |
| Z — the method | What did you do to cause it? | by rewriting the top 20 help articles and adding an in-app FAQ |
Assembled: "Cut monthly support tickets 31% (1,200 → 830) by rewriting the top 20 help articles and shipping an in-app FAQ." One line. Impossible to ignore. And you can talk about it for twenty minutes if asked.
What if you genuinely have no numbers?
This is the objection everyone raises, and it's almost always false. People think metric means revenue, and since they didn't personally close deals, they conclude they have nothing. But a metric is just any dimension that moved. Go hunting in these:
- Time — how long did the thing take before, and after? ("3 days → 4 hours")
- Frequency — how often did something happen? ("weekly outages → zero in six months")
- Volume — how much did you handle? ("a 40-person caseload", "~2,000 tickets/quarter")
- Scope — how many people, teams, countries, systems? ("rolled out to 6 offices")
- Quality — error rate, defect rate, rework, complaints, satisfaction.
- Money — not just revenue: budget owned, cost avoided, hours saved × loaded rate.
What are the mechanics of a good bullet?
- Start with a past-tense verb. Built, cut, shipped, negotiated, migrated, rebuilt, recovered. Never "Responsible for", never "Helped with", never "Worked on".
- Kill the first-person pronoun and most articles. Resume register is compressed. "Rebuilt the onboarding flow", not "I rebuilt our company's onboarding flow."
- One or two lines. Hard stop. A three-line bullet is two bullets that haven't been separated yet.
- Lead with the outcome, not the method. "Cut deploy time 6× by containerising the build" beats "Containerised the build, which cut deploy time 6×" — because the first four words are the ones that get read.
- Vary the verbs. Six bullets starting with "Led" reads as one bullet repeated six times.
If a bullet could appear on the resume of anyone who held your job title, it isn't a bullet. It's a job description you forgot to delete.
Frequently asked questions
What is the XYZ formula for resume bullets?
Accomplished [X] as measured by [Y] by doing [Z]. It forces every bullet to contain an outcome, a measurement, and a method — which is exactly the three things an interviewer will ask you about anyway. It became widely known as a Google recruiting guideline.
What if I don't have any metrics?
You almost certainly have more than you think. Metrics don't have to be revenue — time saved, frequency, volume, headcount, error rate, or scope all count. And where no number exists, a specific before-and-after state works nearly as well: 'replaced a manual weekly process with an automated one' is concrete even without a percentage.
How many bullets should each job have?
Three to five for your current or most recent role, and two to three for older ones. Depth on what's recent and relevant beats completeness on what isn't. Anything older than about ten years can usually be reduced to a single line.
Should resume bullets be full sentences?
No. Drop the leading 'I' and any articles that don't earn their place, start with a strong past-tense verb, and stop at one or two lines. A bullet running to three lines is almost always two bullets wearing a trench coat.