Uber interview notes, page 14 of 61

“My first instinct was to just run a BFS for every query independently.” 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.

“Two-pointer sweep wasn't hard to get to, the intersection formula is just max of starts and min of ends, check that max <= min and you're done.” 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 the whole interview.” 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 know this model reasonably well so I wasn't panicking, but I fumbled the ordering a bit.” The rest of the author's notes on Machine Learning 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.

“High-frequency problem so I'd seen it before, which helped.” 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.

“Part one was fine, just iterate and pick the min of each adjacent pair, handle odd lengths by appending the last element.” 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 with brute force, scanning all four directions for each robot until hitting an X or the boundary.” 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.

“Recursive DFS was the obvious move and I went there immediately, which 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.

“Pretty much a union-find problem once you see 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.

“I rambled a bit here.” The rest of the author's notes on Product Manager interview at Uber, Onsite - Cross-functional / Panel round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.