Resume Bullet Points: The XYZ Formula That Actually Works

Most resume bullets are wallpaper. They describe responsibilities, use weak verbs, and leave the reader with no idea what the candidate actually accomplished. Strong bullets do the opposite — they answer "what did you do, what changed, and how did you do it" in a single sentence.

The most reliable structure for strong bullets is the XYZ formula, popularized by Laszlo Bock when he ran hiring at Google. This guide breaks it down with 20 before/after examples and a checklist you can apply to every bullet on your resume.

The XYZ formula

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

Three components:

• X — what you did. The action or accomplishment, led by a strong verb.
• Y — the measurable result. The number, percentage, scope, or outcome that proves the action mattered.
• Z — the method. The how. The specific tools, approaches, or decisions that made the result possible.

You can re-order the components, drop one if it genuinely doesn't apply, or split across multiple sentences. But every strong bullet has at least two of the three, and most have all three.

Why this works

Three reasons:

1. It forces specificity. A vague bullet ("Improved customer service") can't survive the formula — you'll be forced to name what improved, by how much, and how.

2. It gives the recruiter something to ask about. Interviewers love bullets they can dig into. "Tell me more about the migration that reduced latency 40%" is a real question. "Tell me more about being detail-oriented" is not.

3. It signals seniority. The ability to write XYZ bullets is correlated with the ability to do XYZ work. Recruiters internalize this — candidates who can describe scope, measurement, and method tend to be stronger hires.

20 before/after examples

Engineering

Before: Worked on improving the performance of the platform.

After: Reduced p95 API latency from 800ms to 120ms by introducing a Redis caching layer and consolidating 4 sequential database calls.

Before: Built features for the customer dashboard.

After: Shipped 8 user-facing features in the customer dashboard over 12 months, including the team's largest single product launch (used by 60% of active accounts within 2 weeks).

Before: Mentored junior engineers on the team.

After: Mentored 3 engineers through their first 6 months at the company, including weekly code reviews that reduced PR rework rate by 40%.

Data / analytics

Before: Created reports for marketing leadership.

After: Built the company's first marketing attribution model in dbt and Snowflake, reallocating $1.2M in annual ad spend toward higher-converting channels.

Before: Helped analyze experiments for the product team.

After: Designed and analyzed 14 A/B tests for the onboarding squad, with 4 driving company-wide changes that lifted D7 retention by 6%.

Product management

Before: Owned the user onboarding feature.

After: Led the onboarding redesign for a 30M-user mobile app, lifting D7 retention by 14% based on a 6-week A/B test.

Before: Worked closely with engineering on roadmap planning.

After: Partnered with 4 engineering teams on quarterly roadmap planning, including the discovery and prioritization process that produced our top revenue-driving feature of 2024.

Design

Before: Designed components for the design system.

After: Led the design system that now serves 4 product surfaces and 12 engineering teams, reducing component duplication by 70%.

Before: Conducted user research for the product team.

After: Ran 28 user interviews and 4 usability studies for the new checkout flow, surfacing the friction points that drove a 9% increase in completion rate after launch.

Marketing

Before: Managed paid search campaigns.

After: Owned $4M annual paid search budget across Google and Bing; improved blended CAC by 22% over 18 months through bid automation and landing page redesign.

Before: Wrote content for the company blog.

After: Wrote 30 SEO-driven articles that now generate 80K monthly organic sessions; 4 articles rank in the top 3 for category-defining queries.

Operations / project management

Before: Improved team processes.

After: Redesigned the customer onboarding process across sales, success, and support, reducing average time-to-activation from 18 days to 7.

Before: Led cross-functional projects.

After: Led the regulatory remediation program spanning 6 business lines and 40 stakeholders, delivered on time and 8% under a $4.2M budget.

Sales

Before: Exceeded sales quota.

After: Closed $2.4M in new ARR at 142% of quota in 2024, including the largest single deal in the mid-market segment.

Before: Built relationships with key accounts.

After: Expanded 6 existing enterprise accounts by an average of 38% YoY through multi-stakeholder discovery and tailored business reviews.

