Resume Bullet Points That Read Like Evidence

Almost every resume advice site mentions the XYZ formula: "Accomplished X, as measured by Y, by doing Z." It comes from a Google blog post. It is genuinely useful. It is also widely misapplied.

Applied well, XYZ produces bullets that read like evidence. Applied badly, it produces bullets that read like a robot trying to sound impressive.

The XYZ format, briefly

Accomplished [X], as measured by [Y], by doing [Z].

Example: "Reduced p99 API latency from 340ms to 87ms by profiling and rewriting the payment intent service in Go."

The accomplishment (X) is the outcome — reduced latency. The measurement (Y) is the before and after — 340ms to 87ms. The method (Z) is how — profiling and rewriting in Go.

All three pieces are present and easy to identify. That is why XYZ works.

When to break it

The format becomes awkward when it is forced. Some bullets do not need all three parts:

• Not every bullet needs a number. "Led migration of the payments platform to Kubernetes" is a meaningful outcome without a metric. Adding "as measured by 100% of services migrated" would be padding.
• Not every bullet needs a method. "Mentored 4 mid-level engineers; 3 were promoted within 18 months" communicates outcome and impact without needing to specify how you mentored.
• Context bullets are allowed. If a role or achievement is too complex to compress to a single sentence, a short descriptive bullet is better than a tortured XYZ one.

Start with the verb

Every bullet should open with a strong past-tense verb. This signals both that you did something and what kind of thing it was.

Strong verbs by type:

• Built: Designed, built, launched, shipped, implemented, created, wrote, developed
• Improved: Reduced, increased, grew, scaled, accelerated, cut, improved, optimized
• Led: Led, managed, directed, owned, coordinated, mentored, hired, grew
• Solved: Fixed, resolved, debugged, prevented, eliminated, mitigated

Weak verbs to avoid: Responsible for, worked on, helped, assisted, participated in, involved in, supported. These describe presence, not outcomes.

Good and bad examples

Bad: "Responsible for managing the deployment process."
Better: "Managed deployment pipeline for 40 services."
Best: "Managed deployment pipeline for 40 services, cutting average deploy time from 90 minutes to 12."

Bad: "Helped with marketing campaigns."
Better: "Ran marketing campaigns across email, content, and paid."
Best: "Ran email marketing campaigns reaching 200K subscribers monthly, achieving 22% average open rate and 4.5% click-through."

How many bullets per role?

Three is the standard for a recent role. Two for older roles. One for roles from more than five years ago. Zero is acceptable for very old roles that are only listed for continuity.

More than five bullets per role is usually too many. If you have five things worth saying about a role, the reader will skim, and the strongest bullet loses to the weakest.

Aim for the smallest number of bullets that fully communicates the scope and impact of the role.

Order bullets by impact

Within each role, order your bullets by how impressive they are, not by chronological order or by category. The first bullet is read by everyone. The last bullet is read only if the reader is still engaged.

Put your strongest, most quantified, most directly relevant outcome first.

What if I don't have numbers?

You probably have more than you think. Common non-obvious metrics:

• Scale: Number of users, records, transactions, requests.
• Scope: Team size, number of stakeholders, number of countries or offices.
• Time: Reduction in cycle time, time to close, time to ship.
• Quality: Error rate, bug count, satisfaction score, NPS.
• Money: Revenue, cost, budget, savings.

If none of these apply, describe the outcome without a number. "Led the redesign of the checkout flow" is still an outcome even without a metric.