
Uber Data Analyst interview typically runs 4 rounds: recruiter call, technical interview, team leader conversation, and final panel. It usually takes about 2 months and can include take-home tasks or back-to-back panels.
$137K
Avg. Base Comp
$167K
Avg. Total Comp
4-5
Typical Rounds
4-8 weeks
Process Length
We’ve seen Uber lean hard into analysts who can do more than compute a number — they need people who can explain why a metric moved, what else could be driving it, and how confident they are in the conclusion. Multiple candidates described questions that kept circling back to the same core: defend the analysis. That showed up in practical prompts like stable SLA but rising complaints, identifying bottlenecks in logistics data, and choosing the right north-star metric for a delivery system. The common thread is that Uber seems to value analysts who can connect product behavior to operational reality, not just report on surface-level trends.
A recurring theme is the company’s preference for structured thinking under ambiguity. Our candidates report that interviewers often asked them to walk through root cause analysis, segment users thoughtfully, and validate insights before sharing them. Even the more unusual prompt about returning a customer feedback response in a strict JSON format points to the same signal: they care about precision, clarity, and whether you can follow a defined analytical contract. In other words, it’s not enough to have the right answer — you need to show the path you took to get there.
We also see a strong emphasis on experimentation and communication. Several experiences mention A/B testing discussions alongside behavioral questions about past projects and stakeholder communication, which suggests Uber is looking for analysts who can translate technical findings into decisions people will trust. The candidates who did best were the ones who could speak naturally about tradeoffs, explain how they’d validate a result, and stay consistent when challenged from different angles.
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.
{"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 | |
|---|---|
| Download Facts | |
| Experiment Validity | |
| User Experience Percentage | |
| Weighted Keys | |
| Third Purchase | |
| Bank Fraud Model | |
| Encoding Categorical Features | |
| Distance Traveled | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Random Forest Explanation | |
| Hurdles In Data Projects | |
| Sort Strings | |
| Uber User Journey | |
| Uniform Car Maker | |
| Testing Price Increase | |
| Assumptions of Linear Regression | |
| Dice Rolls From Continuous Uniform | |
| Random Weighted Driver | |
| Type I and II Errors | |
| Data Preparation for Imbalanced Data | |
| Cancellation Fees | |
| Demand Metrics | |
| Multicollinearity in Regression | |
| Density to Cumulative | |
| Uber Eats Customer Experience | |
| Drink Production Allocation | |
| MLE vs MAP | |
| Normal Distribution Sample |
Synthesized from candidate reports. Individual experiences may vary.
An initial call with a recruiter covering the usual background questions, including why you want the Data Analyst role and why Uber. The recruiter also walks through the interview flow so you know what to expect, and in some cases may discuss eligibility requirements early.
A technical round focused on core data analyst skills such as SQL, Python/Pandas, and basic data problem solving. Candidates reported questions ranging from JSON-format response tasks and customer-feedback analysis to coding with easy DSA and discussing a past analysis project.
A panel stage with multiple interviews covering product metrics, A/B testing, and analytical thinking. Questions are practical and scenario-based, such as diagnosing stable SLA but rising complaints, identifying operational bottlenecks, defining north-star metrics, segmenting users, and explaining how to validate findings before presenting them.
The final stage is a longer panel with a mix of behavioral and technical interviews. Candidates described two behavioral interviews focused on past experience and communication, plus technical discussions including medium-level DSA and another A/B testing or metrics deep dive; one experience also mentioned a take-home component that had to be defended line by line.