Design Zoom
Real-time audio, video and screen share for 2 to 1,000 people per meeting, 300 M participants a day, under 150 ms mouth to ear.
One question on this site is reported in Zoom software engineer interviews. Each has a full reference design (requirements, back-of-envelope numbers, components, user flows and deep dives with interviewer follow-ups). Each one can be walked through turn by turn and then sat as a mock. Patterns covered: webrtc, sfu, real-time-media, congestion-control, multi-region.
Attribution comes from public interview guides and candidate reports, not from Zoom. It indicates where a question has been asked, nothing more.
Real-time audio, video and screen share for 2 to 1,000 people per meeting, 300 M participants a day, under 150 ms mouth to ear.
Large-company loops run 45 to 60 minutes, expect numbers, and spend most of the time on deep dives. Walk through a question to see how a strong candidate paces the hour, sit the same question as a mock until you can produce the requirements, the estimates and the design without looking, then read the interview framework guide for how to structure the hour. The other questions on the site teach patterns that show up in Zoom interviews under different names.
The question reported in Zoom system design interviews is Zoom. It tests webrtc, sfu, real time media, congestion control and multi region. The reports come from public interview guides and candidate accounts, not from Zoom, so practise the patterns rather than memorising one list.
Practise the questions reported there out loud, under a 45-minute clock: requirements with numbers first, then estimates, a high-level design, and deep dives into the two or three hardest parts. Start with Zoom: watch a strong candidate answer it turn by turn, then sit it yourself. Then cover the patterns the round leans on (webrtc, sfu, real time media and congestion control) with one more question each.