Uber·Product Manager·Onsite - Product Sense / Strategy
- How would you integrate Uber Eats into the core Uber app?
“This is a meaty one if you let it be.”
Large Enterprises
Most of these Uber write-ups come from Software Engineers (407), then Data Scientists (78) and Machine Learning Engineers (65). The most reported rounds are the technical phone screen (387), the system design round (95), the product sense round (46) and the onsite coding round (23).
609 interview notes · updated Aug 2026
“This is a meaty one if you let it be.”
“Took me a while to see the binary search angle.”
“The naive approach is obvious, square everything and sort it, but that's O(n log n) and they pushed for better.”
“This is the big one.”
“The pressure to pick something genuinely different from what I'd already covered tripped me up a bit.”
“I went straight to backtracking and it felt fine.”
“I recognized this as basically LeetCode 855 but without the leave() part, which actually made it simpler.”
“I started with just a hashmap for counts which was fine, but I fumbled on the 'most recent single-hit' part for a bit.”
“Spent too long overthinking the random placement logic and not enough time on clean output formatting.”
“The core problem is basically course schedule, so I had seen it before.”