From 33 candidate accounts, updated Oct 12, 2026
Netflix runs a senior-biased, team-specific loop: you are matched to a particular team before you interview rather than hired into a general pool, and a recruiter screen is followed by a hiring-manager conversation, a technical screen that is often a take-home instead of a live coding round, then an on-site round of engineer/manager interviews and a second round with directors and cross-team partners. The coding questions candidates describe are practical rather than puzzle-style (implement a TTL cache, a jq-like nested-map lookup, a transactional key-value store, an OOD feature class), and the take-homes are graded hard on judgment calls the brief never states. The distinctive part is the culture screening: the culture memo is sent to candidates ahead of the first call, opinions on it are actively probed, and multiple technically strong candidates report being rejected purely on the culture/behavioral round with no feedback.
These 33 writeups cover data, software engineering, design and other roles, US (Bay Area/Los Gatos) heavy. 32 of them were posted under a forum handle, so we could not verify the authors’ identities.
unknown. 1 round. Shared by jcadam on hn, 2020-09-28
unknown. 1 round. Shared by cultofmetatron on hn, 2024-11-16
372 open roles in our index. Advertised pay floors run $210k to $440k (median $320k, from 185 postings that state pay).
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.
TheJobsMap