general

Netflix Interviews: The Culture Memo Is the Rubric

Netflix is the rare company whose interview prep starts with a document: the culture memo. Where other companies' values live on posters, Netflix's memo is operational (it describes how decisions get made, how feedback works, and who gets to stay) and interviewers test against it explicitly. Walking into a Netflix loop without having studied it is walking in without the rubric they're holding.

(For the systems side of the company, see our Netflix system design deep dive; this post is about the human loop.)

What the memo actually says

The memo has been rewritten several times since the original 2009 slide deck, but the themes that dominate interviews have been stable:

Candor. Feedback is direct, frequent, and expected in all directions. "Only say about someone what you'd say to their face" is treated as policy, not poetry. The memo also describes actively seeking out disagreement before a big decision (it calls this farming for dissent) and being open about your own mistakes.
Judgment over process. Netflix famously minimizes controls (no fixed vacation policy, "act in Netflix's best interest" as an expense policy) and expects context, not control: leaders set context; informed captains make calls without sign-off chains. The memo's phrase for the alternative is "people over process".
Freedom and responsibility. The freedom is real and so is the accountability; you own outcomes, not tasks. An informed captain who makes a bad call is expected to say so, loudly, so others learn from it.
The dream team and the keeper test. Managers ask themselves whether they would fight to keep a person who was about to leave for a similar role elsewhere. Netflix pays top of market and expects sustained excellence: "adequate performance gets a generous severance package" is a line that has appeared in the memo for years.

Read it as a description of how the company says it operates, and expect interviewers to ask you for evidence that you already work that way.

How that shapes the loop

Netflix hires experienced engineers almost exclusively, and the loop reflects that. The shape varies by team and changes over time, but a typical sequence looks like this:

Recruiter screen. Background and fit for a specific role; Netflix hires to a team, not to a pool.
Hiring manager conversation. Often early and substantive, because the hiring manager owns the decision at Netflix in a way a committee does elsewhere.
Technical screen. Anchored in your real work rather than puzzles: walk through a system you built, its trade-offs, and what you would change.
Onsite loop, usually a full day over video or on site. Deep technical rounds, a system design conversation at genuine scale, and culture conversations woven through every round, often with a director or VP taking one entirely. Partner-team engineers sometimes interview too, since you will work across teams.
References and decision. Reference checks are taken seriously, and the hiring manager makes the call with input from the panel.

On levels: Netflix historically kept a single senior engineer title for most individual contributors and has since moved toward more conventional levels. Ask the recruiter how the role is leveled and what the expectations are at that level, because the keeper test is applied against them.

What each round grades

Technical depth on your own work. Not whether you can solve a toy problem, but whether you understand the system you built better than anyone in the room.
System design at scale. Netflix operates at the scale where the standard answers stop working; interviewers want to hear you reason about the point where they break.
Judgment. Did you make calls without waiting for permission, and did you communicate context afterwards? Did you know when a decision was reversible and act accordingly?
Candor. Can you give and receive direct feedback, disagree in the open, and talk about your own mistakes without flinching? Interviewers often ask for the exact words you used, so prepare them.
Fit with the keeper test. The implicit question in every round is whether the manager would fight to keep you a year from now.

The questions you will actually get

Tell me about the hardest piece of feedback you've ever given. How did you deliver it?
Describe a decision you made against the consensus of your team. What happened?
Tell me about a time you were given a goal with no guidance at all.
What would your last team say is your weakness, and would you agree?
Where did you see something broken outside your remit? What did you do?
Walk me through the most complex system you own. What would you redo?
Tell me about a mistake you made that other people had to clean up. How did you handle it?
Describe a time you sought out disagreement before making a decision. Did it change the decision?
Tell me about a time you were given feedback you disagreed with.
How do you decide when a decision needs sign-off and when it does not?
What is a process at your current company you would delete, and why?
Why Netflix, and why now?

Notice the tilt: Amazon probes ownership, Meta probes impact, Netflix probes candor and judgment. The strongest possible signal is a story where you disagreed openly, decided as an informed captain, and owned the result either way.

Preparing

Read the memo, twice. It's public (jobs.netflix.com/culture). Annotate it against your own stories: for each theme, which experience of yours is evidence?
Build candor stories both ways. Feedback you gave that was hard, and feedback you received that changed you. Softened, diplomatic non-answers are themselves a negative signal here.
Prepare independent-judgment stories. Times you made the call without permission and communicated context afterwards. Structure them with STAR but let the decision reasoning take the airtime.
Prepare a mistake you own. Not a disguised strength. A real misjudgment, what it cost, what you said to whom, and what you changed.
Be ready to talk about your craft at depth. Rounds anchor in what you've actually built; rehearse explaining your most complex system (trade-offs, mistakes, what you'd redo) via a story bank and a mock interview or two.
Interview them back. Asking sharp questions about how context-not-control works on this team is both genuine diligence and exactly the behavior the memo predicts of a good hire. Good ones: how a recent disagreement on the team was settled, what the last decision was that someone made without asking, and what happened the last time the keeper test came out as a no.

How seniority changes the bar

Because Netflix hires senior people, the floor is high everywhere, but the emphasis shifts with the role. For an individual contributor the evidence is depth: systems you own end to end, decisions you made alone, and feedback you gave to peers. For a lead or manager the evidence is context-setting: how you briefed a team so they could decide without you, how you applied the keeper test honestly, and how you handled a strong performer who was wrong for the team. If you are moving into management, the engineering manager interview guide covers the general bar; at Netflix add the memo on top of it.

A four-week preparation plan

Week 1. Read the memo twice. List its themes in one column and your candidate stories in another. Mark gaps.
Week 2. Write the two candor stories, the two judgment stories, and the mistake story in STAR form. Write a one-page walkthrough of your most complex system with its trade-offs.
Week 3. Two mock interviews: one technical, anchored in that system, one culture round with someone who will push back on diplomatic answers.
Week 4. Prepare your questions for them, one per theme. Rehearse the comp conversation below so the number does not surprise you.

Common mistakes

Answering candor questions diplomatically. "I always try to find common ground" tells the interviewer you have never given hard feedback.
Claiming no weaknesses, or offering a strength in disguise. The memo expects you to know your own gaps.
Treating the memo as marketing and skipping it. Interviewers quote it.
Describing tasks completed rather than decisions made and outcomes owned.
Preparing algorithm puzzles instead of depth on your own systems.
Not asking anything back. A candidate with no questions about how the team actually operates reads as someone who has not thought about whether they would thrive there.

The comp conversation is different too

Netflix pays top-of-market cash, lets you choose your own salary and stock-options split, and has no bonus theater. That simplifies the arithmetic in our equity guide but sharpens the negotiation: with one big number instead of four levers, your market evidence has to be excellent. If Netflix is one of several offers, handling competing offers covers how to use that evidence without bluffing.

Related guides

The Netflix keeper test guide covers the manager's question behind the dream team idea and the interview questions it produces. For the systems side, see the Netflix system design deep dive.

Targeting Netflix? Get matched with a coach who can pressure-test your stories against the memo, then rehearse with the STAR guide and a mock interview.