Netflix

39 design problems known to be asked at Netflix.

Easy3

Easylow level design design patterns oop

Facade Pattern: One Door Into a Room Full of Machinery

When 'place an order' means orchestrating inventory, payment, shipping, and notifications — every caller re-learns the whole subsystem. A Facade gives them one door, and leaves the machinery open for anyone who still needs it.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·14 min read

Easylow level design design patterns oop

Iterator Pattern: Walk a Collection Without Knowing Its Shape

Every for-each loop you've ever written is the Iterator pattern in disguise. Here's how one hasNext()/next() surface lets you traverse an array, a tree, or an unbounded paged API the exact same way — and why mutating mid-loop blows up.

Asked at Amazon, Google, Microsoft +2

Aug 8, 2026·16 min read

Easylow level design design patterns oop

Template Method: Freeze the Recipe, Swap the Ingredients

When CSV, JSON, and XML importers all do the same four steps in the same order but differ in two of them, three near-identical pipelines is the smell. Template Method puts the order in one place and lets subclasses fill only the steps that vary.

Asked at Amazon, Google, Microsoft +2

Aug 8, 2026·15 min read

Medium28

Mediumhigh level design distributed systems microservices

The API Gateway: One Front Door for a Hundred Services

When a mobile screen fires a dozen calls to a dozen services, each doing its own auth and its own CORS, the answer isn't a smarter client — it's a single entry point that owns the cross-cutting concerns once.

Asked at Netflix, Amazon, Uber +2

Aug 8, 2026·15 min read

Mediumlow level design design patterns oop

Behavioral Patterns: How Objects Talk and Decide

The eleven behavioral patterns aren't eleven tricks — they're eleven answers to one question: when responsibility and communication are tangled inside a class, which one do you pull out, and where does it go? A map, not a re-teach.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·8 min read

Mediumhigh level design distributed systems data structures

Bloom Filters: The Yes/No That Saves a Disk Seek

A tiny bit-array that answers 'definitely not here' or 'maybe here' in constant time — how Cassandra, HBase, and Chrome skip millions of expensive lookups for keys that were never there.

Asked at Google, Amazon, Meta +3

Aug 8, 2026·12 min read

Mediumhigh level design distributed systems caching

Caching Strategies: The Bet That Reads Repeat

A cache is a wager that the same data gets read again before it changes. Get the read/write pattern, the eviction policy, and — the hard part — invalidation right, and one box absorbs the load that would have flattened your database.

Asked at Meta, Amazon, Netflix +3

Aug 8, 2026·13 min read

Mediumhigh level design distributed systems consistency

CAP Theorem: The Choice You Only Make When the Network Breaks

Everyone quotes 'pick 2 of 3' and everyone is wrong. CAP is a decision forced only during a partition — and PACELC is the sharper lens for the 99.9% of the time when the network is fine.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·12 min read

Mediumhigh level design distributed systems networking

CDNs: Move the Bytes to the User, Not the User to the Bytes

A user in Sydney pays ~200ms to reach a Virginia origin before any work happens — physics you can't code around. This is how CDNs cheat the speed of light with edge PoPs, anycast routing, and HTTP caching.

Asked at Cloudflare, Akamai, Fastly +3

Aug 8, 2026·16 min read

Mediumlow level design design patterns oop

Chain of Responsibility: Let the Request Find Its Own Handler

Why the sender of a request should never hard-code who processes it — and how linking handlers into a chain turns a brittle escalation switch into the reorderable pipeline behind every middleware stack.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·15 min read

Mediumlow level design design patterns oop

Command Pattern: Make a Request Something You Can Hold in Your Hand

A method call happens once and is gone. Turn that request into an object with execute() and undo(), and suddenly you can queue it, log it, retry it, and reverse it — the backbone of undo/redo, job queues, and transactional replay.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·15 min read

Mediumlow level design design patterns oop

Composite Pattern: One size() Call for a File or Ten Thousand

When your data is a tree — files and folders, elements and containers, parts and assemblies — the Composite pattern lets client code treat a single leaf and a whole subtree with the exact same call. The recursion hides inside the tree, not in your if-statements.

Asked at Amazon, Google, Microsoft +2

Aug 8, 2026·15 min read

Mediumlow level design design patterns oop

Creational Patterns: Who Decides What Gets Built

The five creational patterns aren't five clever tricks — they're five answers to one question: how does an object come into existence without the code that uses it hard-wiring the code that makes it? A map, and one interactive way to pick the right one.

Asked at Amazon, Google, Microsoft +3

