Interview Prep

Netflix interview preparation: what they look for and how to prepare for it

Netflix runs a culture most companies don't. Here's what its own leaders say the bar is, and how to build answers that meet it.

13 min read

Preparing for Netflix looks like preparing for any big tech loop: hunt for a list of rounds, memorize the question formats, polish a few stories. That approach helps you less at Netflix than almost anywhere else, because what the company screens for is whether you'd do well inside an unusual way of working, and whether you'd want to.

This article covers the culture model Netflix leaders describe publicly, and what candor and feedback look like once you're inside. It also covers how to build examples that show independent judgment, the tradeoffs to weigh before you accept, and the questions to ask your interviewers. Read the culture sections first, then rewrite two or three of your stories against them, because that's where most of the preparation value is.

One thing to say plainly before you go further. We don't have reliable current information about Netflix's interview loop, and neither does most of what you'll read online. Hiring managers at Netflix design their own processes, formats change, and any round-by-round map you find is somebody's snapshot from a specific team at a specific time. So this covers the bar and the culture. It doesn't try to map the format. Every claim below is traceable to a named person, on the record, with a timestamp you can check.

The sources are Elizabeth Stone, chief technology officer of Netflix; McKenzie Lock, a general manager at Netflix who runs content platform operations and publishing and has been there about six and a half years; Ebi Atawodi, a former director of product at Netflix now at YouTube; and Gibson Biddle, VP of product at Netflix during the DVD and early streaming years.

The culture model, in the words of the people running it

Netflix describes its culture as three things that depend on each other: high talent density, candor, and freedom and responsibility. The order matters. Elizabeth Stone, who became CTO in 2023 after leading data and insights, says the first one is what makes the other two possible at all.

Her framing is that talent density is what buys you everything else. If the people around you are excellent, the company can skip the approval layers, the vacation policy, and the prescriptive process that most companies use to manage risk. Take the talent density away and the same freedom gets dangerous.

She's also direct that keeping talent density high asks for behavior most people find unpleasant.

What keeping the bar high actually costs. The player below is queued to 30:48, the exact moment Elizabeth Stone says it. Watch on YouTube.

"No one comes to Netflix as a perfect human being and stays a perfect human being the whole time. We all have ways that we could grow and improve. And so in order to keep that bar high, you have to be willing to have those types of very uncomfortable conversations. It's an uncomfortable amount of candor and feedback in order to keep that bar high."
Elizabeth Stone, chief technology officer at Netflix · Lenny's Podcast

Earlier in the same conversation she says you have to hold yourself to "a lot of stuff that doesn't feel like natural human behavior" (30:20). That's a fair summary of what you're signing up for, and a good place to start when you're deciding whether you want this job.

The third piece, freedom and responsibility, gets quoted a lot and explained badly. Ebi Atawodi ran product for payments and EMEA at Netflix, and liked the model enough that she'd already built a version of it on her team at Uber before she joined.

What freedom and responsibility means day to day. The player below is queued to 1:20:34, the exact moment Ebi Atawodi describes the values she carried out of Netflix. Watch on YouTube.

"I do believe in this freedom of responsibility. I will give you freedom, but with that comes responsibility. That means the buck stops with you."
Ebi Atawodi, former director of product at Netflix, now at YouTube · Lenny's Podcast

She goes on (1:20:58) to describe the idea of an informed captain: one named person owns a decision, gathers the context and the input, and then makes the call, rather than six people arriving at consensus. If you've spent your career in places where decisions get made by committee, you'll need to show you can work without that.

Who tends to do well there

Stone describes a hiring bar that isn't about clearing a checklist. She contrasts it with the way large companies often hire, checking a person against a list of skills and slotting them into a defined box of work.

What she says Netflix looks for instead is people who arrive with "additive skills, additive perspectives, people who are going to push our thinking on something" (41:09), which she connects back to talent density: every hire is supposed to raise the level of the team they join. She frames the underlying question as whether you'll "help us identify the right problems to solve, or new ways to solve existing problems" (40:31).

So the profile that does well is someone who can operate without much structure, who forms opinions and says them, and who is comfortable owning an outcome instead of a task list. Stone puts the requirement bluntly when explaining why Netflix can run with so little process: the company relies on people who are smart "but even better have strong judgment" (46:16).

McKenzie Lock, a GM at Netflix, adds a useful correction to a common assumption about where those people come from. Asked whether Netflix mostly hires out of Amazon, Meta, and Google, she says the net is much wider, and that plenty of high performers on her team came from companies you've never heard of. What she does want is exposure to federated decision-making, because that's how the company runs (27:23).

