Methods/XYZ Resume Format Generator
Free. No signup. The Laszlo Bock formula made famous at Google: accomplished [X] as measured by [Y], by doing [Z]. Paste your experience; we'll structure it — and refuse to invent the number.
0 characters · the XYZ format depends on a real metric (count, %, time, dollars). The more specific you are, the stronger the bullet.
Free · 1 generation per request · no signup
Definition
XYZ is a resume bullet template popularized by Laszlo Bock, the former SVP of People Operations at Google (2006-2016). Bock first described the formula in a 2014 New York Times interview, then wrote it up himself in a LinkedIn post, “My Personal Formula for a Winning Resume.” A Google recruiter has since used the same three-part structure in one of Google's own recruiting videos — so it's Bock's personal method, echoed in Google's own hiring materials, proposing that every resume bullet follow a single formula:
Accomplished [X] as measured by [Y], by doing [Z].
The three slots map to three concrete questions:
What you accomplished
The outcome, not the duty. "Cut deployment time" not "was responsible for deployments."
How it was measured
The number that proves the accomplishment was real. Count, percentage, time, dollars, scope.
What you did
The action, tools, methods. The verb-and-stack part.
Bock's argument: most resumes describe responsibilities instead of outcomes. XYZ structurally fixes this by demanding a measurement in every bullet.
The compressed bullet typically reads 20-40 words. The format works best for technical and data-heavy roles where metrics are available — though it applies anywhere you can put a real number on the work.
Step-by-step
Before writing anything, dig for the number. Users, requests, dollars, percentage, time saved, tickets resolved, conversion rate. If no real metric exists for the work, XYZ is the wrong format for that bullet — switch to STAR.
Open with what was accomplished, not what you were responsible for. "Cut homepage load time" — not "was responsible for performance." The outcome is what hiring managers care about; the duty is invisible.
The number is the load-bearing part of the bullet. Specific numbers beat round numbers — "reduced p95 latency from 840ms to 290ms" reads more credibly than "improved performance by 4x." If your only number is a percentage, include the base if it's small (1% of 50M ≠ 1% of 50).
Name the tools, languages, methods, scope. This is where credibility lives. "By migrating the image pipeline from on-the-fly resizing to a CDN-cached, pre-computed asset bucket" is a 22-word bullet section that any reviewer can verify.
Before → After
Each bullet includes a real X, a real Y, and a real Z. The metric is the part that does the work.
Software engineering intern
Worked on improving site performance for the e-commerce team.
Cut homepage p95 load time from 4.2s to 1.6s (–62%) by migrating product images to a CDN-cached, pre-computed asset bucket and removing 3 render-blocking scripts.
Marketing intern
Helped run cold outreach for the sales team.
Lifted outbound reply rate from 2.1% to 6.8% across 1,200 sends by rewriting 6 cold-email templates and running 4 weeks of A/B tests in HubSpot.
Data analyst intern
Analyzed sign-up data and shared findings with the product team.
Identified the top 3 onboarding drop-off points (40% combined exit rate) by writing SQL against a 12M-row event log; the redesigned welcome flow lifted D7 retention by 4 points.
Social media intern
Ran the social media accounts during the summer.
Grew combined Instagram + TikTok following from 8.2K to 14.6K (+78%) in 12 weeks by publishing 4 posts/week and producing the highest-performing video in the brand's history (1.1M views).
For 30 more before/after bullet pairs across 8 role types, see Resume bullets that get callbacks: 35 before-and-after examples.
Pick the right framework
| Framework | Stands for | Best for |
|---|---|---|
| XYZ | Accomplished X by doing Y, measured by Z | Tech, data, product — outcome-first, requires a real metric |
| STAR | Situation, Task, Action, Result | Resume bullets + behavioral interviews — most flexible |
| CAR | Challenge, Action, Result | Consulting and leadership bullets — front-loads difficulty |
What kills the bullet
The most damaging XYZ failure. The bullet looks complete ("Lifted conversion 47% by redesigning the funnel"), but the 47% was guessed. Recruiters detect inflated metrics on a careful read; one challenged number kills the credibility of the whole resume. If you don't have a real number, don't write XYZ.
"By improving the process" or "by working with the team" is not a Z. The Z is where credibility lives — name the tools, methods, scope. "By migrating the image pipeline from on-the-fly resizing to a CDN-cached pre-computed asset bucket" is a Z. "By doing improvements" is not.
Bullets that open with the action and end with the outcome read like duties. XYZ inverts this: lead with the accomplishment so the recruiter sees it in the first 6 seconds. "Cut latency by 62%" first; "by migrating the image pipeline" second.
"Reduced load time by 50%" reads suspicious. "Reduced p95 load time from 4.2s to 1.6s" reads measured. Specific numbers carry trust; round numbers feel estimated. If you have the precise number, use it.
FAQ
XYZ is a resume bullet template popularized by Laszlo Bock, Google's former SVP of People Operations. The formula is: 'Accomplished [X] as measured by [Y], by doing [Z].' X is the outcome, Y is the measurement (the number), and Z is what you actually did. The format forces every bullet to lead with an accomplishment and prove it with a metric.
Laszlo Bock — Google's SVP of People Operations from 2006 to 2016 — first described it in a 2014 New York Times interview, then wrote it up himself in a LinkedIn post titled "My Personal Formula for a Winning Resume." A Google recruiter has since used the same three-part structure in one of Google's own recruiting videos. It's best described as Bock's personal method, echoed in Google's own hiring materials — not an official, universal Google policy. His core argument: most resumes describe duties instead of outcomes, and XYZ corrects this by structurally requiring a measurable result.
Then XYZ is not the right format for that bullet. The Y is the entire point — without a real metric, you'd need to invent one, which is exactly what we won't do. Either dig harder for the number (count of users, time saved, % change, dollars, scope), or use the STAR format for that bullet instead. The tool will return an honest note when your input lacks a metric.
20-40 words. XYZ is naturally tighter than STAR because it compresses everything into one structured sentence. Aim short — recruiters spend 6-8 seconds on a resume, and XYZ's value is that the outcome and metric are visible inside that window.
No. The system prompt explicitly forbids fabricating numbers, scope, tools, or outcomes you didn't state. If you didn't give a number, the tool returns an honest qualitative summary plus a note urging you to add a real metric. Always read the output before pasting it.
XYZ is tighter and outcome-led; STAR is more flexible and works for both resumes and behavioral interviews. Use XYZ for technical and quantifiable resume bullets where you have real numbers. Use STAR when the context matters more, when you don't have a clean metric, or when you're prepping for a behavioral interview.
Yes. No signup, no email capture, no paywall on the working tool. Anonymous users get 3 generations per IP per day; logged-in free users get 10/day; paid users are unlimited. Most students never hit the cap.
Yes — though it leans tech. Engineering, data, product, and design resumes use XYZ heavily because metrics tend to be available (latency, conversion, users, throughput). For consulting, healthcare, education, and humanities work, the format works when you have a real number; otherwise STAR or CAR is more flexible.
Paste a JD, upload your resume, and we'll rewrite every weak bullet with proper outcome-first phrasing, score the keyword match, list what's missing, and write the cover letter — usually under fifteen seconds. Your first one is free.
Related methods