Uber interview notes, page 43 of 61

“This is basically topological sort dressed up in a packaging scenario, which I recognized pretty fast.” 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 went with Kahn's algorithm because BFS feels more intuitive to explain out loud than recursive DFS.” 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 knew the mechanics well enough but stumbled a bit explaining the 'why' before the 'how'.” 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 went with inflation squeezing consumer discretionary spending and gig worker supply shifting as unemployment rates change.” 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.

“This one sprawled in a way I wasn't ready for.” 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.

“This was the entire interview.” 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 jump rule is what got me.” 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 union-find, which was right, but I went straight to checking every pair and the interviewer let me code it up before pointing out the scale.” 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 knew the hash map part immediately but fumbled explaining why the doubly linked list of frequency buckets actually gives you O(1).” 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 is a meaty one.” 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.