
Uber Data Scientist candidates report a process centered on SQL or Python work, statistics, experimentation, causal inference, product cases, and discussion of prior projects.
$176K
Avg. Base Comp
$253K
Avg. Total Comp
5-7 rounds
Typical Rounds
2-4 weeks
Process Length
Uber Data Scientist interviews reported here combine practical analysis with marketplace and product reasoning. Candidates describe an online assessment or early technical screens that can cover SQL, Python or pandas, statistics, and project discussion. SQL examples range from joins and grouping to window functions; coding is paired with explaining the choices behind prior work.
Experimentation and causal reasoning recur throughout the reported process. Candidates were asked to design A/B tests, define metrics, reason about sample size, and work through causal-inference tradeoffs. Case prompts use Uber contexts such as service expansion, order or driver assignment, ETA presentation, and churn, but the preparation priority is to make a defensible measurement plan: define the objective, name key metrics, surface constraints, and explain how results would guide a decision.
Several reports also describe behavioral or hiring-manager conversations around resumes, conflicts, and stakeholder work. Final stages vary: one candidate presented a churn case study, while another completed a three-interview loop involving a hiring manager, bar raiser, and experimentation-focused technical round. A candidate who cleared a Staff Data Scientist onsite reported that hiring froze before an offer or team match could be finalized. Treat the sequence below as a preparation framework rather than a fixed format.
Synthesized from 11 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 technical screen was more approachable than I expected, but I still didn’t make it past that stage. I started with a recruiter screen focused on general questions about my background, past projects, and technical experience. The recruiter was straightforward, and the conversation felt like a standard fit check rather than a technical evaluation.
The next round combined SQL, Python, and statistics. The questions were in the easy-to-medium range, and the interviewer was great to work with. I was also asked to discuss my prior experience and projects, so it was important to explain not just what I had done but the technical choices behind it. My process ended after this round. The recruiter scheduled a follow-up call and gave me clear feedback that matched my own sense of where my interview performance fell short.
For preparation, I would make sure you can comfortably handle straightforward SQL, Python, and statistics questions while clearly walking through the technical details of your past projects. Have a concise answer ready for the project you are most proud of, including your specific contribution and the reasoning behind your approach.
Prep tip from this candidate
Be ready to discuss a project you are most proud of in technical detail, alongside easy-to-medium SQL, Python, and statistics questions. The technical screen also covered past experience, so practice connecting your project decisions to the underlying technical concepts.
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 | |
| Revenue Retention | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Google Maps Improvement | |
| Random Forest Explanation | |
| Type-ahead Search | |
| Sort Strings | |
| Random Weighted Driver | |
| Uber User Journey | |
| Hurdles In Data Projects | |
| Cancellation Fees | |
| Dijkstra implementation | |
| Assumptions of Linear Regression | |
| Dice Rolls From Continuous Uniform | |
| Testing Price Increase | |
| Drawing Balls From Bin |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment or first screen that may combine SQL, statistics, simple math, or a Python task. Some accounts also include an early conversation about background, role fit, and technical experience.
Candidates report one or two technical screens with SQL or Python/pandas work, statistics, and discussion of prior projects. Prepare to explain both the result of a project and the reasoning behind its technical decisions.
Candidates report cases on promotions, ETA, batching, campaign launches, or marketplace operations. These discussions typically ask for goals, metrics, an experiment design, and treatment of issues such as spillovers or uncertainty.
Candidates report final loops that may include behavioral or hiring-manager interviews alongside metrics, experimentation, causal-inference, or econometrics cases. Resume walkthroughs, stakeholder examples, and structured business reasoning may appear here.
One candidate reported a team-matching discussion after four onsite rounds, while other reports end after a case-study presentation or final loop. The exact close-out step and timing vary across candidates.