Uber interview notes, page 55 of 61

“This is a DP problem but it's easy to go down the wrong path if you start thinking about it greedily.” 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 question has a lot more surface area than it looks.” 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 is essentially 'design your own past work from scratch in front of us' and it's way harder than a made-up system design prompt because you can actually be wrong.” 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.

“The basic rate limiter wasn't bad but the follow-ups stacked up fast.” The rest of the author's notes on Software Engineer interview at Uber, Onsite - Multi Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The first part is basically a warmup but it sets a trap for the second part.” 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've seen this question floating around so I wasn't totally blindsided, but actually writing it cleanly under pressure is a different story.” 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 was deceptively open-ended.” 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 question is basically seven questions duct-taped together.” 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.

“This one took me a while to even understand what they were asking.” 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.

“I went with the classic event-based sweep: split each interval into a +1 at start and -1 at end, sort the events, then scan.” 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.