Uber interview questions

The onsite process consisted of multiple rounds covering algorithms, machine learning coding, system design, a deep dive on past projects, and behavioral/leadership. Overall, the process was well-structured and interviewers were engaged. The system design and behavioral rounds focused on real-world ML systems, product thinking, and cross-functional collaboration. The ML-focused discussions emphasized modeling choices, feature design, and architecture at scale. The algorithms and ML coding rounds placed a strong emphasis on correctness, problem framing, and clear communication. In particular, interviewers looked for candidates to validate assumptions, handle edge cases, and fully execute solutions rather than just outline approaches. For ML coding, there was an expectation to translate ideas into working implementations and reason through mathematical details where relevant. The “previously solved problem” round focused on depth over breadth. While discussing prior work, interviewers probed for detailed trade-offs, design decisions, and reasoning rather than high-level overviews. Takeaways: Strong emphasis on correctness and end-to-end execution in coding rounds Clear communication and structured problem-solving are critical Depth in trade-off discussions is important, especially for senior roles System design and behavioral rounds are aligned with real-world ML systems and collaboration Overall, the interview bar felt high, particularly around execution and depth of understanding. The recruiting team did not follow up regularly.

2 coding phases + 1 system design + 1 behavior. It followed the Big Tech interview process. The interviewers were nice and supportive, I really enjoyed the process. You must be sharp at your coding skills for sure, they are very technical.