# System design interview questions

> Nineteen common system design interview questions, most from the System Design Primer, each with requirements, a load estimate, a design, what breaks, and what to build in the game.

The first fourteen questions come from the [System Design Primer](https://github.com/donnemartin/system-design-primer), the most widely used interview prep repository. Each page below answers one question the way a strong candidate would: it states the requirements, estimates the load, builds the design piece by piece, and names what breaks first. Each then shows what to place on the board in Quorum, so you can watch the failure instead of memorizing it.

| Question | The idea it teaches |
| --- | --- |
| [Design a URL shortener or Pastebin](https://wiki.playquorum.dev/guides/design-a-url-shortener.md) | Unique keys, and a read-heavy workload served from a cache |
| [Design a news feed or Twitter timeline](https://wiki.playquorum.dev/guides/design-a-news-feed.md) | Fan-out on write versus fan-out on read |
| [Design a web crawler](https://wiki.playquorum.dev/guides/design-a-web-crawler.md) | Queues, politeness, and deduplicating a huge frontier |
| [Design Mint.com](https://wiki.playquorum.dev/guides/design-mint-com.md) | Syncing accounts and batch reports off the main database |
| [Design the data structures for a social network](https://wiki.playquorum.dev/guides/design-a-social-network-graph.md) | Sharding a graph and finding paths between people |
| [Design a key-value store for a search engine](https://wiki.playquorum.dev/guides/design-a-query-cache.md) | Caching queries with LRU, sharding, and invalidation |
| [Design Amazon's sales ranking by category](https://wiki.playquorum.dev/guides/design-a-sales-rank.md) | Aggregating events into precomputed top lists |
| [Design a system that scales to millions of users](https://wiki.playquorum.dev/guides/design-a-system-for-millions-of-users.md) | The ladder from one box to sharded data |
| [Design a file sync service like Dropbox](https://wiki.playquorum.dev/guides/design-a-file-storage-service.md) | Chunking, metadata, and sync |
| [Design a search engine like Google](https://wiki.playquorum.dev/guides/design-a-search-engine.md) | Crawl, inverted index, and sharded serving |
| [Design a key-value store like Redis or Dynamo](https://wiki.playquorum.dev/guides/design-a-key-value-store.md) | Partitioning, replication, and quorums |
| [Design a cache system like Memcached](https://wiki.playquorum.dev/guides/design-a-cache-like-memcached.md) | Eviction, hashing across nodes, and stampedes |
| [Design a chat app like WhatsApp](https://wiki.playquorum.dev/guides/design-a-chat-system.md) | Long-lived connections and message ordering |
| [Design a content delivery network like Cloudflare](https://wiki.playquorum.dev/guides/design-a-cdn.md) | Edge caches, routing, and origin shielding |
| [Design a rate limiter](https://wiki.playquorum.dev/guides/design-a-rate-limiter.md) | Counting requests fairly across many servers |
| [Design a notification system](https://wiki.playquorum.dev/guides/design-a-notification-system.md) | Queues, retries, and idempotent delivery |
| [Design a payment system](https://wiki.playquorum.dev/guides/design-a-payment-system.md) | Never charging twice when everything retries |
| [Design a video streaming service](https://wiki.playquorum.dev/guides/design-a-video-streaming-service.md) | Upload pipelines, object storage, and CDNs |
| [Design a ticket booking system](https://wiki.playquorum.dev/guides/design-a-ticket-booking-system.md) | Holding scarce inventory under a flash sale |

If a question uses a term you do not know, [System design concepts](https://wiki.playquorum.dev/explanation/system-design-concepts.md) groups every idea by the problem it solves. If you are starting from nothing, [Learn system design by playing](https://wiki.playquorum.dev/tutorials/learn-system-design.md) gives an order.

## Common questions

### How do I approach a system design interview question?

Ask for the requirements first, estimate the load, sketch the simplest design that works, then find its first bottleneck and fix it. Each guide here follows that order, because the order is what interviewers watch for.

### What do interviewers look for in a system design answer?

They look for clear requirements, numbers that justify each choice, and an honest account of the tradeoffs. Naming a technology matters less than saying what it costs and when you would pick something else.

### Can a game really help with interview preparation?

It helps with the part that reading cannot teach, which is the order in which a system fails as load grows. Seeing a database saturate, then a cache absorb the reads, then the queue fill, gives you a feel for bottlenecks that a diagram does not.

Source: https://wiki.playquorum.dev/guides/system-design-interview-questions
