##### Question Estimate how much data YouTube streams to users worldwide in a typical 24-hour period. Walk through your assumptions, calculations, and sanity checks; then present the final estimate. ##### Hints Think about average watch time, video bitrates, and daily active users; clearly state each assumption before using it.

Practice a YouTube daily data throughput Fermi estimate using daily users, watch time, average bitrate, overhead, unit conversions, sensitivity analysis, sanity checks, and a final exabytes-per-day range.

How do I approach Product / Decision Making interview questions?

Product / Decision Making questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master product / decision making interviews.

What difficulty level is this interview question?

This is a medium difficulty Product / Decision Making question, commonly asked during Technical Screen rounds at Google.

What role is this question designed for?

This question is commonly asked for Product Manager candidates at Google during technical interviews.

YouTube Data Throughput Estimation | Google Interview Question

Estimation Challenge: YouTube Daily Data Streamed

Estimate how much data YouTube streams to users worldwide in a typical 24-hour period. Walk through assumptions, calculations, sanity checks, and a final point estimate with a plausible range.

Constraints & Assumptions

Treat this as a Fermi estimate; the goal is structured reasoning, not exact public reporting.
State each assumption before using it.
Use daily active users, average watch time, average bitrate, and overhead as the main drivers.
Distinguish data delivered to end users from internal CDN or backbone traffic.

Clarifying Questions to Ask

Should I estimate all YouTube surfaces, including Shorts, TV, music videos, ads, and livestreams?
Are offline downloads included on the day they are downloaded?
Should I count only user-delivered bytes or also internal replication and CDN fill traffic?
Should I use decimal exabytes or binary exbibytes?

Part 1 - Build the Model

Define the formula and the core variables.

What This Part Should Cover

Daily active users.
Average watch time per active user.
Weighted average bitrate across resolution, device, codec, and content type.
Protocol, retransmission, thumbnail, and ad overhead if included.

Part 2 - Calculate a Base Case

Use reasonable assumptions to compute a central estimate.

What This Part Should Cover

Unit conversions from users to hours, seconds, bits, bytes, terabytes, petabytes, and exabytes.
A transparent arithmetic path that is easy to audit.
A clear point estimate.

Part 3 - Sensitivity and Sanity Checks

Bracket the estimate with low and high cases, then sanity-check the result.

What This Part Should Cover

Sensitivity to users, watch time, and bitrate.
Comparison to known-scale intuition such as billions of watch hours and video dominating consumer internet traffic.
Discussion of adaptive bitrate, mobile versus TV, Shorts, 4K, ads, caching, and downloads.

What a Strong Answer Covers

Clean assumptions and correct unit handling.
A plausible range, not false precision.
Explicit treatment of what is counted and what is excluded.
Sanity checks that show whether the answer is in the right order of magnitude.

Follow-up Questions

Which assumption matters most?
How would the estimate change if TV watch time doubled?
How would AV1 adoption change the answer?
Does CDN caching reduce the number you report?
What data would you ask YouTube's analytics team for to improve the estimate?

Estimation Challenge: YouTube Daily Data Streamed

Estimate how much data YouTube streams to users worldwide in a typical 24-hour period. Walk through assumptions, calculations, sanity checks, and a final point estimate with a plausible range.

Constraints & Assumptions

Treat this as a Fermi estimate; the goal is structured reasoning, not exact public reporting.
State each assumption before using it.
Use daily active users, average watch time, average bitrate, and overhead as the main drivers.
Distinguish data delivered to end users from internal CDN or backbone traffic.

Clarifying Questions to Ask

Should I estimate all YouTube surfaces, including Shorts, TV, music videos, ads, and livestreams?
Are offline downloads included on the day they are downloaded?
Should I count only user-delivered bytes or also internal replication and CDN fill traffic?
Should I use decimal exabytes or binary exbibytes?

Part 1 - Build the Model

Define the formula and the core variables.

What This Part Should Cover

Daily active users.
Average watch time per active user.
Weighted average bitrate across resolution, device, codec, and content type.
Protocol, retransmission, thumbnail, and ad overhead if included.

Part 2 - Calculate a Base Case

Use reasonable assumptions to compute a central estimate.

What This Part Should Cover

Unit conversions from users to hours, seconds, bits, bytes, terabytes, petabytes, and exabytes.
A transparent arithmetic path that is easy to audit.
A clear point estimate.

Part 3 - Sensitivity and Sanity Checks

Bracket the estimate with low and high cases, then sanity-check the result.

What This Part Should Cover

Sensitivity to users, watch time, and bitrate.
Comparison to known-scale intuition such as billions of watch hours and video dominating consumer internet traffic.
Discussion of adaptive bitrate, mobile versus TV, Shorts, 4K, ads, caching, and downloads.

What a Strong Answer Covers

Clean assumptions and correct unit handling.
A plausible range, not false precision.
Explicit treatment of what is counted and what is excluded.
Sanity checks that show whether the answer is in the right order of magnitude.

Follow-up Questions

Which assumption matters most?
How would the estimate change if TV watch time doubled?
How would AV1 adoption change the answer?
Does CDN caching reduce the number you report?
What data would you ask YouTube's analytics team for to improve the estimate?

YouTube Data Throughput Estimation

Quick Overview

YouTube Data Throughput Estimation

Estimation Challenge: YouTube Daily Data Streamed

Constraints & Assumptions

Clarifying Questions to Ask

Part 1 - Build the Model

What This Part Should Cover

Part 2 - Calculate a Base Case

What This Part Should Cover

Part 3 - Sensitivity and Sanity Checks

What This Part Should Cover

What a Strong Answer Covers

Follow-up Questions

Write your answer

YouTube Data Throughput Estimation

Quick Overview

YouTube Data Throughput Estimation

Estimation Challenge: YouTube Daily Data Streamed

Constraints & Assumptions

Clarifying Questions to Ask

Part 1 - Build the Model

What This Part Should Cover

Part 2 - Calculate a Base Case

What This Part Should Cover

Part 3 - Sensitivity and Sanity Checks

What This Part Should Cover

What a Strong Answer Covers

Follow-up Questions

Write your answer