Uber interview notes, page 7 of 61

“Classic estimation question, but I fumbled the structure a bit.” 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.

“I stared at this for a bit and started thinking about sorting by reward1 descending, which was wrong.” 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'd done this kind of question before but never with an actual diagram component.” 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 to brute force it: for each k, slide a window of size k and check if the min is 1 and max is k with no gaps.” 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 to upsell mechanics, like bundling drinks or suggesting add-ons at checkout, 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 i+1 movement is obvious but the 'jump to any index ending in 3' rule threw me off at 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.

“The explosion detection part was fine, I flagged the cells in a separate pass so I wouldn't modify the board mid-scan.” 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.

“Already seen this one in the phone screen, so I finished it pretty fast and just asked to move on.” 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 energy-dependent walking cost is what makes this tricky.” 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 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.