Uber interview notes, page 8 of 61

“My first instinct was to just iterate over all x and pick the minimum, which works but the O(N^2) felt gross and I said so out loud which I think was fine.” 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.

“Knew this one cold so I jumped straight to the linear scan approach, tracking the running minimum and updating max profit as I go.” 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 part that tripped me up was they wanted all five pieces: original design, competing goals, options considered, why I pivoted, and the outcome.” 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 just do a BFS and track the first and last node at each level, which is roughly right, but I kept fumbling the dedup condition.” 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 the first minute trying to figure out if they wanted me to be aspirational or grounded and I picked wrong.” 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.

“I knew it was some kind of DP but spent way too long thinking about it person-by-person before realizing you should iterate over hats instead, since there are only 40 hats but up to 10 people.” 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 naive BFS solution comes to mind immediately but they pushed back on the space usage right away.” 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 had a decent story here but I fumbled the measurable impact part.” 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.

“I got the general idea pretty fast, uniform region becomes a leaf, otherwise split into four quadrants and recurse.” 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.

“Started okay.” 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.