Engineering Manager interview
at Netflix.

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

1. 01 Apply the keeper test to your own team: tell me about someone you would fight hard to keep and someone you decided to let go, and how you reasoned through it.
2. 02 Describe how you build a 'dream team' of stunning colleagues and what you do when a well-liked engineer is no longer meeting the bar.
3. 03 Tell me about a time you gave your team context instead of control on a major project, and how you ensured autonomy scaled safely.
4. 04 Walk me through a leadership call you got wrong, what your judgment missed, and what you changed afterward.

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

1. 01 How do you set technical direction and guardrails (metrics, rollout plans, runbooks) so engineers can move fast autonomously without you in every decision?
2. 02 Describe how you'd lead an incident response and the post-incident culture you'd build around blamelessness and ownership.
3. 03 How do you evaluate whether a senior engineer's system-design proposal meets Netflix's bar, and how do you push back with candor?
4. 04 How would you drive adoption of chaos engineering and resilience practices across the services your team owns?

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

1. 01 Design the org and platform strategy to support migrating a monolith to resilient microservices for a global streaming service.
2. 02 Design how your team would build and operate a piece of the Open Connect CDN, including reliability, on-call, and capacity planning.
3. 03 Design the recommendation-ranking service ownership model, covering experimentation velocity, model rollout safety, and observability.
4. 04 Design a streaming-playback service from a managerial lens: how you'd staff it, set SLOs, and ensure it survives premiere-day traffic spikes.