Uber Business Analyst interviews typically start with a short recruiter screen and a situational hiring-manager or team-lead conversation; some candidates then face a harder SQL round and a final case study or take-home presentation.
$99K
Avg. Base Comp
$113K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Uber's Business Analyst interviews generally open with a short recruiter screen focused on your background, why Uber, and what drew you to the role. One candidate's Zoom screen lasted about 15 minutes and included a question on data analytics experience, while the recruiter also explained the team structure. The next step is usually a hiring-manager or team-lead conversation that leans situational rather than technical. Candidates were asked:
When the process goes deeper, the SQL round and the final case are the parts to prepare for most. One candidate described a second round where the SQL got noticeably harder, especially around window functions. That was followed by a case study presented to a panel that probed methodology and alternative scenarios. Another candidate had a take-home presentation with a few days to prepare and was asked which three operational metrics would measure the success of a new-city launch. A third candidate's final case was built on a real problem the team was facing.
Expect underspecified prompts too. One hiring manager answered clarifying questions on a street-light scenario with "just assume." Practice stating your assumptions and showing how they change your recommendation.
Logistics can be fluid. Candidates reported the role changing mid-process, a different interviewer than planned, executive scheduling shifts, and no follow-up after the final conversation. Confirm the role's scope at each stage, and prepare a crisp story about why this specific role fits your level.
Synthesized from 17 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.
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 | |
| Size of Joins | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Groups of Anagrams | |
| Sort Strings | |
| Network Experiment Design | |
| Hurdles In Data Projects | |
| Christmas Dinner Ingredient Optimization | |
| Assumptions of Linear Regression | |
| Testing Price Increase | |
| Random Weighted Driver | |
| Uber User Journey | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Bloated Mid-Funnel | |
| Cancellation Fees | |
| Uniform Car Maker | |
| Demand Metrics | |
| Multicollinearity in Regression | |
| Dasher Payment Structure | |
| The Pirate’s Hunt |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a brief recruiter conversation covering background, why Uber, and interest in the role. One candidate's Zoom screen lasted about 15 minutes, touched on data analytics experience, and included an overview of the team structure. Another process began with an online assessment before the phone screen.
This conversation is usually situational rather than technical. Candidates were asked how they would handle a client issue, how they would improve a business in a scenario, and how they had communicated advanced analytics insights to upper management. One candidate was given an underspecified street-light scenario and told to "just assume" details. Another met a current team member instead of the planned department head.
One candidate described a technical round where the SQL became noticeably harder than earlier stages, especially around window functions. Another candidate's process included a technical round between the behavioral round and the final presentation.
The final stage is often a case. One candidate presented a data exercise to a panel that asked about methodology and alternative scenarios. Another had a few days to prepare a take-home presentation and was asked which three operational metrics would measure a new-city launch. A third worked through a case based on a real problem the team was facing.
One candidate's planned final panel was affected by executive availability, and a follow-up conversation with another executive was arranged. That discussion was described as strategic and conversational, including questions on office-location preference and notice period. Updates after final rounds may not come quickly.
