Uber interview notes, page 20 of 61

“I jumped straight to a hashmap of name to count and felt pretty good about it.” The rest of the author's notes on Software Engineer interview at Uber, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I fumbled the opening because I jumped straight into user segments without grounding it in why Netflix would even do this.” The rest of the author's notes on Product Manager interview at Uber, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I rambled a bit here, jumped around chronologically and lost the thread.” The rest of the author's notes on Software Engineer interview at Uber, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to reach for DFS and backtracking, which would've been completely wrong here.” The rest of the author's notes on Software Engineer interview at Uber, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to treat it like the simpler version where the path only goes parent to child.” The rest of the author's notes on Software Engineer interview at Uber, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Went with row-by-row backtracking which felt right.” The rest of the author's notes on Machine Learning Engineer interview at Uber, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent too long on the revenue upside and not enough on user experience tradeoffs.” The rest of the author's notes on Product Manager interview at Uber, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to copy the whole adjacency list on every snapshot, which is obviously wrong at scale and they pushed back immediately.” The rest of the author's notes on Software Engineer interview at Uber, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was BFS and that was right, but I spent too long second-guessing myself on the modulo wrapping for leftward jumps.” The rest of the author's notes on Software Engineer interview at Uber, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I jumped straight to GMV and order volume, which felt safe but probably too surface-level.” The rest of the author's notes on Product Manager interview at Uber, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.