Uber interview notes, page 44 of 61

“The recursion itself isn't bad once you see it, but I fumbled the stopping condition 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.

“I picked a story I thought was solid but halfway through realized I was talking way too much about the technical details and not enough about my actual role in getting the team there.” The rest of the author's notes on Software Engineer 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.

“Spent the first few minutes just trying to scope it out because 'reporting dashboard' could mean a dozen different things.” 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.

“This was basically the whole interview in one prompt.” 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.

“The single-square part was fine, just pick random x and y within bounds.” 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 to just sort the array somehow, but that misses the point entirely since you need to count or minimize actual move operations.” 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 where I actually had to think.” 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 the kind of question where you think you're done after sketching the classes and then they hit you with 'what about buses?' I hadn't pre-baked the consecutive-slot scan and it showed.” 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.

“Got through it in about 25 minutes which felt okay.” 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 top-down first, which in hindsight was probably the wrong call.” 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.