ScaleCrafts

Design Zoom

HardWebRTCMedia serversLow latency

Host video meetings with many participants, screen sharing and chat, like Zoom or Google Meet.

Functional requirements

  • Start and join meetings by link
  • Audio, video and screen sharing
  • In-meeting chat and participant list

Non-functional requirements

  • Under 200 ms mouth-to-ear latency
  • Calls adapt to poor networks
  • Meetings of up to 1,000 people

Scale

  • 300M daily meeting participants
  • Five people in an average meeting
  • Media traffic dwarfs everything else

How you’ll be scored

9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works

What interviewers look for

  • Clarify before you draw. State what is in and out of scope. For “Design Zoom”, that starts with: Start and join meetings by link; Audio, video and screen sharing; In-meeting chat and participant list. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (300M daily meeting participants; Five people in an average meeting; Media traffic dwarfs everything else) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
  • Show how each quality is met. Your design should visibly deliver: Under 200 ms mouth-to-ear latency; Calls adapt to poor networks; Meetings of up to 1,000 people. Saying that it does isn’t enough; point to the part of the design that makes it true.
  • Expect follow-ups on the hard parts. Interviewers usually probe webrtc, media servers and low latency here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
  • Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.

Related problems

Loading your workspace…