Rejected. It doesn't feel like a hard fail — after the interview it took about a week to hear back, and when I followed up, HR said they were syncing up with the team, and in the end told me they were moving on with other candidates.
My own sense is that I didn't perform badly, but definitely not perfectly — there were various small issues where I didn't give the optimal answer right away, or I missed something and only caught it after I'd already finished writing, or I only noticed after the interviewer pointed it out.
So it's not a direct fail, but I also wasn't at the top of this batch of candidates (guess that's the only way I can console myself, haha).
Two rounds of phone interviews, one coding and one problem solving.
The coding one was a variant of LeetCode 3 — they swapped the number for a show name, or changed the requirements a bit, but the underlying logic was the same.
The point of the problem-solving round wasn't really about writing code, but about how you communicate with the interviewer — explaining your thought process and arriving at a reasonable approach. The question was about viewport rendering for the Netflix homepage: how do you make sure that within the first screen, none of the rows or columns have a repeated show.
Discussion
Loading comments…