Uber interview notes, page 34 of 61

“Spent the first few minutes just trying to scope it down because stock trading can mean a hundred different things.” 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.

“This is the kind of question where a vague answer kills you fast.” The rest of the author's notes on Data Scientist 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.

“My first pass was a queue, just append timestamps on hit() and prune anything older than 300 seconds on getHits().” 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 tree structure part clicked pretty fast for me, parent pointers, store subtree sums, update ancestors on insert.” 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.

“The part that got me was the feasibility check.” 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.

“The add operations are straightforward enough but the referral one trips you up because updating the referrer's revenue means their position in any sorted structure changes.” 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 just brute force DP, loop over every valid jump from each position.” The rest of the author's notes on Software Engineer interview at Uber, Online Assessment (OA) round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The bottleneck part is what trips you up first.” 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 with a GenAI agent project because I thought it showed breadth: business context, system design, data pipeline, eval, post-launch tradeoffs.” 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.

“This is a meaty one.” 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.