Uber interview notes, page 57 of 61

“My first instinct was to just iterate through logs and subtract child durations, but that falls apart fast with deeply nested calls.” 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.

“Spent probably too long on the data model upfront and had to rush the concurrency stuff later, which is honestly where the interesting problems live.” 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 knew this problem but still fumbled the explanation for like two minutes.” 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 user segments affected and tried to separate driver-side cancellations from rider-side ones because the root causes are completely different.” 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 is the kind of question that sounds easy until you're actually in it and realize you're trying to compress 18 months of work into 15 minutes without losing the thread.” The rest of the author's notes on Machine Learning Engineer interview at Uber, Onsite - Multi Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I jumped straight to revenue uplift and forgot to talk about the geo-restriction angle until they nudged me.” The rest of the author's notes on Data Scientist 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 much a sliding window or single-pass min-tracking problem.” 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 spent way too long on edge cases before I even had a working solution.” 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 monotonic stack part clicked pretty fast for me, standard next-smaller-element pattern.” 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 Dijkstra and that was the wrong direction to go down.” 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.