Google·Product Manager·Onsite - Product Sense / Strategy·Intermediate

Intermediate

May 2026

Summary

Google PM interview with a single estimation question about traffic and lost productivity. Pretty classic fermi problem but it has a few moving parts that can trip you up if you're not careful about your assumptions.

Questions Asked (1)

Estimate the total number of productivity hours lost per year due to traffic congestion.

Product Analytics & MetricsAdaptability & Ambiguity

Author's notes

I started by trying to scope it geographically and immediately second-guessed myself on whether to do US-only or global.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Break down the problem into a demand-side equation: total hours lost = number of commuters × average commute time × congestion delay factor × working days per year. Then segment the population by geography (urban vs. rural) and mode of transport to refine estimates, and validate with top-down data like total vehicle miles traveled and average speed reduction.

Pro tip: State your assumptions clearly and round numbers to simplify calculations; interviewers care more about your structured thinking than precise arithmetic. Also, mention that you'd validate with real-world data sources like INRIX or TomTom traffic indices if available.

1. Clarify the scope

Ask whether the estimate is for a specific country (e.g., US) or global, and whether it includes all modes of transport or just car commuters. This narrows the problem and shows you avoid ambiguity.

2. Define the equation

Set up a formula: Total lost hours = (Number of affected commuters) × (Average one-way commute time) × (Congestion delay percentage) × (2 for round trip) × (Working days per year).

3. Estimate each variable

Use round numbers: e.g., for the US, assume 150 million workers, 75% commute by car, average commute 30 minutes, congestion adds 30% delay, 250 working days. Calculate step by step.

4. Sanity-check and refine

Compare your result to known data (e.g., INRIX reports Americans lose ~99 hours/year to congestion). Adjust assumptions if needed and discuss potential over/underestimates.

5. Summarize and interpret

Present the final estimate, highlight key drivers, and suggest how a product manager might use this insight (e.g., for a navigation app feature).

Key Points to Mention

Segment the population by urban vs. rural and by commute mode (car, public transit, etc.) to improve accuracy.
Use a top-down approach: start with total workforce, then apply filters for commuters and congestion-affected trips.
Incorporate a congestion delay factor (e.g., 30-40% extra time) based on average peak-hour traffic.
Account for working days per year (e.g., 250) and vacation/holidays.
Validate with external benchmarks like TomTom Traffic Index or INRIX reports.
Discuss limitations: not all commuters face congestion, some work remotely, and hours lost may not be purely 'productivity' if commuters adjust schedules.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.