Software Engineer interview
at Netflix.

Tell-me-about-a-time stories on ownership, conflict, and impact — scored against this company's real values.

1. 01 Tell me about a time you acted like a senior owner under 'context, not control,' driving a project to completion without waiting for instructions or sign-off.
2. 02 Describe a moment you disagreed with a technical decision and used candor plus evidence to change the team's direction.
3. 03 Walk me through a production incident you owned end-to-end, including the trade-offs you made under pressure and what you'd do differently.
4. 04 Tell me about a time you raised the bar on quality or simplicity even though it slowed an in-flight project.

The hard screen for the craft itself — talked through out loud, not whiteboarded in your head.

1. 01 Design a thread-safe, concurrency-safe in-memory cache with TTL and eviction suitable for a high-throughput streaming service.
2. 02 Implement a rate limiter that protects a Netflix microservice from traffic spikes during a major show release.
3. 03 Given a graph of service dependencies, detect cycles and compute a safe deployment ordering for the microservices.
4. 04 How would you make a service resilient to downstream failures using timeouts, circuit breakers, fallbacks, and chaos-engineering principles?

Open-ended design of the systems this company actually runs, with the interviewer probing your tradeoffs.

1. 01 Design Netflix's end-to-end video streaming architecture, including adaptive bitrate streaming and the encoding pipeline.
2. 02 Design the Open Connect CDN, covering geographic partitioning, cache-fill strategies, peering, and monitoring cache-hit ratios.
3. 03 Design a system to absorb massive traffic spikes when a hit title premieres simultaneously worldwide.
4. 04 Design the playback service that selects the optimal Open Connect server and bitrate for each member's device and network conditions.