Uber·Machine Learning Engineer·Onsite - Multi Round
Jul 2026
Went through the staff-level MLE loop at Uber, which is only two rounds: one focused on org scope and influence, the other a deep architecture walkthrough. The bar is genuinely different from senior; they're not looking for incremental improvements, they want you to show you redesigned the problem itself. Feedback after a rejection is basically nonexistent, so debrief yourself immediately.
- Walk me through a project you led recently in detail, including the architectural decisions and how the project was scoped.
- How do you measure your scope of influence at a staff engineering level, and how many teams or engineers have you actually impacted?
- What technical direction did you set on this project versus what direction were you given?
- Present a complex system you've built, covering the major subsystems, latency budget, model choices, and how failures are handled.
- What were the failure modes in this system and how did you handle on-call incidents related to it?
- What alternatives did you consider and reject when designing this architecture?
- What do you expect from a staff-level engineer on this team, specifically?
“This is the core of the first round and it runs longer than you'd expect.” The rest of the author's notes on Machine Learning 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.
View Post