Healthcare

Before: Provided patient care on a busy unit.

After: Provided direct care for a 6:1 patient load on a 32-bed med-surg unit averaging 95% occupancy; precepted 4 new graduate nurses over 12 months.

Before: Worked on improving patient outcomes.

After: Co-led a sepsis early-recognition initiative on the unit, contributing to a 19% reduction in time-to-antibiotic administration over 6 months.

Customer success / support

Before: Managed customer accounts.

After: Owned a book of 40 mid-market accounts ($8M ARR); maintained 96% gross retention through quarterly business reviews and proactive churn risk monitoring.

Before: Resolved customer tickets.

After: Resolved 350+ technical support tickets per quarter at 4.8/5 CSAT; authored 14 knowledge base articles that reduced repeat ticket volume on the top 3 issues by 30%.

The 5-question bullet checklist

Run every bullet on your resume through this:

1. Does it start with a strong action verb? Not "Responsible for," not "Tasked with." (See 200+ resume action verbs.)
2. Is there at least one specific number or named scope? A percentage, a count, a dollar amount, a team size, a named system.
3. Could anyone in the role have written this same bullet? If yes, it's too generic. Add specifics until it's clearly about you.
4. Does it give the interviewer something to ask about? A good bullet plants a hook.
5. Is it under 2 lines? Bullets over 2 lines get skimmed. Tighten.

The metric problem (and how to solve it)

"I don't have any metrics" is the most common objection to the XYZ formula. Almost always wrong. Sources of metrics most people forget:

• Volume: How many of something did you do? Tickets, features, customers, reports, meetings, hires.
• Scope: What did you own? Team size, budget, codebase, product surface.
• Comparison: Did anything become faster, smaller, larger, cheaper, more accurate compared to before?
• Quality: Error rates, satisfaction scores, defect counts, audit results.
• Influence: How many people / teams used what you built?

If after all that there are genuinely no numbers, lean into named scope: "the company's first attribution model," "the only on-call engineer for the platform team," "the lead designer for our largest enterprise account."

Common XYZ formula mistakes

• Big number, no context. "Reduced costs by $400K" — over what timeframe, on what budget? Without scope, the number is meaningless.
• Method without outcome. "Implemented Kubernetes" — okay, but did it matter? Pair with the result.
• Outcome without method. "Increased revenue 35%" — how? The "how" is what differentiates you from someone who just happened to be there.
• Stacking too many numbers. A bullet with 4 different percentages is hard to read. Pick one or two anchors and use scope for the rest.
• Overusing "led." "Led X, led Y, led Z" within the same role looks lazy. Use different verbs: drove, designed, built, scoped, owned, ran.

One transformation, step by step

Starting bullet:

Worked on improving website performance.

Step 1 — Add an action verb: "Led website performance improvements."

Step 2 — Add scope: "Led performance improvements across the marketing website (50 pages, 200K monthly visitors)."

Step 3 — Add the result: "Led performance improvements across the marketing website, cutting average page load from 4.2s to 1.4s."

Step 4 — Add the method: "Led performance improvements across the marketing website by introducing image lazy-loading, CDN caching, and a webpack bundle audit — cutting average page load from 4.2s to 1.4s and lifting organic traffic by 18% within 90 days."

Final: 38 words. Specific, measurable, interview-worthy. Five times longer than the original, but on a resume read in 8 seconds, that one bullet now does the work of five vague ones.

FAQ

How many bullets per role?

3–6 for recent and senior roles, 1–3 for older or less relevant ones. Each role should have at least 3 if you want it to register; roles with only 1 bullet read as filler.

Should bullets be in past or present tense?

Past tense for past roles, present tense for current. Within each role, stay consistent.

Do periods at the end of bullets matter?

Stylistically only. Be consistent — either all periods or none. Most modern resumes drop the periods.

Can I use the same bullet for multiple jobs?

If two roles genuinely involved the same accomplishment, sure. But if you're tempted to reuse bullets, it usually means you're not capturing what was different about each role.