Uber Business Analyst interview typically runs 4 rounds: online assessment, phone screen, formal interview, final case presentation. Timeline is usually a few business days to several weeks, and the process is structured and fairly conversational.
$111K
Avg. Base Comp
$213K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Uber is unusually good at making the early conversation feel approachable, but that friendliness should not be mistaken for a soft bar. A recurring theme is that interviewers quickly test whether you can explain why Uber, why this role, and why now in a way that sounds grounded rather than generic. We’ve seen multiple candidates get screened on communication, role alignment, and even language fit before any heavy analytics discussion really starts, which tells us Uber is listening for clarity and maturity from the outset.
The real separator, though, is the analytical depth once the process turns technical. Multiple candidates mentioned that SQL becomes meaningfully harder than expected, with window functions showing up as a common pressure point. We also saw a strong emphasis on reasoning over memorization: in the case-style discussion, interviewers pushed on methodology, alternative scenarios, and how the candidate would think through a data exercise for Uber Eats or a marketplace problem. That pattern suggests they care less about a polished final answer and more about whether you can defend your logic when the problem gets messy.
What makes this process distinctive is the combination of crisp communication and practical judgment. Our candidates consistently describe a panel that wants to see whether you can translate analysis into a decision, not just run the analysis itself. If you sound vague, over-explain, or can’t connect your work to Uber’s marketplace context, that tends to stand out quickly.
Synthetized from 2 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Uber process.
The process was pretty structured and, in my case, started with an online assessment before moving into a phone screen. After that I had a formal interview, then one last round. The early stages felt straightforward and mostly conversational, with the recruiter and interviewer asking basic motivation questions like why I wanted the role and why Uber. It also seemed like they were moving through a lot of post-grad candidates, so the vibe was less intimidating than I expected.
The technical part came later and was the real filter. My second round was the hardest because the SQL got noticeably more difficult, especially around window functions. The interviewer was helpful and kept the conversation moving, but it was still a step up from the first round. The final round was more of a case study and presentation format, where I had to walk through a data exercise and present my approach to a panel. They asked follow-up questions on methodology and alternative scenarios, so it wasn’t just about the answer but how I reasoned through the problem. Overall the process was fairly simple in structure, but the final case presentation and the SQL round were the parts to prepare for most carefully. I didn’t get the offer in the end.
Prep tip from this candidate
Practice SQL window functions under time pressure, and be ready to explain your methodology and alternate scenarios in a case-study presentation. Also prepare concise answers for why Uber and why this role, since those came up early and often.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Uber
Write a query to select the top 3 departments with at least ten employees and rank them according to the percentage of their employees making over 100K in salary.
| Question | |
|---|---|
| Download Facts | |
| User Experience Percentage | |
| Distance Traveled | |
| P-value to a Layman | |
| Third Purchase | |
| Hurdles In Data Projects | |
| Sort Strings | |
| Testing Price Increase | |
| Assumptions of Linear Regression | |
| Christmas Dinner Ingredient Optimization | |
| Random Weighted Driver | |
| Uber User Journey | |
| Uniform Car Maker | |
| Demand Metrics | |
| Multicollinearity in Regression | |
| Type I and II Errors | |
| Uber Eats Customer Experience | |
| MLE vs MAP | |
| Density to Cumulative | |
| Stakeholder Communication | |
| Random Forest from Scratch | |
| Drink Production Allocation | |
| Two Cars | |
| Your Strengths and Weaknesses | |
| Merchant Acquisition | |
| Understanding Dynamic Pricing Strategy | |
| Extra Delivery Pay | |
| Apartment Pricing | |
| Incentive Scheme |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a short recruiter conversation over Zoom or by phone, sometimes scheduled via email or LinkedIn. This stage is mostly structured and conversational, covering your background, motivation for applying, interest in Uber, and basic fit for the Business Analyst role.
Some candidates begin with an online assessment before speaking with the team. This appears to be an early filter before live interviews, likely used to screen for analytical ability and readiness for the role.
The next step is a phone screen that can include analytics and SQL questions. In the experiences shared, this was where the technical bar became more noticeable, especially with harder SQL topics like window functions.
After the technical screen, candidates move into a more formal interview that is still partly conversational but more evaluative. Interviewers may ask about your analytics experience, role alignment, and in some cases language proficiency or other job-specific fit questions.
The final round is a case-style exercise where you walk through a data problem and present your approach to a panel. Expect follow-up questions on methodology, tradeoffs, and alternative scenarios, so the focus is on reasoning and communication as much as the final answer.