Jul 28, 2026·5 min read

Mediumhigh level design distributed systems databases

Database Indexing: Why B-Trees Read Fast and LSM-Trees Write Fast

A missing index turns a one-user lookup into a scan of fifty million rows. Here's how the two great index families — B+ trees and LSM-trees — buy that lookup back, and what each one charges you for it.

Asked at Amazon, Google, Meta +3

Aug 8, 2026·13 min read

Mediumhigh level design distributed systems databases

Database Replication: Copies That Disagree With Each Other

Why the same query returns different answers on two servers a second apart — and the failover, lag, and conflict traps that turn 'just add a read replica' into a 3am incident.

Asked at Amazon, Google, Meta +3

Aug 8, 2026·15 min read

Mediumlow level design design patterns oop

Decorator Pattern: Stack Behavior at Runtime Without a Subclass Bomb

You need buffering, then compression, then encryption — in any combination. Subclassing that gives you BufferedEncryptedCompressedInputStream. The Decorator pattern lets you wrap those responsibilities on one object at a time instead.

Asked at Amazon, Google, Microsoft +2

Aug 8, 2026·14 min read

Mediumlow level design oop design principles

Dependency Inversion: Point the Arrow at an Abstraction

A service that news-up its own email sender can't be tested or swapped. Dependency Inversion flips the arrow so high-level policy and low-level detail both depend on an abstraction.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·8 min read

Mediumhigh level design distributed systems reliability

Idempotency: How to Retry a Payment Without Charging Twice

The network fails after your server does the work but before the answer gets home, so the client retries — and a naive charge endpoint bills the card twice. Idempotency is the discipline that makes every retry safe.

Asked at Stripe, Amazon, PayPal +3

Aug 8, 2026·15 min read

Mediumlow level design oop design principles

Interface Segregation: Don't Make Callers Depend on What They Don't Use

One fat Notifier interface forces every channel to stub methods it can't support and every caller to depend on methods it never calls. Interface Segregation splits it into roles.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·7 min read

Mediumhigh level design distributed systems networking

Load Balancing: One Front Door for a Fleet That Keeps Changing

A single server melts under Black-Friday traffic. Load balancing is how you put ten servers behind one address — and the L4-vs-L7 choice, the routing algorithm, and the health checks are where systems live or die.

Asked at Amazon, Google, Netflix +3

Aug 8, 2026·16 min read

Mediumlow level design oop design principles

Liskov Substitution: If Clients Must Check the Type, You Broke It

An SmsChannel that can't do what a Channel promised isn't a safe stand-in for its base — so callers start type-checking. Liskov, explained simply: a subtype must work anywhere its parent does.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·8 min read

Mediumhigh level design distributed systems messaging

Message Queues & Event Streaming: Stop Making Users Wait for Work They Don't Care About

A checkout that emails, bills, and updates inventory before it answers is one flaky partner away from a timeout. How queues and logs let producers and consumers stop holding each other hostage.

Asked at Amazon, LinkedIn, Netflix +3

Aug 8, 2026·17 min read

Mediumlow level design design patterns oop

Observer Pattern: Broadcast State Without Knowing Who's Listening

When one object changes and an unknown, shifting crowd must react, wiring the subject to each dependent is a maintenance trap. Observer inverts it — dependents subscribe, the subject just broadcasts.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·15 min read

Mediumlow level design oop design principles

Open/Closed: Add a Channel Without Touching the Core

Every new notification channel meant another edit to the same switch — and another regression. Open/Closed makes new behavior a drop-in, not a rewrite.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·7 min read

Mediumlow level design design patterns oop

Proxy Pattern: The Stand-In Your Code Can't Tell Apart

The @Transactional annotation on your service method does nothing on its own — a proxy quietly wrapping the bean is what makes it work. Understand that stand-in and half of Spring's magic stops being magic.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·14 min read

Mediumhigh level design distributed systems networking

Real-Time Updates: Polling, Long Polling, SSE, and WebSockets

HTTP can't push — the server only answers when asked. Here's the ladder of techniques that fake or fix that, each one solving the last one's flaw, and the fan-out problem that breaks all of them at scale.

Asked at Slack, Discord, WhatsApp +3

Aug 8, 2026·16 min read

Mediumlow level design oop design principles

SOLID, Actually: Five Rules for Code That Survives Change

SOLID isn't five unrelated rules — it's one idea about managing dependencies and change. Watch one messy NotificationService become clean, one principle at a time.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·4 min read

Mediumhigh level design distributed systems databases

