Design Google Docs
Let many people edit the same document at once and see each other’s changes and cursors live, like Google Docs.
Functional requirements
- Create and edit rich-text documents
- Many people edit at the same time
- Version history and comments
Non-functional requirements
- Edits appear to others in under 200 ms
- Everyone ends up with the same document
- No edits lost after a brief disconnect
Scale
- 1B documents
- Up to 100 simultaneous editors per document
- Millions of concurrent editing sessions
How you’ll be scored
10 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 Google Docs”, that starts with: Create and edit rich-text documents; Many people edit at the same time; Version history and comments. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (1B documents; Up to 100 simultaneous editors per document; Millions of concurrent editing sessions) 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: Edits appear to others in under 200 ms; Everyone ends up with the same document; No edits lost after a brief disconnect. 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 collaboration, ot / crdt and real-time 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.