Uber interview notes, page 3 of 61

“I jumped straight into the matching service and kind of forgot to scope the problem first.” 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.

“Pretty standard opener but I fumbled it more than I expected.” The rest of the author's notes on Software Engineer 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 fumbled the opening on this one.” 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.

“I had a decent example ready but I spent too long on the setup and barely got to what I actually did.” 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.

“My first instinct was to brute force check all subarrays for each k and I started explaining that before catching myself.” 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 started with a per-room sorted list of intervals and binary search to find gaps, which felt reasonable.” 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.

“Started fine but didn't reach for a TreeMap on my own.” 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.

“They kept following up.” 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.

“Classic 0/1 knapsack.” 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 started with the class hierarchy and it went fine, Vehicle and Spot and Ticket are all pretty natural.” The rest of the author's notes on Backend 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.