SQL vs NoSQL: Model the Access Pattern, Then Pick the Store

The choice isn't a religion — it's a consequence. Design how your data is read and written first, and the datastore that fits falls out of it. Pick the store first and you'll hand-join in application code for the next three years.

Asked at Amazon, Google, Netflix +3

Aug 8, 2026·15 min read

Mediumlow level design oop design principles

Single Responsibility: One Reason to Change, One Owner

SRP isn't 'do one thing' — it's 'answer to one actor'. Watch a Marketing copy tweak break Compliance's audit log, then split one NotificationService by who owns each change.

Asked at Amazon, Google, Microsoft +3

Jul 27, 2026·7 min read

Mediumlow level design design patterns oop

State Pattern: Make Illegal Transitions Impossible

An order that can be paid, shipped, delivered, or cancelled grows a switch(status) block in every method — until one of them forgets an arm and a shipped order gets refunded. The State pattern moves both behavior and the legal next-steps into the state itself.

Asked at Amazon, Google, Microsoft +2

Aug 8, 2026·16 min read

Mediumlow level design design patterns oop

Structural Patterns: Composing Objects Into Bigger Things

The seven structural patterns aren't seven clever tricks — they're seven answers to one question: how do you compose classes and objects into larger structures without the composition itself going rigid? A map, and how to tell the confusing ones apart.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·8 min read

Hard8

Hardlow level design design patterns oop

Bridge Pattern: When Two Things Vary, Stop Multiplying Them

Shape × Renderer, Remote × Device, Notification × Transport — the moment two dimensions vary independently, inheritance breeds a class explosion. Bridge splits the hierarchy so each axis grows on its own.

Asked at Amazon, Google, Microsoft +3

Aug 8, 2026·14 min read

Hardhigh level design distributed systems consensus

Consensus & Leader Election: How a Cluster Agrees on One Truth

Split-brain corrupts data quietly. This is how Raft gets N crash-prone nodes to agree on a leader, a log, and a lock — and why a majority is the only quorum that can't lie to itself.

Asked at Google, Amazon, Microsoft +3

Aug 8, 2026·17 min read

Hardhigh level design distributed systems databases

Database Sharding: When One Machine Stops Being Enough

Your 4 TB users table no longer fits — or no longer keeps up with writes — on a single node. Sharding is the answer, and the shard key you pick quietly decides everything that follows.

Asked at Amazon, Google, Meta +3

Aug 8, 2026·16 min read

Hardhigh level design distributed systems transactions

Distributed Transactions: When One Business Action Spans Many Services

The payment succeeded but the inventory reservation failed — and there's no ROLLBACK that spans both. How 2PC, Sagas, and the Outbox pattern give you atomicity when a single ACID transaction is no longer on the table.

Asked at Amazon, Uber, DoorDash +3

Aug 8, 2026·17 min read

Hardlow level design design patterns oop

Interpreter Pattern: When Your Config Grows a Grammar

Feature-flag rules, search filters, and pricing conditions all quietly become little languages. The Interpreter pattern turns that grammar into a tree of classes that evaluate themselves — and tells you exactly when to stop and reach for a real parser instead.

Asked at Google, Amazon, Microsoft +2

Aug 8, 2026·15 min read

Hardsystem design interview databases algorithms concurrency

Design a Key-Value Store

The capstone that ties the whole series together: consistent hashing to place data, quorums to tune consistency, vector clocks to detect conflicts, and hinted handoff to stay writable through failure. This is Amazon's Dynamo, rebuilt from its four moving parts.

Asked at Amazon, Netflix, Uber +2

Aug 9, 2026·23 min read

Hardhigh level design distributed systems consensus

Raft, Driven: Watch a Cluster Elect, Replicate, and Heal

Everyone can recite 'Raft elects a leader by majority.' The hard part is the log — how a follower that missed writes during a partition gets repaired, and the one subtle rule that stops a committed entry from ever being lost. Drive a live 5-node cluster, then take it apart.

Asked at Google, Amazon, Microsoft +4

Aug 9, 2026·20 min read

Hardhigh level design distributed systems databases storage

Storage Engines: LSM-Trees vs B-Trees

Every database makes one foundational choice — how to lay bytes on disk. B-trees update in place; LSM-trees never overwrite, they append and compact. That single decision sets your write throughput, read latency, and space usage. Drive an LSM write path — memtable, flush, compaction — and see the tradeoff for yourself.

Asked at Google, Meta, Amazon +3

Aug 9, 2026·14 min read