Uber·Machine Learning Engineer·Onsite - System Design / Architecture
Jun 2026
ML system design round at Uber for an MLE role. The whole session was a single deep-dive into building a destination autocomplete system, and it went pretty far into the weeds on ranking, latency, and personalization tradeoffs.
- Design an ML system that predicts and ranks destination suggestions in the Uber app as a user types the first few characters into the search bar.
- What features would you use in the ranking model, and would you go with a gradient-boosted model or a neural ranker?
- How would you handle cold-start for new users who have no trip history?
- What offline and online metrics would you use to evaluate this system, and how do they relate to each other?
- How do you think about the privacy and personalization tradeoff in a system like this?
“This is the whole question, basically.” The rest of the author's notes on Machine Learning 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.
View Post