If you're working out how to present a non-obvious background against a bar like that, the positioning playbook covers how to frame your track record for a specific company rather than in general.

Candor, and how it turns up in the interview

Candor at Netflix isn't only about feedback conversations with your manager. Stone gives two examples of what it looks like from a senior leader. She takes notes in leadership meetings and shares them with her whole organization, which she ties to the company's phrase "context, not control" (48:25). And when the company introduced levels for individual contributors, a change she describes as a roller coaster, she ran a retro on it and said publicly that it hadn't all gone well (51:22).

Netflix also runs without the process most companies use to deliver all of this.

No performance reviews, on purpose. The player below is queued to 34:26, the exact moment Elizabeth Stone explains what Netflix does instead. Watch on YouTube.

"We don't have performance reviews. So we don't have a practice that a lot of other companies do where we would think about reflecting on like a rating of how things are going. We do have an annual cycle of 360 feedback, where you request and receive feedback from a lot of people. But it's not an input to some output."
Elizabeth Stone, chief technology officer at Netflix · Lenny's Podcast

She admits it's hard to sustain, and that she gets about 300 pieces of feedback in the annual 360, some of it about things that happened six months earlier, which she'd rather have heard at the time (35:50).

Here's why that matters for your preparation. In a culture where feedback is the main management mechanism, interviewers pay attention to how you handle being questioned. McKenzie Lock describes what candidates walk into on her team's case exercise.

A debate-heavy culture, tested on purpose. The player below is queued to 30:26, the exact moment McKenzie Lock explains why the case presentation gets picked apart. Watch on YouTube.

"They'll present it and there'll be quite a lot of questioning and debate during that process with the folks on the panel. And the reason for that is that Netflix is a very logic-based and debate-heavy culture, and so we want to see how people will respond to that."
McKenzie Lock, general manager at Netflix · The Skip

In the same answer she names what she's looking for: depth of thought, meaning you've come at the question from several angles and anchored on why; simplicity, meaning you can make a complicated problem followable without flattening it; and a healthy degree of skepticism. She calls out one behavior as a red flag, which is candidates who never ask whether it's the right problem to be solving and just start working through an answer (31:32).

Practically, that means two things for you. Disagreeing with an interviewer is allowed and sometimes expected, so long as you disagree with reasons and stay genuinely open to theirs. And changing your mind mid-conversation because someone showed you something you hadn't considered counts in your favor. If pushing back on senior people is the part you find hardest, the playbook on disagreeing respectfully has the wording to practice.

The book that made this famous, and how to use it

Most of what circulates about Netflix culture traces back to No Rules Rules, the book Reed Hastings wrote with Erin Meyer. Worth being precise here: that book is a description of Netflix written by its founder, and the notes below come from the Mochary Method curriculum's summary of the book, not from Netflix. It's a useful model of the feedback style. For how the company talks about itself today, go with the leaders quoted above.

The four A's of feedback, from the curriculum notes on the book

  • Assist. Give feedback with positive intent. Explain how the change helps the person or the company, never how it relieves your own frustration.
  • Actionable. Say what someone can start doing, not just what to stop.
  • Appreciate. When you receive it, expect to feel defensive, and thank the person instead of explaining yourself.
  • Accept or not. You have to listen and say thank you. You only act on it if it resonates.

The "appreciate" step is the one worth rehearsing before an interview. When an interviewer pokes a hole in your answer, the instinct is to defend the decision you made two years ago. A better first move is to acknowledge the point, say what you'd weigh differently now, and then explain what you knew at the time.

Building examples that show judgment

Every behavioral round asks for examples. A Netflix-style panel pushes on a specific quality inside them: did you decide, or did you wait to be told? Use these filters when you pick which stories to bring.

What each example needs to show

  • You owned the call. Name the decision, say that it was yours, and say what you'd have done if it went wrong. "We aligned as a group" is the answer to avoid.
  • You gathered dissent first. Who did you ask, what did they say, and which piece of input changed your plan.
  • You questioned the problem. At least one story where you pushed back on the brief before working on it.
  • You gave hard feedback. A specific time you told a peer or a manager something uncomfortable, what words you used, and what happened next.
  • You took hard feedback. Something real that landed badly, what you did with it, and what changed in your work afterward.
  • You made the outcome public. Especially a failure you told people about rather than quietly moved past.

Two of those are worth extra work, because most candidates have never told the story out loud. The giving-feedback example needs the actual sentence you said, down to the words. And the receiving-feedback example needs to be genuinely uncomfortable, since a story about being told to speak up more in meetings tells an interviewer nothing.

