The interview process consists of eight stages, some of which involve engineers based in Poland (though not Polish), while others are with engineers based in the United States. The interviews with U.S.-based engineers tend to be of higher quality. Some stages feel overly transactional, lacking a personal touch, as if there isn’t a human being on the other side. Technical interviewers conducted in Poland focus heavily on domain-specific knowledge, particularly related to content platforms. For example, they may ask about REST API filtering based on search input, caching strategies tailored to business needs, and similar topics. In one instance, I explained that my only proposed solution—debouncing—was not ideal. Despite this, the interviewer responded condescendingly, reiterating that a delay of up to 3000ms would be too high for a 200ms debounce, which I had already stated. While most interviews were well-structured and effectively assessed problem-solving skills, some were narrowly focused on technical knowledge. These sessions failed to guide the candidate through the problem, missing an opportunity to evaluate their approach to solving unfamiliar challenges. Interestingly, others in my network who have gone through the Netflix interview process reported that they did not encounter such domain-specific questions, suggesting this might be a temporary inconsistency. Overall, the experience was neutral to good. However, two poorly handled stages significantly diminished the positive aspects of the process.

I complied bug lists for Netflix for many years, hoping to eventually get a chance to work there and 1) fix the darn bugs and 2) help them innovate their way out of the ultimate commodification of the extremely crowded streaming video market. Early in my career I spent 4 formative years at a company with a culture similar to that described in Netflix's culture document. This high individual responsibility culture is how I came to approach all my positions at every company I then worked for - and I was eagerly anticipating a kind of "returning home" glow and familiarity during the interview and, hopefully, day-to-day work at Netflix. However, it was a very strange interview: very confrontational. Was he just trying to provoke me and see how I would argue my case? I did argue my case each time but he refused to, or pretended to, not hear me and never acknowledged having heard or understood my points. Insisted my intention to help grow Netflix's market cap by 10X meant that I liked the size of corps that had room to grow 10X, as opposed to my desire, expressed several times, for my ideas and efforts impacting 10X growth to the bottom line (which I believe any one of us is capable of given opportunity and the will to do so - especially for such a rich technology-powered market like streaming video). Insisted EngProd was exclusive of toolkits, frameworks (and debuggers and IDEs) and that I had no business saying I was passionate about it even though I had worked on all four of those things in the past. He stated that any addition to the UI framework would have to be run by all 70 - 100 people who use the framework in order to get their buy in first. I did not mention that I personally thought this to be an onerous anti-pattern, but did say that I would probably find this to be the most challenging part of the position (I am very familiar with UI tech and nothing about what they are currently doing would have been a challenge - just fun as heck). Thereafter, he insisted over and over that, apparently because I said it was a challenge, I was incapable of doing it - instead of me just acknowledging that, as I said, this would be one of my primary focuses until the challenge was overcome. Even after I described how I recently worked on a product that had approximately 20 stakeholders from 3 different organizations and that I had successfully navigated this situation, he expressed his opinion that I would not be up to this task. I also mentioned that I had been a consultant for much of my career. He then insisted that I would leave the company earlier than average and, because I was a consultant, I had been able to write crap software and just leave to go to the next assignment - never having to maintain my own code. Despite my average time at a gig being longer than his average term of employment, and longer than most devs in the Bay Area, and that I had left several positions with code less than 1 bug per 10K lines of code - he, true to form, remain unconvinced. Like a troll, he insisted that he was right about everything and would not acknowledge any point I would make. Finally, I asked why they were still hacking React, trying to make it performant - why didn't they just write their own little toolkit to run on top of all the low-performance platforms they support. His answer was that "the UI is not a core competency", and they couldn't afford the engineering resources to support such an effort. Well, certainly explains a few things, that does. Didn't talk in all CAPS, but... this would be my manager? After processing all this - I now understand why Netflix's UI is the way it is (see any comment thread) and has so many bugs (current annoyance is that it pauses for 1/2 second about 1 minute before the end of every video segment as it loads the following segment. Oh, and now the left arrow of their horizontal-scrolling videosnaps disappears and the right arrow appears in the middle of the screen). Clue to Netflix: the UI is how you compete with the other dozen of so players in this increasingly crowded market. What happens when relying only on content, increasingly boring content, for differentiation has many historical precedents. As I click back and forth between Prime, Paramount+, HBOMax, Hulu, Disney+, and the rest - I have to wonder about the future of this FAANG.