Stop Listing Duties: How to Quantify Your Impact Using the Google Formula

The Problem with 'Responsible For'

Most resumes suffer from a fatal flaw: they read like job descriptions, not performance reviews. Candidates tend to list their daily obligations rather than their achievements. You see lines like "Responsible for managing a team" or "Tasked with writing code for the frontend."

The problem? This tells a recruiter what you did, but not how well you did it. Did you manage the team into the ground, or did you lead them to record profits? Did your code crash the server, or did it speed up load times by 50%?

To stand out in a competitive market—especially in tech and engineering—you must pivot from qualitative descriptions to quantitative proofs.

The Laszlo Bock Formula

Laszlo Bock, the former SVP of People Operations at Google, coined a simple formula for writing resume bullet points that has become the gold standard in the industry. The formula is:

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

Let’s break this down:

• X: The specific outcome or impact you achieved.
• Y: The metric, number, or data point that proves the scale of the achievement.
• Z: The specific action, skill, or tool you used to make it happen.

Applying the Formula: Before and After

Let’s look at how this transformation works across different roles. The goal is to maximize information density while keeping the text readable.

Example 1: Software Engineer

Weak: "Wrote code for the new login page using React."

Strong: "Reduced user login time by 40% (X) as measured by server logs (Y), by refactoring the authentication flow using React hooks and OAuth 2.0 (Z)."

Example 2: Marketing Manager

Weak: "Managed the company Twitter account and grew followers."

Strong: "Increased social media engagement by 200% (X) in Q3, adding 5,000+ organic followers (Y) by implementing a data-driven content calendar and A/B testing ad copy (Z)."

Example 3: Medical Student / Intern

Weak: "Helped doctors with patient history and rounds."

Strong: "Improved patient intake efficiency by 15% (X) across the ward, processing 20+ patients daily (Y), by digitizing history logs and standardizing the triage checklist (Z)."

Finding Your Metrics (When You Don't Have Data)

A common objection is, "I don't have access to the exact numbers." If you don't have the hard data, you can use estimates or proxy metrics. The key is to be honest but descriptive.

• Frequency: How often did you do the task? (e.g., "Drafted 10+ reports weekly...")
• Scale: How big was the team or budget? (e.g., "Managed a budget of $10k...")
• Speed: Did you do it faster than before? (e.g., "Cut reporting time in half...")
• Range: Who did it affect? (e.g., "Servicing 500+ active clients...")

The 'So What?' Test

Before you finalize a bullet point on ImpresCV, ask yourself "So what?"

You utilized Python? So what? So that we could automate the data entry.

You automated data entry? So what? So that the team saved 20 hours of manual work per week.

That final answer is your bullet point: "Saved 20 hours of manual work per week by building a Python automation script for data entry."

Conclusion

Recruiters spend an average of 6 to 7 seconds scanning a resume. Numbers catch the eye. They break up the wall of text and provide immediate context. By systematically applying the Laszlo Bock formula to your resume, you move from being a candidate who "did the job" to a candidate who "delivered results."