Uber interview notes, page 2 of 61

“I spent way too long on the design part and rushed the monetization angle, which is obviously the whole point of the question.” 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.

“The multi-part structure threw me a bit.” The rest of the author's notes on Software Engineer interview at Uber, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I got the basic class working fine.” 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.

“The interviewer was visibly exhausted, which made the whole thing feel a bit flat.” The rest of the author's notes on Frontend Engineer interview at Uber, Onsite - Coding / Algorithms 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 check every pair of points, which is obviously too slow but I coded it halfway anyway before catching myself.” 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 started with the cart and item models which felt safe, but then the pricing piece got messy fast.” 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.

“I started with the recursive DFS approach because that's what everyone knows, O(N) time, O(H) space for the call stack.” 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 started with the naive approach of searching each word independently using DFS and backtracking.” 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.

“Seen this one before on prep forums so I wasn't totally blindsided.” 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.

“This one took me a minute to even parse.” The rest of the author's notes on Machine Learning 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.