Google XYZ formula for resumes: 20 examples for engineers
The Google XYZ formula for resume bullets (accomplished X, measured by Y, by doing Z), when not to force it, and 20 examples for engineers.
By the fastcv team · 26 October 2026 · 7 min read
The Google XYZ formula is a way to write resume bullets as results: "Accomplished [X] as measured by [Y] by doing [Z]". X is what you achieved, Y is the number that proves it, and Z is how you did it. It was shared in 2014 by Laszlo Bock, then Google's head of People Operations, as his personal formula for a winning resume, and it's still the simplest way to turn a list of duties into proof.
Below: how to use it step by step, what to do when you don't have numbers, when not to force it, and 20 before-and-after bullets for software, data and student resumes.
Why the XYZ formula works
Recruiters skim. A bullet like "Worked on the payments API" tells them you were near something; it doesn't tell them you were good at it. The XYZ formula forces three things a reviewer wants:
- X, the outcome: what changed because of your work.
- Y, the measure: how much, so the claim is concrete and comparable.
- Z, the method: the skill or tool you used, which is also where job-post keywords naturally fit.
Bock's point was that specifics stand out even when the accomplishment is modest. A small, concrete result reads stronger than a big, vague one.
How to write an XYZ bullet in 4 steps
- Pick a piece of work from a job, internship or project that matters for the role you're applying to.
- Ask "what got better?" Faster, cheaper, more users, fewer errors, less manual work, a feature shipped. That's X.
- Find the number. Before and after, percentage, count, time, money, scale (users, requests, rows). That's Y. Use one you can explain if asked.
- Name how you did it, with the specific technique or tool. That's Z.
Then rearrange for readability. The formula doesn't have to read in X-Y-Z order; leading with an action verb is usually clearer:
Cut checkout API latency from 900 ms to 250 ms (Y) by adding Redis caching and removing 3 synchronous calls (Z), raising conversion 1.8% (X).
No numbers? Use these instead
Not every task has a clean metric, especially for students. You can still be specific:
- Scale: "for 1,200 shops", "on a 2M-row dataset", "across 40 services".
- Users or adoption: "now used by the 30-person support team", "120 GitHub stars".
- Time: "shipped in 3 weeks", "replaced a 2-day manual task".
- Before and after state: "ended nightly job failures", "zero duplicate payouts since launch".
- Recognition: "selected for the national finals of Smart India Hackathon", "merged into the main repository".
Never invent a number. If you don't know a percentage, give the scope instead; it's just as convincing and you can defend it in an interview.
When not to force the formula
Bock's advice was about making accomplishments measurable, not about writing every line identically. A page of bullets that all read "Accomplished X as measured by Y by doing Z" becomes tiring and robotic, a point career advisers have made too. Use XYZ for your most important bullets, typically the first one or two in each role, and keep supporting bullets shorter.
20 XYZ examples for engineers and students
Backend and full-stack
| Before | After (XYZ) |
|---|---|
| Worked on the payments API. | Cut payments API p95 latency from 420 ms to 180 ms by adding Redis caching and fixing N+1 queries in PostgreSQL. |
| Migrated cron jobs to a queue. | Removed nightly job failures and saved ₹3.1L a month in compute by moving 14 cron jobs onto Kafka-based processing. |
| Built REST APIs in Spring Boot. | Launched 12 Spring Boot APIs for loan applications serving 30K requests an hour by designing paginated, cached endpoints. |
| Helped with database design. | Achieved zero duplicate payouts on 1.2M daily transactions by designing idempotent settlement writes in PostgreSQL. |
Frontend and mobile
| Before | After (XYZ) |
|---|---|
| Made the website faster. | Raised the Lighthouse performance score from 54 to 92 by code-splitting routes and serving images in AVIF. |
| Built the onboarding flow in React. | Lifted day-7 retention from 31% to 36% for 120K monthly users by rebuilding onboarding in React with progressive steps. |
| Fixed app crashes. | Raised the Android app's crash-free user rate from 97.1% to 99.6% by fixing the top 15 Crashlytics issues. |
| Improved app startup. | Cut cold-start time from 2.8 s to 1.1 s by adding Baseline Profiles and lazy-loading SDKs. |
Data, ML and DevOps
| Before | After (XYZ) |
|---|---|
| Created Power BI dashboards. | Replaced 6 manual Excel reports for 40 regional managers by building a weekly Power BI sales dashboard. |
| Did churn analysis in SQL. | Cut early churn 18% by finding through SQL cohort analysis that 62% of churn came in the first 14 days, prompting an onboarding change. |
| Built a fraud model. | Caught 31% more fraudulent orders than the rules engine at the same false-positive rate by shipping a LightGBM model. |
| Set up Kubernetes. | Cut deploy time from 40 minutes to 8 by moving 20 services to Kubernetes with Helm and GitHub Actions. |
| Handled on-call. | Reduced pager alerts 60% in a quarter by fixing the 5 noisiest alerts and writing runbooks for the rest. |
| Wrote data pipelines. | Made 300 GB of daily events queryable within 15 minutes by building Spark ingestion jobs on S3. |
Students, interns and freshers
| Before | After (XYZ) |
|---|---|
| Made a chat app using MERN stack. | Built a real-time chat app with React, Node.js and Socket.IO that handled 200 concurrent users in load tests. |
| Did an internship at a startup. | Shipped a CSV import feature in Django during an 8-week internship, now used by 30+ client teams. |
| Good at DSA. | Solved 600+ LeetCode problems (rating 1850) and reached Codeforces Specialist. |
| Final year project on plant disease. | Classified 38 leaf diseases at 96% top-1 accuracy on held-out data by fine-tuning EfficientNet in PyTorch. |
| Organised a college tech fest. | Grew the college tech fest to 2,000 attendees and ₹4L in sponsorship by leading a 25-person team. |
| Contributed to open source. | Got 3 pull requests merged into an open-source Python library, fixing date-parsing bugs reported by users. |
All of these are examples; every number in your own bullets has to be real.
XYZ vs STAR: which one for resumes?
STAR (Situation, Task, Action, Result) is built for interview answers, where you have time to tell the story. XYZ is built for resume bullets, where you have one line. Use XYZ on the resume, and keep the STAR version of each important bullet ready for the interview. The bullet is the headline; the STAR story is what you say when they ask about it.
Put it into practice
Rewrite your top bullet in each role with the four steps above, then check the result against a real job post with the free resume and job description checker. For formatting that keeps these bullets readable to both people and parsing software, start from Jake's Resume in the builder. For more role-specific bullets, see the samples for backend engineers, data analysts and freshers, and our guide to getting shortlisted at Google and Amazon.
Frequently asked questions
What is the Google XYZ formula for resumes?
It's a template for resume bullets: "Accomplished [X] as measured by [Y] by doing [Z]". X is the result, Y the number that proves it, and Z how you achieved it. It was shared by Laszlo Bock, Google's former head of People Operations, in 2014.
Do I have to use the XYZ formula for every bullet?
No. Use it for your strongest one or two bullets per role. Writing every line the same way reads as robotic; supporting bullets can be shorter.
What if I don't have any numbers?
Use scale (users, data size, number of services), time saved, adoption or a clear before-and-after state. Never invent a number you can't explain in an interview.
Is the XYZ formula only for Google applications?
No. It works for any resume because every recruiter is looking for evidence of impact. Amazon's recruiters, for example, also ask for measurable data and straightforward language.
What's the difference between the XYZ and STAR methods?
XYZ fits a one-line resume bullet; STAR (Situation, Task, Action, Result) structures a longer interview answer. Write XYZ bullets on the resume and prepare a STAR story behind each.