
Uber Data Analyst candidates report recruiter and hiring-manager conversations followed by SQL and analytics work, including product metrics, conversion investigation, experimentation, and communication of findings.
$131K
Avg. Base Comp
$136K
Avg. Total Comp
3 rounds
Typical Rounds
2 months
Process Length
Uber Data Analyst candidates describe an interview that blends background discussion with practical analytics judgment. One candidate reported three main rounds: a recruiter conversation, a hiring-manager interview, and a technical, analytics-focused round. Another described a recruiter call, technical work, and a team-leader conversation, with two technical tasks during the process. SQL appears in both reports, while the detailed product-analysis case comes from one candidate.
For the recruiter and manager conversations, be ready to connect your background to product analytics and explain a prior analysis project, including how you presented the result. The technical evidence includes SQL proficiency questions and a transaction-table exercise requiring a previous-quarter spend calculation, date-range definition, aggregation, ranking, and tie handling.
One reported product case asked the candidate to investigate a drop in rider booking conversion. The discussion covered funnel stages, segmentation, metrics, possible confounders such as seasonality or pricing changes, and how to communicate a recommendation to a PM. That report also described experiment-design follow-ups on randomization, sample size, significance, and guardrail metrics.
One reported end-to-end process lasted about two months; timelines can vary.
Synthesized from 3 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.
{"experience":"The hardest part for me was that the questions kept coming back to the same theme from different angles: how do you think about metrics, and how do you defend your analysis? My process started with a recruiter call where they asked the usual why this role and why Uber, but they also spent time walking me through the interview flow so I knew what to expect. After that, I had a panel round with two technical-style interviews. One was coding-focused and mixed Pandas with easy DSA, and the other centered on product metrics and A/B testing. The metric questions were very practical, like what could explain stable SLA but rising customer complaints, how I’d identify operational bottlenecks in a dataset, what metrics I’d track for a delivery or logistics system, how I’d segment users for analysis, and how I’d define a north-star metric. They also wanted me to talk through root cause analysis and how I’d validate insights before presenting them, and they asked everything one by one rather than in a rapid-fire style. The final stage was another panel, this time four interviews back to back. Two were behavioral and past-experience heavy, with a lot of tell me about a time questions. The other two were more technical: one DSA medium coding round and one more A/B testing discussion. Compared with other companies, the process felt shorter overall, but the final round had a take-home component that took longer than I expected. In that part, I had to walk through my findings and defend my logic, which made it feel less like a presentation and more like a live review of how I reasoned. Overall it was pretty standard, but the emphasis on metrics, experimentation, and explaining tradeoffs was very real. I ended up getting the offer, and I’d say the best prep is to practice explaining metric changes clearly, especially around complaints vs. SLA, and to be ready to defend a take-home analysis line by line. outcome":"Accepted offer outcome_color":"green prep_tip":"Practice explaining metric shifts like stable SLA but rising complaints, and be ready to defend a take-home analysis step by step. Also review Pandas plus easy-to-medium DSA and basic A/B testing since those came up directly in the panels."}
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 | |
|---|---|
| Experiment Validity | |
| Download Facts | |
| User Experience Percentage | |
| Button AB Test | |
| Weighted Keys | |
| Top 3 Users | |
| Third Purchase | |
| Bank Fraud Model | |
| Maximum Profit | |
| Encoding Categorical Features | |
| Distance Traveled | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Google Maps Improvement | |
| Type-ahead Search | |
| Random Forest Explanation | |
| Sort Strings | |
| Uber User Journey | |
| WAU vs Open Rates | |
| Hurdles In Data Projects | |
| Bloated Mid-Funnel | |
| Dijkstra implementation | |
| Uniform Car Maker | |
| Assumptions of Linear Regression | |
| Dice Rolls From Continuous Uniform | |
| Testing Price Increase | |
| Random Weighted Driver | |
| Type I and II Errors | |
| Production Model Monitoring |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter conversation covering their background, interest in Uber, and alignment with product analytics. One candidate also described the recruiter as supportive throughout a longer process.
Candidates report a later conversation with a hiring manager or team leader that may explore analytical background, a prior data-analysis project, and how findings were presented to stakeholders.
Candidates report SQL proficiency questions and analytics-focused technical tasks. Reported examples include ranking quarterly client spend, investigating booking-conversion decline, designing an experiment, and following a required JSON output structure.