Uber Business Analyst candidates report recruiter and hiring-manager conversations, followed in some processes by SQL or business-case work and a presentation. Prepare project stories, structured recommendations, and clear success metrics.
$124K
Avg. Base Comp
$156K
Avg. Total Comp
3-5 rounds
Typical Rounds
2-4 weeks
Process Length
Uber Business Analyst interviews reported here range from conversational early screens to analytical cases and presentation work. The recurring preparation theme is turning analysis into a business decision. Candidates describe recruiter conversations about background, motivation, and role fit, followed by hiring-manager or team discussions that probe past projects, business judgment, and how candidates approach situational problems.
Technical depth varies by team. One candidate completed an Excel analysis and prepared two commercial presentations before discussing the work with a panel. Other reported prompts involved evaluating an Uber Eats market expansion, responding to a client issue, improving a business scenario, or explaining a strategic decision. These exercises tested whether candidates could organize ambiguous information and turn their reasoning into a practical, business-facing recommendation.
Prepare two or three project stories covering the business problem, your strategy, the information you used, the actions you took, and the result. For a case, clarify the problem, state reasonable assumptions, identify what you would investigate, make a commercially grounded recommendation, and explain how you would judge whether it worked. Reports show meaningful team-level variation, so ask the recruiter what assessment format to expect and prepare to explain why this particular Business Analyst role fits your experience and goals.
Synthesized from 13 candidate 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 most surprising part of this process was how different the second conversation felt from the recruiter screen. My initial recruiter interview went extremely well: I was told I was a great fit and that the next step would be a discussion with the department head to go into the opportunity in more detail. Instead, the next interview was with someone already doing the job, with no explanation for the change.
That conversation focused on general background questions rather than a technical or case-style assessment. The interviewer repeatedly questioned why I was applying for a role she believed I was overqualified for. She also spoke negatively about her workload and her overall experience in the position, which made the interview feel unusually candid but also confusing given the positive recruiter screen.
Afterward, I did not receive any update, including after I followed up by email. I ultimately did not receive an offer. I would go in ready to clearly explain why this specific Business Analyst role fits your goals and how your background matches the level, since that became a central point of discussion. Also, keep expectations flexible about who you will meet in the next round, because the stated interview plan changed without notice.
Prep tip from this candidate
Prepare a concise explanation for why you want this Business Analyst role and why its level is the right fit, especially if your background could be viewed as overqualified.
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 | |
|---|---|
| Button AB Test | |
| Top 3 Users | |
| Third Purchase | |
| Experiment Validity | |
| Download Facts | |
| WAU vs Open Rates | |
| User Experience Percentage | |
| Distance Traveled | |
| Revenue Retention | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Sort Strings | |
| Hurdles In Data Projects | |
| Christmas Dinner Ingredient Optimization | |
| Testing Price Increase | |
| Assumptions of Linear Regression | |
| Random Weighted Driver | |
| Uber User Journey | |
| Bloated Mid-Funnel | |
| Cancellation Fees | |
| Uniform Car Maker | |
| Demand Metrics | |
| Multicollinearity in Regression | |
| Dasher Payment Structure | |
| Drink Production Allocation | |
| Type I and II Errors | |
| Uber Eats Customer Experience | |
| Rider Acquisition Target | |
| MLE vs MAP |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation covering their background, interest in Uber and the role, previous tools or client-facing work, and practical fit. Be ready to explain a relevant project succinctly and why the role's level fits your goals.
Candidates report manager interviews centered on prior experience, difficult decisions, competing priorities, stakeholder situations, and project walkthroughs. Answers may be strongest when they connect the business problem, strategy, execution, and delivered result.
Some candidates report SQL or BigQuery scenarios, while others describe business cases involving client issues, market expansion, or operational metrics. Typically, explain assumptions, the data you would examine, the recommendation, and how you would measure success.
Later stages may include an Excel or take-home case presentation, panel follow-ups, or cross-functional conversations. Candidates report questions about methodology, alternatives, technical experience, and communicating an analysis as a business-facing recommendation.
