Estimation Prompt: Annual Hours Lost to Traffic in the United States
Estimate the total number of hours that drivers in the United States collectively spend stuck in traffic each year.
Provide:
-
A clear definition of "stuck in traffic," such as delay relative to free-flow conditions.
-
Stated assumptions and data splits, such as urban versus rural or metro size.
-
Key data points you estimate or use.
-
An end-to-end calculation and brief sanity check.
Constraints & Assumptions
-
Use a Fermi estimation approach rather than trying to recall exact traffic-study numbers.
-
Define whether you include passenger vehicles only or all vehicles.
-
Avoid double counting drivers and passengers unless you explicitly estimate person-hours.
-
Give a central estimate and reasonable range.
Clarifying Questions to Ask
-
Should the estimate be driver-hours or person-hours?
-
Should freight, taxis, rideshare, buses, and delivery vehicles be included?
-
Are we measuring delay versus free-flow conditions or all time in slow traffic?
-
Should we include non-recurring delays such as crashes and weather?
Part 1 - Define the Metric and Segments
Define the metric and segment the driving population.
What This Part Should Cover
-
Delay time relative to free-flow travel.
-
Passenger-vehicle driver-hours unless otherwise stated.
-
Segments such as large metros, other urban/suburban areas, and rural areas.
-
Rationale for different delay assumptions.
Part 2 - Calculation
Estimate drivers and annual delay per driver by segment, then sum.
What This Part Should Cover
-
U.S. licensed drivers or active drivers.
-
Segment shares.
-
Annual delay assumptions.
-
Multiplication and total.
-
Central estimate and range.
Part 3 - Sanity Check
Provide a sanity check and identify key sensitivities.
What This Part Should Cover
-
Average delay per driver.
-
Comparison to monthly or weekly experience.
-
Sensitivity to metro share and annual delay assumptions.
-
Alternative approach using commute days and daily delay.
What a Strong Answer Covers
A strong answer is structured, transparent, and easy to adjust. It defines the metric, segments drivers by congestion exposure, calculates cleanly, and sanity-checks the result.
Follow-up Questions
-
What assumption matters most?
-
How would the estimate change if using person-hours instead of driver-hours?
-
How would remote work change the estimate?
-
How would you estimate economic cost from the hours?
-
How would you validate the estimate after the interview?