Gibson Biddle, who was VP of product at Netflix before running product at Chegg, spent one to two days a week hiring and recruiting when he was in the thick of it, and describes a specific thing he screens senior candidates for.

Lenny's Podcast: Gibson Biddle on his DHM product strategy framework. This one is audio only. The quote is at 50:50; the player starts from the top, or open it on Apple Podcasts cued to 50:50.

"I look for folks who understand how important culture is, because culture helps people to understand the skills and behaviors that are wanted of everyone within the building."
Gibson Biddle, former VP of product at Netflix · Lenny's Podcast (50:50, audio)

He also says he looks for people who are "proactive, results-oriented folks," and puts it more simply a second later: "For me, leaders lead. You can't be a follower" (50:43). If you're building the rest of your behavioral answers, the behavioral interview questions playbook covers the structure to hang them on.

Practice not getting defensive

Work Coach records how you take feedback and flags the moment you started defending a decision instead of examining it. A simulated panel then challenges your example, which is what the loop does.

Start Free Trial

2-week trial, no credit card needed. Your data is never shared with your employer.

The keeper test, and the tradeoffs to weigh

The keeper test is the piece of Netflix culture candidates ask about most, and it's usually described wrong. Here's the CTO defining it.

The keeper test, defined by the CTO. The player below is queued to 31:43, the exact moment Elizabeth Stone explains it. Watch on YouTube.

"That's where we refer to the keeper test, which is really just a mental framing to make sure we hold ourselves accountable for this. Where if I'm asking myself the question, if this person on my team came to me and said, I'm leaving today, I have a different opportunity and I would like to take it, would I do everything I could to keep them at Netflix? If not, then I should be having that tough conversation about should you really be here."
Elizabeth Stone, chief technology officer at Netflix · Lenny's Podcast

Two details from her answer are worth holding onto. It's a question managers ask themselves, with no ranking or quota attached to it. And employees use it in the other direction: she says people ask her "am I passing your keeper test?" often enough that it's become a normal one-on-one question (33:44), which she treats as another way of asking how am I doing.

Lenny asks her the obvious follow-up, which is whether this creates a Hunger Games atmosphere where people worry about being fired any day. She answers from her own experience.

The CTO on whether it's stressful. The player below is queued to 37:06, the exact moment Elizabeth Stone answers the Hunger Games question. Watch on YouTube.

"In my personal experience, I have felt a lot more at ease by having these conversations than by not having them. So in many roles I've had, I haven't been sure how I was doing or things I could be doing better on, and I didn't quite know how to get that information. And that made me feel much more stressed or nervous or at risk."
Elizabeth Stone, chief technology officer at Netflix · Lenny's Podcast

She doesn't claim the pressure isn't real. She says the nerve-wracking part is the high bar itself, and being surrounded by people who are very good, which "can feed a sense of, am I doing well enough compared to how everyone else is doing" (38:01). She says she feels it herself, and her point is that the regular conversations take some of that pressure off.

So here's what you're actually weighing:

Worth it if

  • You'd rather know where you stand every month than get a rating twice a year.
  • You want to make calls without asking permission, and you're willing to own them when they miss.
  • You want compensation at the top of the market. Stone describes the policy as "personal top of market," deliberately set so pay doesn't become golden handcuffs (39:37).
  • You do your best work around people who are visibly better than you at something.

Think harder if

  • You need a defined promotion ladder. Netflix only introduced levels for individual contributors a couple of years before this conversation, and Stone says the implementation still has a lot to improve (51:22).
  • Your security comes from tenure or from process protecting you. Neither exists here in the usual form, and there's no PIP runway before a manager acts.
  • You're joining for the brand or the pay rather than the way of working. That's the version of this job people burn out in.
  • You'd need a very stable year for reasons outside work.

What we can't tell you about the current loop

You'll find round-by-round guides to the Netflix interview online. Be careful with all of them, and here's the reason, from a Netflix hiring manager describing how her own process is set.

Why there's no single Netflix loop. The player below is queued to 9:58, the exact moment McKenzie Lock is asked whether her process is standard across Netflix. Watch on YouTube.

"Netflix, one of our cultural values is responsibility and freedom, we talk a lot about that. And so what that means is that we really put a lot of judgment, we trust hiring managers and trust their judgment in terms of how to design the process. So there's definitely similarities, and I'd say that a lot of those traits are similar across groups, but I'm speaking specifically for my team."
McKenzie Lock, general manager at Netflix · The Skip

