Senior Full Stack Engineer Interview Experience

I’d clearly read the culture memo, and I treated it like the center of the conversation. I talked through which principles resonated with me, especially feedback, and then they immediately turned that into a mini behavioral by asking for an example of giving feedback. It wasn’t just ‘do you know the memo.’ They were checking whether I actually aligned with it and could talk in that framing.

I answered this pretty directly off the job description because that seemed to be what they wanted. The vibe I got was that they were not looking for a generic ‘why Netflix’ answer. They wanted to hear why this exact role made sense for me and whether my background lined up with the internal tooling and data-heavy work they were hiring for.

Build out a React component to display event log stream configuration data.

They gave me a small React project, a README, a stubbed component, and a mock endpoint for the config list. I built it up in steps: first a simple table, then a collapsible JSON view, then collapse all and expand all. The interesting part was the discussion around hook usage, fetching, memoization, and effects. I used a pre tag for the JSON and the interviewer specifically called that out as a good semantic HTML choice, which told me they cared about real front end depth, not just getting it working.

This round went deeper than the recruiter screen and stayed very question-answer the whole time. I walked through an example of receiving feedback and then got pushed on how I’d actually carried that forward afterward, not just whether I took it well in the moment. It felt like they were looking for evidence that feedback changes how I work over time.

They asked for one example of dissent and then immediately wanted another, which definitely felt like a curveball. I had a few different projects in mind, so I was balancing across multiple stories, but the key thing was that they weren’t satisfied with a single polished answer. They wanted to see whether disagreement was a real repeated pattern in how I work, not a one-off story.

What does your background look like, and what kind of candidate do you think fits this team best?

By the end, it became very clear this was an expert-fit search. I heard two candidate buckets: someone with deep data-domain expertise doing exactly this kind of work, or someone very front end and product oriented who had driven internal tools with internal stakeholders. They were also explicit that React experience mattered, so it did not feel stack-agnostic at all.

Build a collapsible list component in React.

This one was another practical React task where I had to display data and make it collapsible. The tricky part was less the component itself and more the discussion once a filter changed the data underneath it. We spent a lot of time on how React handles renders and updates when items are removed, and maybe touched briefly on what I’d do with a huge list. It felt like they were probing whether I really understood React’s behavior, not just whether I could write JSX.

You’re building an event logging product. Would you build and own the client libraries yourself, or have each team build their own clients while you provide documentation?

This threw me off because we never drew boxes at all. I treated it more like a PM-style discussion and did a lot of requirements gathering first. I talked through long-term failure modes, scalability, team bandwidth, and the human side of supporting other teams versus owning the clients ourselves. I also pulled in examples from past work where I’d seen cross-team interfaces create pain. It felt like they wanted judgment on a real problem the team was dealing with, not a textbook architecture answer.

This one was much lighter than I expected for a Netflix behavioral. The focus was on receiving critical feedback, especially from someone above me, and showing how I improved from it. It felt narrower than the hiring manager round and much less like a grill session than I’d heard some people get.

They also wanted the same general theme from a different angle, like feedback coming from someone I was leading or very close to in the work. The point seemed to be whether I could take hard input across different power dynamics, not just from a manager. Since it was only about 30 minutes, we really just covered those feedback dimensions and left time for questions.

This was the hardest behavioral for me. My first example was a disagreement over a design and then he drilled into exactly how I voiced it, like whether it happened in comments or team meetings. Then he asked for the same kind of example again, and by the third time I was really scraping. On the last one he even suggested that a PR disagreement would count, which helped me get something out. It felt very intentional, like he wanted to see how I handled pressure when I couldn’t rely on one polished story.