Uber interview notes, page 22 of 61

“I went straight to rider savings and driver utilization, which felt obvious in retrospect.” 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 core idea clicked pretty fast.” 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 obvious stuff like ID verification failures and age restrictions, then got into things like driver refusals and stricter delivery windows.” 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.

“I had a decent story ready but fumbled the delivery.” 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 jumped straight into the data ingestion layer and kind of forgot to nail down what kind of heatmap we were even talking about.” 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 jumped straight to BFS on a directed graph, multiplying edge weights along the path.” 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.

“I started with brute force, picked an arbitrary root, ran a DFS to count reversals, then tried to re-run for every possible root.” 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.

“Pretty standard opener but I still fumbled the 'why it mattered' part.” The rest of the author's notes on Product Manager 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 just walk up the path and count character frequencies, which works but is way too slow if you think about the constraints.” 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 went straight into the data model and probably should've asked more clarifying questions first.” 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.