The freedom that shows up in the product work shows up in hiring too. One team's process can differ from another's, and the same team's process can change between quarters. Lock does describe her own team's approach in that conversation, a take-home exercise covering strategy, prioritization, and solutioning, with one to two weeks to do it, presented to a panel and paired with faster case questions on the call (30:18 and 32:08). That's one team's format as of early 2026, and it may already have moved.

What to do instead of hunting for the format: ask your recruiter directly what rounds you have, who's on the panel, and what each one is testing. Recruiters answer that question happily, and at a company with this much variation it's the only reliable source. Then prepare against the bar described above. The final-round playbook covers how to prepare for a full panel once you know what's in it.

Questions worth asking your interviewers

At a company that hires for candor, the questions you ask are part of the evaluation. Vague questions about culture will get you the recruiting-page answer, so ask for specifics instead.

About how the team really works

  • When was the last time someone on this team made a call you disagreed with, and what happened?
  • How do decisions get made here when people don't agree? Who ends up owning the call?
  • What's a recent thing this team got wrong, and how was that shared?

About feedback and the bar

  • What's the most recent piece of feedback you gave someone on this team?
  • How would I find out I wasn't meeting your expectations, and how quickly?
  • What does someone in this role do in their first six months that makes you glad you hired them?

About the keeper test specifically

  • How often do you ask yourself the keeper test about people on your team?
  • Has anyone left this team in the last year, and what did you tell the rest of the team about why?
  • What kind of person has struggled here who'd have done fine somewhere else?

The last one gets you the most. If a manager answers it specifically, you learn exactly who this job suits. If they can't answer it, that tells you something about how much feedback their team gets.

Frequently asked questions

Will they ask me about the keeper test in the interview?

Nobody we have on record says that's a standard question. But your interviewers live with it, so being able to talk about it without flinching helps. If it comes up, the answer that works is a real one: you'd want to hear early and often where you stand, and you'd take an uncomfortable conversation over six months of guessing.

Should I read the Netflix culture memo before interviewing?

Yes, and read it as a description of how the company wants to operate rather than a script to quote back. Ebi Atawodi's story is a good illustration of what it's for: someone sent her the memo while she was at Uber, and she used it to build a culture on her own team long before she joined Netflix (1:20:22). Reciting the values at a panel won't help you. Having examples that match them will.

How direct should I actually be in the interview?

Be direct, and attach your reasons. McKenzie Lock's red flag is a candidate who never questions the problem, so pushing back is expected. What she's watching alongside that is how you respond to questions and pokes, so the pushback has to come with visible openness to their answer. Disagreeing and then defending your position no matter what you hear is the worst version of this.

Does Netflix only hire from big tech companies?

Lock says no. She describes a much broader sense of talent, and says plenty of exceptionally high performers on her team came from companies you haven't heard of (27:42). What she does want is people who've operated in a federated decision-making environment, which you can demonstrate from a startup, an agency, or a team inside a big company that ran with real autonomy.

Is the pay really that different?

Stone describes the policy as personal top of market, and says the intent is to be highly competitive without pay becoming golden handcuffs (39:37). She also says the company hopes not to rely on compensation to make people want to be there. Treat the money as real and the culture question as the one that decides whether you'd stay.

What if my current company has none of this?

That's most candidates, and it isn't disqualifying. Lock's point about federated decision-making is about what you've been exposed to rather than where you worked. Find the moments in your history where you decided without cover, disagreed with someone senior, or told a group something they didn't want to hear, and build your examples out of those.

Your Netflix prep on one page

Before you prepare answers

  • Watch the Elizabeth Stone conversation end to end. It's the longest public account of the culture we could find from someone currently running a large part of the company.
  • Read the culture memo on the Netflix jobs site as a description of intent.
  • Ask your recruiter what rounds you have, who's on the panel, and what each one tests.
  • Decide honestly whether the tradeoffs above are ones you want. Treat that as a real decision.

When you build your examples

  • Pick stories where you owned a decision, and say so in the first sentence.
  • For each one, name who you asked for dissent and what changed because of it.
  • Have one example of pushing back on a brief before doing the work.
  • Have one example of giving hard feedback, with the actual words you used.
  • Have one example of receiving hard feedback that stung, and what changed afterward.
  • Have one failure you shared publicly rather than buried.

On the day

  • Ask whether it's the right problem before you solve it.
  • Expect questioning and debate on any case work, and treat that as part of the evaluation.
  • When challenged, acknowledge the point first, then explain what you knew at the time.
  • Change your mind out loud when someone shows you something you'd missed.
  • Bring energy. Lock's closing advice to candidates is that momentum and drive go a long way right now, so signal it wherever you can (54:08).
  • Ask your own questions about decisions, feedback, and who has struggled on the team.

Sources