Uber Data Scientist candidates report SQL/Python work, experimentation and causal-inference cases, marketplace metrics, project discussion, and behavioral interviews. Reported loops range from three to seven rounds.
$176K
Avg. Base Comp
$253K
Avg. Total Comp
3-7 rounds
Typical Rounds
2-4 weeks
Process Length
Uber Data Scientist interviews reported here emphasize applied analysis over a purely algorithmic screen. Experiment design and causal reasoning recur most often: candidates describe cases about surge pricing, service expansion, ETA changes, feature launches, and order or driver assignment. Prepare to define a decision metric, identify threats to validity, choose an appropriate design, and explain how you would investigate failed or unexpected experiment results.
SQL and Python are also frequent components. Reported SQL work includes joins, grouping, common table expressions, window functions, and timestamp-oriented analysis. Python tasks include sorting a list, straightforward implementation, and plotting a normal curve with a provided function. Practice explaining your reasoning as you work, because follow-up discussion may connect technical execution to precision and recall, product impact, data quality, or experiment validity.
Several candidates describe project or resume conversations alongside technical work, followed in longer loops by behavioral, hiring-manager, or bar-raiser discussions. Have a concise account of your contribution, technical choices, and how you handled ambiguity, conflict, or stakeholders. Some reports also describe econometrics and causal-inference questions involving pricing or observational data, including endogeneity and methods such as difference-in-differences or synthetic control.
Reported formats vary by team and seniority, so use these recurring themes to prepare rather than expecting every stage.
Synthesized from 15 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 useful part of the process was how closely the technical questions reflected Uber’s actual marketplace problems. I came in through a colleague who thought I would be a good fit, and my first conversation was a fairly casual call with the hiring manager. We discussed my background and the role without making the interaction feel overly formal.
The next round was technical and centered on experimentation and product thinking. I was asked how I would measure the effect of surge pricing on driver retention, so the challenge was not just proposing a metric but thinking through how pricing changes could affect driver behavior over time. I also had to design an A/B test for a new Uber Eats recommendation feature. The statistics discussion included how I would reduce variance between the control and treatment groups, which made it important to understand experimentation beyond the basic setup. There was also an estimation question about the number of Uber trips taken in San Francisco on a typical weekday. I had practiced that exact style of company-specific estimate beforehand, so it was a nice confidence boost rather than a surprise.
The process ended with a behavioral interview focused more on how I work and communicate. I received an offer and accepted it. Overall, my experience was straightforward and welcoming, with questions that stayed close to Uber’s products rather than becoming purely abstract.
Prep tip from this candidate
Practice framing experiments around Uber-specific marketplace effects, especially driver retention, recommendation systems, and variance reduction between treatment and control. Also rehearse a structured estimate of weekday trip volume in a city such as San Francisco.
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 | |
| Distance Traveled | |
| Button AB Test | |
| Weighted Keys | |
| Top 3 Users | |
| Third Purchase | |
| Maximum Profit | |
| Bank Fraud Model | |
| Encoding Categorical Features | |
| WAU vs Open Rates | |
| Sum to N | |
| Network Experiment Design | |
| Revenue Retention | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Google Maps Improvement | |
| Random Forest Explanation | |
| Type-ahead Search | |
| Random Weighted Driver | |
| Sort Strings | |
| Uber User Journey | |
| Hurdles In Data Projects | |
| Xgboost vs Random Forest | |
| Cancellation Fees | |
| Production Model Monitoring | |
| Dijkstra implementation | |
| Assumptions of Linear Regression |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report different entry points: some began with an online assessment covering SQL, statistics, or modeling, while others started with a recruiter or hiring-manager discussion of background and fit. A few processes moved directly into a technical screen, so the initial format may vary.
Candidates report SQL problems involving joins, filters, grouping, and window functions, plus Python or pandas work. Some screens also discuss prior projects, statistics, classification modeling, or applied coding; the reported difficulty ranges from straightforward data manipulation to an algorithmic graph problem.
Candidates frequently report experiment-design cases tied to pricing, promotions, recommendations, ETA, retention, batching, or marketplace operations. Prompts may require defining metrics, accounting for spillovers, evaluating results, or explaining causal-method tradeoffs rather than only naming an A/B test.
In longer reported processes, final interviews included behavioral or resume walkthroughs, hiring-manager and bar-raiser conversations, and additional technical or case rounds. Candidates describe being asked to explain collaboration, conflicts, stakeholder work, and the practical impact of analytical decisions.
