The interview process consists of eight stages. Some stages 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 and lack 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.

Q: How would you filter results dynamically from a REST API based on the input query?