Netflix software engineer candidates describe a recruiter call, a hiring manager conversation, technical rounds that vary by team, and culture-heavy interviews built around the Netflix culture memo.
$261K
Avg. Base Comp
$360K
Avg. Total Comp
5-7 rounds
Typical Rounds
3-4 weeks
Process Length
Across candidate reports, the Netflix software engineer interview is as much a culture conversation as a coding test. Several candidates say interviewers asked about the Netflix culture memo, including which part resonated most and how they work in practice. One candidate who accepted an offer said the questions drew directly from the memo and that a concrete example beat a polished answer that ignored it.
The recruiter call also seems to matter more than a logistics check. One candidate who received an offer was asked about relocation, why they were leaving, and technical achievements. Another treated the call as a real interview and found that it paid off. A third had a short, friendly screen about languages and motivation, and the process went no further.
Technical content differs by team and level. Reports mention a live topological sort in an IDE plus a mapreduce question, and a vague content-manager CRUD prompt for a senior role. Others describe coding, system design and data modeling tied to studio and production tools, and a system design discussion on recommendation pipelines. One candidate describes a loop of short video conversations with no coding at all. Ask your recruiter what your team will focus on, since candidates describe different emphases depending on domain.
Timing and outcomes vary. One candidate reports about three to four weeks from start to finish, while others describe long gaps or no response after follow-ups. Prepare for some waiting and follow up proactively.
Synthesized from 38 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Netflix process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Netflix
Write a query to get the number of friends of a user that like a specific page
| Question | |
|---|---|
| P-value to a Layman | |
| Paired Products | |
| Basic Regex | |
| Identifying User Sessions | |
| Centralized Event Ingestion | |
| Digital Library Borrowing Metrics | |
| Real-Time Hashtag Partitioning | |
| Priority Queue Using Linked List | |
| Page Recommendations | |
| Loan Model | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| John's New Best Friend | |
| Relational Migration | |
| Unstructured Data Pipeline (ETL) | |
| Reverse List Starting at Index K | |
| Trial Test Analysis | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Raining in Seattle | |
| Find the Missing Number | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call covering background, why Netflix, languages used, relocation and reasons for leaving. One candidate who received an offer treated it as a real interview, so prepare a clear resume story and some familiarity with the culture memo. One candidate's process stopped after this call.
Several candidates describe a hiring manager call. Reports mention discussion of past projects, libraries used and which culture memo idea resonates. Tone varies by interviewer, and one candidate found the call disjointed and never heard back, so expect experiences to differ.
Candidates report different formats. These include a live coding screen with a topological sort and a mapreduce question, and a coding assessment built around a vague content-manager CRUD prompt. One candidate reports no coding at all. Ask your recruiter which format applies.
Reported loops range from three onsite rounds to five or more conversations. They may include coding, system design, data modeling, and behavioral interviews with team members and cross-functional colleagues. Candidates mention edge cases, recommendation pipelines and domain depth, so expect depth in your area.
Outcomes in these reports include offers, rejections and silence after follow-up emails. One candidate noted that limited domain depth can become a deciding factor. Follow up proactively and be ready to show relevant experience.
