Uber interview notes, page 53 of 61

“The view tracking part is where I spent most of my energy and probably where I should have been more careful about tradeoffs.” 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 went straight for the obvious stuff first: population density, smartphone penetration, existing transport infrastructure.” The rest of the author's notes on Software Engineer 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 went straight into frameworks and probably over-indexed on TAM sizing before actually anchoring on what Uber's core strengths are.” 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.

“This was the whole interview basically.” 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.

“Felt pretty comfortable with the base case but the follow-up threw me off.” The rest of the author's notes on Software 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.

“I knew BFS but initially reached for Dijkstra out of habit.” 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 just loop through every room and every interval inside it, which works but is obviously brute force.” 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 two pointers and I think that's right, but I fumbled the pair-counting logic initially.” 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 key thing nobody tells you upfront: BFS over routes, not stops.” 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 hit me sideways.” 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.