Limited Time Offer:Up to 20% off Hello Interview Premium
Up to 20% off Hello Interview Premium 🎉
Hello Interview
Learn System Design
Introduction
How to Prepare
Delivery Framework
Core Concepts
Key Technologies
Common Patterns
Question Breakdowns
Networking Essentials
API Design
Data Modeling
Caching
Sharding
Consistent Hashing
CAP Theorem
Database Indexing
Numbers to Know
Bitly
Dropbox
Local Delivery Service
Ticketmaster
FB News Feed
Tinder
LeetCode
WhatsApp
Rate Limiter
FB Live Comments
FB Post Search
YouTube Top K
Uber
YouTube
Web Crawler
Ad Click Aggregator
News Aggregator
Yelp
Strava
Online Auction
Price Tracking Service
Instagram
Robinhood
Google Docs
Distributed Cache
Job Scheduler
Payment System
Metrics Monitoring
ChatGPT
Real-time Updates
Dealing with Contention
Multi-step Processes
Scaling Reads
Scaling Writes
Handling Large Blobs
Managing Long Running Tasks
Redis
Elasticsearch
Kafka
API Gateway
Cassandra
DynamoDB
PostgreSQL
Flink
ZooKeeper
Time Series Databases
Data Structures for Big Data
Vector Databases
Vote For New Content
Pricing
Sign in / Sign up
Search
⌘K
Pricing

Tutor

Common Problems

Google Docs

Real-time Updates
Published
ByStefan Mai·
hard

Try This Problem Yourself

Practice with guided hints and real-time feedback

Premium users can view this video once signed in

Understanding the Problem

📄 What is Google Docs? Google Docs is a browser-based collaborative document editor. Users can create rich text documents and collaborate with others in real-time.
In this writeup we'll design a system that supports the core functionality of Google Docs, dipping into websockets and collaborative editing systems. We'll start with the requirements (like a real interview), then move on to complete the design following our Delivery Framework.

Functional Requirements

Core Requirements
  1. Users should be able to create new documents.
  2. Multiple users should be able to edit the same document concurrently.
  3. Users should be able to view each other's changes in real-time.
  4. Users should be able to see the cursor position and presence of other users.
Below the line (out of scope)
  1. Sophisticated document structure. We'll assume a simple text editor.
  2. Permissions and collaboration levels (e.g. who has access to a document).
  3. Document history and versioning.

Non-Functional Requirements

Set Up

Planning the Approach

Defining the Core Entities

Defining the API

High-Level Design

1) Users should be able to create new documents.

2) Multiple users should be able to edit the same document concurrently.

Collaborative Edits Breakdown

3) Users should be able to view each other's changes in real-time.

When the Document is Loaded

When Updates Happen

4) Users should be able to see the cursor position and presence of other users.

Potential Deep Dives

1) How do we scale to millions of websocket connections?

2) How do we keep storage under control?

Some additional deep dives you might consider

What is Expected at Each Level?

Mid-level

Senior

Staff

References

Purchase Premium to Keep Reading

Unlock this article and so much more with Hello Interview Premium
Buy Premium

Currently up to 20% off

Hello Interview Premium

System Design Guided Practice
Exclusive content
Recent interview questions
Learn More
Reading Progress

On This Page

Understanding the Problem

Functional Requirements

Non-Functional Requirements

Set Up

Planning the Approach

Defining the Core Entities

Defining the API

High-Level Design

1) Users should be able to create new documents.

2) Multiple users should be able to edit the same document concurrently.

3) Users should be able to view each other's changes in real-time.

4) Users should be able to see the cursor position and presence of other users.

Potential Deep Dives

1) How do we scale to millions of websocket connections?

2) How do we keep storage under control?

Some additional deep dives you might consider

What is Expected at Each Level?

Mid-level

Senior

Staff

References

Questions
Meta SWE Interview QuestionsAmazon SWE Interview QuestionsGoogle SWE Interview QuestionsOpenAI SWE Interview QuestionsEngineering Manager (EM) Interview Questions
Learn
Learn System DesignLearn DSALearn BehavioralLearn ML System DesignLearn Low Level DesignGuided Practice
Links
FAQPricingGift PremiumHello Interview Premium
Legal
Terms and ConditionsPrivacy PolicySecurity
Contact
About UsProduct Support

7511 Greenwood Ave North Unit #4238 Seattle WA 98103


© 2026 Optick Labs Inc. All rights reserved.