Katkat

Company

Netflix interview questions

97 practice questions in the style of Netflix's interviews, covering Machine Learning, Data Manipulation (SQL/Python), Coding & Algorithms, Behavioral & Leadership, Statistics & Math, ML System Design, System Design, Analytics & Experimentation, Software Engineering Fundamentals.

Questions97

9 easy63 medium25 hard

Your progress0/97

Netflix interview questions by the numbers

Last updated

Katkat has 97 Netflix interview questions. The largest topics are Coding & Algorithms (31%), System Design (23%) and Software Engineering Fundamentals (12%). By difficulty: 9% easy, 65% medium and 26% hard. The most common round is Onsite (47%). Frequent concepts include System Design, Distributed Systems, Caching and Data Structures.

Difficulty

  • Easy9% · 9
  • Medium65% · 63
  • Hard26% · 25

Interview rounds

  • Onsite47% · 46
  • Technical Screen40% · 39
  • Other5% · 5
  • HR Screen4% · 4
  • Online Assessment3% · 3

Roles

  • Software Engineer64% · 62
  • Data Scientist21% · 20
  • Machine Learning Engineer11% · 11
  • Data Engineer4% · 4

Frequent concepts

  • System Design12% · 12
  • Distributed Systems7% · 7
  • Caching6% · 6
  • Data Structures6% · 6
  • Concurrency5% · 5
  • Scalability5% · 5

Showing 61–90 of 97 results

  • This question evaluates a candidate's ability to design and analyze efficient algorithms for detecting longest consecutive incrementing sequences in unsorted integer arrays, testing understanding of appropriate data structures and time/space complexity trade-offs.

    NetflixData ScientistCoding & AlgorithmsOnsite
  • This problem tests your ability to combine a Least Recently Used (LRU) cache with a command-based undo system, applied to a hierarchical tree structure traversal.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates proficiency with data structures, API design, and system-level concerns by combining timed in-memory caching, command undo/redo semantics, and depth-first traversal of a tree; it falls under the Coding & Algorithms domain and is commonly asked to assess practical implementation skills, correctness under edge cases, and the ability to reason about time and space complexity. The level of abstraction spans practical application—designing clean APIs and implementing core logic—while also requiring conceptual understanding of complexity analysis and background cleanup or state-management patterns.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates streaming data processing, string tokenization, and frequency-aggregation competencies, focusing on maintaining accurate counts over incremental text inputs using associative data structures.

    NetflixMachine Learning EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates proficiency in designing efficient in-memory data structures and tree algorithms, specifically time-to-live cache behavior (expiration semantics and accurate unexpired counts) and per-node subtree-height computations for balance reporting, and it falls under the Coding & Algorithms domain.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests the ability to design an in-memory storage system that combines fixed-capacity constraints with time-based invalidation logic.

    NetflixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates understanding of time-versioned data storage, related data-structure selection, handling of overwrite semantics at equal timestamps, and the ability to reason about correctness and complexity trade-offs.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to design a cache that respects both memory capacity and item weights, requiring an efficient combination of a hash map and a doubly linked list.

    NetflixData EngineerCoding & AlgorithmsTechnical Screen
  • A coding interview question that asks you to implement an in-memory key-value store whose entries expire after a per-key time-to-live, explain the design as you go, and test it. It tests expiry semantics, overwrite handling, reclaiming memory from keys that are never read again, complexity trade-offs and deterministic tests with a controllable clock.

    NetflixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates proficiency in array algorithms and algorithmic optimization, focusing on handling boundary cases, reconstructing index ranges, and meeting strict O(n) time and O(1) extra-space constraints.

    NetflixData ScientistCoding & AlgorithmsOnsite
  • This question evaluates graph algorithm skills (topological ordering and cycle detection) and software design competencies related to command interfaces, undo semantics, and shared-state management.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to process unstructured text into a searchable index and navigate hierarchical data structures using path patterns.

    NetflixData EngineerCoding & AlgorithmsOnsite
  • This question evaluates understanding and practical implementation of data structures and algorithms for a weighted cache, including weighted eviction policies, use of ordered maps, and time-space complexity analysis.

    NetflixSoftware EngineerCoding & AlgorithmsTechnical Screen
  • A machine learning fundamentals question asking how L1 normalization differs from L2 normalization of a vector. It tests precise definitions, what each normalized vector represents geometrically, when each is the right choice, and the ability to keep normalization distinct from L1 and L2 regularization.

    NetflixMachine Learning EngineerMachine LearningTechnical Screen
  • A set of basic machine learning checks: a Bayes' rule posterior with a low base rate, forward-pass and parameter-count arithmetic for small neural networks, and true-or-false concept checks on k-nearest neighbors and Transformer attention. It tests quick, accurate reasoning on core ML fundamentals.

    NetflixMachine Learning EngineerMachine LearningOnline Assessment
  • This Software Engineering Fundamentals question evaluates data and domain modeling skills for ad-technology order management, focusing on entities such as advertisers, agencies, orders, line items, targeting, creatives, delivery constraints, tracking events, reporting needs, and configuration versioning.

    NetflixSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question tests the ability to design a robust data pipeline and schema for tracking ad performance metrics, focusing on handling event-level data, aggregations, and dimension consistency.

    NetflixSoftware EngineerSystem DesignOnsite
  • This question evaluates proficiency in data modeling and database schema design for advertising systems, including entity-relationship modeling, privacy-aware user identifier handling, and delivery/tracking log representation.

    NetflixSoftware EngineerSystem DesignOnsite
  • Implement an in-memory movie playlist in which get returns the highest-scoring movie not yet served in the current loop, starting a new loop once every movie has been served, while scores can change at any time. A follow-up asks where to add locks when many threads call it concurrently.

    NetflixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Given two integer matrices stored as dense lists of rows in which most entries are zero, return their exact matrix product. It tests handling matrix dimensions correctly and exploiting sparsity to skip work on zero entries while still producing every entry of the result.

    NetflixMachine Learning EngineerCoding & AlgorithmsOnline Assessment
  • This question evaluates a Data Scientist's behavioral and leadership competencies — including adaptability to changing expectations, stakeholder management, prioritization between depth and breadth, decision-making principles, and post-outcome learning — and sits squarely in the Behavioral & Leadership domain.

    NetflixData ScientistBehavioral & LeadershipOnsite
  • This problem tests the design of an in-memory caching system, focusing on memory management, eviction strategies, and concurrency control to ensure high performance and stability.

    NetflixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests the ability to manage dynamic scheduling and priority updates using balanced binary search trees (ordered maps) while handling concurrency and system scalability.

    NetflixSoftware EngineerSoftware Engineering FundamentalsOnsite
  • A problem-solving question about recommending new friends from a mutual friendship graph, worked mostly through discussion with a little code and pseudocode. It tests candidate generation and scoring with deterministic tie-breaks, cost in terms of node degree, handling highly connected users, and precomputing and refreshing suggestions at scale.

    NetflixSoftware EngineerSoftware Engineering FundamentalsOther
  • Tests traversing a binary tree stored in array (heap) layout to compute subtree heights and identify nodes rooted at height-balanced subtrees along with their tree levels.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • This problem tests your ability to use the sliding window pattern and a hash map to maintain a range of unique elements efficiently in O(n) time.

    NetflixSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates proficiency in graph algorithms, notably topological sorting and cycle detection, as well as algorithmic complexity analysis and handling of dependency constraints.

    NetflixSoftware EngineerCoding & AlgorithmsOnsite
  • Review a feature pipeline pull request whose tests all pass and explain what could break once it runs in production, from time leakage and training-serving skew to data quality and scale. Then decide how the same features should be served when the model needs day-old, minute-fresh or request-time values.

    NetflixMachine Learning EngineerML System DesignTechnical Screen
  • Implement an in-memory cache whose entries expire individually, reclaim memory for keys that are never read again, and prove it with deterministic tests using an injected clock. Tests expiry semantics, stale-entry handling and test design.

    NetflixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Show Behavioral Fit and Experience evaluates behavioral evidence, ownership, communication, trade-offs, and measurable outcomes in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    NetflixSoftware EngineerBehavioral & LeadershipHR Screen

