Uber interview notes, page 21 of 61

“The part nobody warned me about: the prompt transcript is graded.” 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 straight to the obvious stuff, security lines, boarding delays, and kind of lost the thread on what Uber could actually own versus what's just the airport's problem.” 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 question is basically five questions stapled together.” 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 scan each subregion naively every time, which works but gets slow on bigger grids.” 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 palindrome condition is the part that trips you up first.” 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.

“My first instinct was to just simulate it, sum up the total capacity per index and compare to nums[i].” 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.

“My first instinct was a heap and I was pretty confident about it.” 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.

“Routine opener.” 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 in thinking this was a simple 'tell me a win' question and kind of fumbled the prioritization angle.” The rest of the author's notes on Product Manager 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 instinct was plain Dijkstra but then the stop constraint throws a wrench in it because you can't just track visited nodes the usual way.” 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.