QuorumWiki
Jugar
Guías prácticas

Preguntas de entrevista de diseño de sistemas

Diecinueve preguntas comunes de entrevista de diseño de sistemas, la mayoría del System Design Primer, cada una con requisitos, una estimación de carga, un diseño, lo que se rompe y qué construir en el juego.

The first fourteen questions come from the 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.

QuestionThe idea it teaches
Design a URL shortener or PastebinUnique keys, and a read-heavy workload served from a cache
Design a news feed or Twitter timelineFan-out on write versus fan-out on read
Design a web crawlerQueues, politeness, and deduplicating a huge frontier
Design Mint.comSyncing accounts and batch reports off the main database
Design the data structures for a social networkSharding a graph and finding paths between people
Design a key-value store for a search engineCaching queries with LRU, sharding, and invalidation
Design Amazon's sales ranking by categoryAggregating events into precomputed top lists
Design a system that scales to millions of usersThe ladder from one box to sharded data
Design a file sync service like DropboxChunking, metadata, and sync
Design a search engine like GoogleCrawl, inverted index, and sharded serving
Design a key-value store like Redis or DynamoPartitioning, replication, and quorums
Design a cache system like MemcachedEviction, hashing across nodes, and stampedes
Design a chat app like WhatsAppLong-lived connections and message ordering
Design a content delivery network like CloudflareEdge caches, routing, and origin shielding
Design a rate limiterCounting requests fairly across many servers
Design a notification systemQueues, retries, and idempotent delivery
Design a payment systemNever charging twice when everything retries
Design a video streaming serviceUpload pipelines, object storage, and CDNs
Design a ticket booking systemHolding scarce inventory under a flash sale

If a question uses a term you do not know, System design concepts groups every idea by the problem it solves. If you are starting from nothing, Learn system design by playing 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.