Google XYZ Resume Formula: Examples for State Job Applications

Google's published resume guidance describes the framework this way:

“Accomplished [X] as measured by [Y] by doing [Z].”^[1]

Former Google people-operations leader Laszlo Bock also explained the idea publicly in a widely shared post.^[2] It is a way to write bullets — not an official state requirement, a complete resume layout or a Google Docs template. CalHired is not affiliated with Google or the State of California.

The strongest strict XYZ bullets use a measured result. When no outcome metric exists, describe verifiable scope or a qualitative result honestly rather than implying something was measured. Keep in mind that scope (how many, how often) is not proof of improvement.

1. Choose a relevant responsibility. Start from the job's duty statement and pick work you've done that matches it. Don't copy duties as if they were accomplishments.
2. Identify the actual result or contribution. What was different because you did the work?
3. Find evidence in your own records. Reports, logs, schedules or confirmed feedback. Use only details you can explain in an interview, and never include confidential client or employee information.
4. Name the specific actions or tools you used. Be concrete: a checklist, a tracking spreadsheet, a new routing step.
5. Trim to one clear sentence and check facts and grammar. Natural variation is fine — don't start every bullet with “Accomplished” or force the same word order.

• Administrative (hypothetical)

  Before

  “Processed invoices.”

  After

  “Reduced average invoice turnaround from 5 to 3 business days over three months by introducing a completeness checklist and routing exceptions to the correct reviewer.”

  Why it works

  Strict XYZ: measured result, timeframe and method.

• Customer service (hypothetical)

  Before

  “Handled customer complaints.”

  After

  “Reduced average response time for escalated cases from 10 to 7 hours over one quarter by standardizing case notes and assigning follow-up owners.”

  Why it works

  Measures response time only. It does not claim cases were resolved faster.

• Training (hypothetical)

  Before

  “Trained new hires.”

  After

  “Shortened onboarding from 4 to 3 weeks for a 12-person new-hire group by creating role checklists and scheduling weekly practice sessions.”

  Why it works

  Measured change with group size as context.

• Operations / team project (hypothetical)

  Before

  “Helped with a reporting project.”

  After

  “Contributed to reducing weekly report preparation from 8 to 5 hours by building the team's data-validation checklist.”

  Why it works

  “Contributed to” makes clear it was a team result, not sole credit.

• Analyst / reporting (scope only) (hypothetical)

  Before

  “Made reports.”

  After

  “Consolidated data from 6 weekly reports into one exception summary by reconciling spreadsheet totals and flagging discrepancies for manager review.”

  Why it works

  Shows output and scope. It does not claim an efficiency gain that was never measured.

• Volunteer / early career (scope only) (hypothetical)

  Before

  “Helped at events.”

  After

  “Coordinated check-in for 80 attendees at a community workshop by organizing the roster and guiding volunteers through arrival procedures.”

  Why it works

  Scope, not improvement — and listed accurately as volunteer work.

Don't manufacture percentages. Instead, look for things you can verify: workload, frequency, team size, deadlines met, deliverables completed, or a process other people adopted.

If you don't know even the scope, a clear action plus its purpose is still useful:

“Created a shared handoff checklist so incoming staff could see open tasks and their owners.” (hypothetical)

This is a practical adaptation, not a fully measured XYZ result. “So incoming staff could see” states the purpose, not a verified impact.

If you approximate, base it on defensible records and say “approximately.” Don't estimate a change you can't support or invent a baseline, or claim “100% accuracy” without evidence. An honest, specific bullet is stronger than an inflated metric.

Caltrans recommends highlighting specific accomplishments and tailoring your resume to the duty statement.^[3] Before writing, read the posting and its required documents, including any page or file rules.^[5]

Each part of a state application package has its own job:

• Resume: highlights selected evidence — a good home for XYZ bullets.
• STD 678: documents the employment details the state requests, such as dates, hours and duties.
• SOQ (if required): answers its actual prompts.

Use the same facts, dates and titles across all of them, with different emphasis. A resume doesn't substitute for the STD 678 or a required SOQ. Don't reduce your STD 678 to short XYZ bullets and leave out the duties, hours or dates reviewers need to assess minimum qualifications.

Avoid state terms like “contract administration” or “budget analysis” unless your actual work supports them — describe transferable experience accurately instead.

Setting up your application for the first time? Read our guide to creating a CalCareers account and completing your STD 678.

Our practical baseline:^[4]

• A single column with common headings
• Consistent date formats and verb tense
• Your most relevant accomplishments placed prominently
• Selectable text, with no graphics replacing essential information

Follow the file type the posting requests; there's no universal one-page or PDF rule. Simpler formats can help people and software read your resume, but XYZ bullets alone don't guarantee screening results or an interview, and there's no universal keyword score. Use the job's terms only where they truthfully describe your work.

Copy this into your own document and fill it in privately. Nothing here is saved or sent anywhere.

Target duty: ___
X — result/contribution: ___
Y — verified evidence or scope (if known): ___
Z — my action/method: ___
Evidence source to check privately: ___
Draft: [Action/result] + [verified evidence/context] + by [specific method].

Before you use a bullet, check that:

• Any metric, baseline and timeframe is accurate
• It's clear whether the result was yours or the team's
• It shows a skill relevant to the job
• You can explain the example in an interview
• It agrees with your STD 678 and other application documents

Is XYZ a resume format?

No. XYZ is a framework for writing individual bullet points. It does not prescribe a resume layout, section order or template.^[1]

Do all resume bullets need numbers?

No. Use a measured result when you have one. Otherwise, describe truthful scope or a clear action and purpose. Never invent a figure to fit the formula.

Can I use XYZ in a state job application?

Yes, as a writing aid for your resume — subject to the actual posting instructions. It is not an official state requirement or endorsement, and it does not establish eligibility or guarantee an interview.^[3][5]

Does XYZ replace the STAR method?

Not exactly. XYZ is a compact resume bullet. STAR (situation, task, action, result) is a fuller narrative, useful when a prompt asks you to describe an example. For an SOQ, answer the prompt as written rather than forcing either format.