Mock system design interview at Netflix
A live 45-minute round on a question reported in Netflix interviews, run by an AI interviewer that asks one thing at a time, probes what you say, looks at your whiteboard, and weighs what that round is reported to weigh. It ends with a debrief: a score, what was strong, what was missing.
Design YouTube
Upload, transcode, and stream video to a billion viewers: a processing pipeline on one side, a CDN problem on the other.
You will not see the requirements, the numbers or the design before you start. That is the point.
What the Netflix round is reported to look like
45–60 minutes, often on streaming delivery, the data platform behind it, or a high-volume service such as search or ad events.
What it weighs
- Availability first: what keeps playing when a dependency fails
- Content delivery: CDN placement, caching and the cost of bytes moved
- Event pipelines at very high volume, and what has to be exact versus approximate
- Operating it: resilience testing, regional failover and observability
The common mistake
Spending the hour on the metadata service. The bytes, the CDN and what happens when a region goes down are what the interviewer wants to hear about.
From public interview guides and candidate reports, not from Netflix. The interviewer is an AI running in that style; it is practice, not a prediction.
Start the round
The interviewer’s opening question is free. Answering it is part of Pro.
Other companies: Anthropic · Google · Meta · Amazon · OpenAI · Microsoft · Uber · DoorDash