Netflix interview notes, page 7 of 20

“I went for the rotation first, which was a mistake.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Three parts and the first two felt fine.” The rest of the author's notes on Data Scientist interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic sliding window.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The actual algorithm wasn't the hard part, I had that in a few minutes.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The prompt was way longer than expected and took a few minutes just to parse what they were actually asking.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I'd seen topological sort problems before and thought I had it.” The rest of the author's notes on Software Engineer interview at Netflix, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with the basics: a hashmap storing value plus expiry timestamp, check on get and return null if stale.” The rest of the author's notes on Software Engineer interview at Netflix, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is the kind of question that sounds easy if you know the theory but they really want a real project, not a textbook answer.” The rest of the author's notes on Software Engineer interview at Netflix, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The O(1) space constraint is what tripped me up at first.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight for a HashMap plus a TreeMap keyed by weight, which felt right.” The rest of the author's notes on Software Engineer interview at Netflix, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.