Netflix interview experiences

All 16 →
  • Phone Screen on a Key-Value Store with TTL, RejectedNetflix · Software Engineer · Senior+ · Technical Screen · Oct 2026
    Rejected

    I recently interviewed for an IC5 role on the Netflix Ads team. The phone screen was the classic Key-Value Store with TTL. Personally I felt it went okay. I implemented the usual set of methods, and for TTL expiration I used a min heap keyed on timestamp. I explained my design thinking and the tradeoffs as I went, wrote test cases at the end, and the code ran correctly. I still got rejected. The…

  • 90-Minute OA With 4 MC and 2 Coding QuestionsNetflix · Machine Learning Engineer · Intern · Online Assessment · Sep 2026

    I just finished the Netflix MLE Intern OA. It was timed at 90 minutes, with 6 questions total: 4 multiple choice and 2 coding. Below are the topics I remember. I don't fully remember the exact wording or details anymore, but I hope this helps others preparing for the same OA. The multiple choice questions were fairly basic overall. The topics I can recall: Bayes' formula; simple calculations invo…

  • Data Platform Loop, Rejected After the Final System Design RoundNetflix · Software Engineer · Onsite · Sep 2026
    Rejected

    I think the team I interviewed for was data platform. A recruiter reached out because I had related experience a few years ago. From other posts I used to think the problem solving round and the coding round were different, but after going through it they feel like essentially the same thing. Netflix's interview process is very long, and different teams probably test different things, so you need…

  • ML Fundamentals Plus a Production PR Review, RejectedNetflix · Machine Learning Engineer · Technical Screen · Sep 2026
    Rejected

    Sharing a failure story from September. The recruiter reached out to me on LinkedIn, and then we scheduled a phone screen. Since this was hiring for a newly formed applied GenAI org, the format was pretty new and I haven't seen it in any other interview write-ups: 30 min of ML fundamentals + 30 min of practical coding. 30 min ML fundamentals, three questions: What is a KV cache? What is attention…

  • Two Back-to-Back Coding Rounds and a No-Feedback RejectionNetflix · Software Engineer · Technical Screen · Aug 2026
    Rejected

    The questions were different from every interview report I had seen. There were two back-to-back interviews. First phone round — problem solving: Question: The ping times between cities are different. Starting from one city, find the fastest paths for broadcasting to every other city. Solution: Dijkstra's algorithm. Follow-up: If the ping times keep changing, how should the paths be updated? Solu…

More companies