The XYZ Method Resume Guide
Learn the resume formula popularized by former Google people leader Laszlo Bock: Accomplished [X] as measured by [Y], by doing [Z].
Reviewed by Markus Fink
Senior Technical Recruiter · Formerly Google & Airbnb
What You'll Learn
What is the XYZ Method?
The Google XYZ formula is a compact format for writing achievement-focused resume bullet points. It was popularized by former Google people leader Laszlo Bock and is often written as:
Accomplished [X], as measured by [Y], by doing [Z].
- X — Accomplishment: the business, product, customer, or engineering result.
- Y — Measurement: the number, scale, frequency, or before-and-after evidence.
- Z — Method: the technical work or decision that produced the result.
The Google XYZ format works because it replaces a task description with evidence. A recruiter can see what changed, how much it mattered, and what you actually did.
The Formula Explained
You do not have to preserve the literal X-Y-Z order. The strongest version usually leads with the most impressive result, then adds the metric and technical method.
Result first
Reduced API p95 latency by 48% by replacing repeated database reads with a Redis caching layer.
Scale first
Processed 12M daily events with 99.95% pipeline reliability by migrating batch ingestion to Kafka and idempotent consumers.
Business impact first
Recovered $320K in annual revenue by identifying checkout failures and adding retry-safe Stripe payment handling.
All three bullets contain the same ingredients: a meaningful outcome, proof of scale or change, and a credible explanation of how the engineer caused it.
20+ Google XYZ Resume Examples
Use these XYZ resume examples as patterns, not copy. Replace every metric and technical detail with evidence you can explain in an interview.
Backend engineering
- Cut checkout API p95 latency from 780ms to 410ms by adding compound PostgreSQL indexes and removing N+1 queries.
- Reduced payment-related support tickets by 31% by implementing idempotency keys, structured retry handling, and clearer failure states.
- Supported a 4× traffic increase without additional instances by introducing request coalescing and Redis caching for read-heavy endpoints.
Frontend engineering
- Improved checkout conversion by 8.6% by reducing JavaScript bundle size 42% and moving noncritical scripts off the initial render path.
- Cut median page load time from 3.1s to 1.8s by adding route-level code splitting, responsive images, and server-rendered product data.
- Reduced accessibility defects by 67% by building tested form primitives and adding automated axe checks to CI.
Mobile engineering
- Raised crash-free sessions from 98.1% to 99.7% by tracing startup failures and replacing an unsafe local-storage migration.
- Reduced cold-start time by 39% by deferring analytics initialization and parallelizing independent network requests.
- Increased seven-day retention by 5.2% by shipping an offline-first onboarding flow backed by local caching and sync recovery.
Data and machine learning
- Improved recommendation click-through rate by 12% by retraining the ranking model with freshness features and better negative sampling.
- Cut warehouse spend by $9,400 per month by clustering high-volume tables and replacing full refreshes with incremental dbt models.
- Reduced pipeline recovery time from 3 hours to 25 minutes by adding checkpointed backfills, data-quality alerts, and idempotent jobs.
Infrastructure, DevOps, and SRE
- Improved service availability from 99.90% to 99.97% by redesigning health checks and automating failover for two critical services.
- Cut deployment time from 28 minutes to 9 minutes by parallelizing CI jobs and caching unchanged Docker layers.
- Reduced monthly AWS spend by 18% by right-sizing Kubernetes requests and scheduling nonproduction workloads outside business hours.
Leadership and collaboration
- Reduced new-engineer ramp time from six weeks to four by creating an ownership map, local setup automation, and a reviewed onboarding project.
- Increased quarterly delivery predictability from 62% to 87% by introducing dependency reviews and smaller milestone-based release plans.
- Cut recurring production incidents by 35% by leading postmortem follow-through and assigning measurable owners to reliability work.
Intern and new-grad experience
- Saved the support team 6 hours per week by building an internal React dashboard that consolidated customer-account diagnostics.
- Reduced test-suite runtime by 24% by identifying slow integration fixtures and replacing repeated setup with shared factories.
- Improved documentation search success by 15% by analyzing zero-result queries and adding synonyms for common developer terms.
How to Use XYZ When You Do Not Have Exact Metrics
Do not invent numbers. If exact percentages or revenue figures are unavailable, use defensible evidence of scope, frequency, speed, or adoption.
- Scope: services owned, repositories migrated, endpoints shipped, teams supported, or regions launched.
- Frequency: daily jobs, weekly releases, monthly incidents, or recurring hours saved.
- Before and after: manual to automated, nightly to near real time, days to hours, or several steps to one.
- Reliability: fewer alerts, safer rollbacks, eliminated failure mode, or clearer operational ownership.
- Adoption: used by the support team, adopted across engineering, or rolled out to all customer accounts.
Example without a percentage
Replaced a manual weekly access review with an automated audit workflow used by security and engineering, reducing the process from two days to under an hour.
XYZ Resume Bullet Checklist
Before keeping a bullet, check that a reviewer can answer each question in one pass:
- What changed? Name the product, system, workflow, or customer outcome.
- How much did it matter? Add a metric, scale marker, or concrete before-and-after result.
- What did you personally do? Include the technical decision, tool, or leadership action.
- Is the claim credible? Keep only details you can defend and explain.
- Is it concise? Remove filler such as responsible for, helped with, and worked on.
If your bullet names only a task, it is missing X. If it has no evidence, it is missing Y. If it hides your contribution, it is missing Z.
XYZ vs STAR Method
Both methods help you write better bullet points, but they serve different purposes:
| Aspect | XYZ Method | STAR Method |
|---|---|---|
| Best for | Resume bullets | Interview stories |
| Length | 1-2 lines | 2-5 minutes spoken |
| Focus | Metrics first | Context & action |
For resumes, XYZ is often more concise. Use STAR for interview preparation and longer-form descriptions.