Uber Product Analyst candidates report a recruiter call, a hiring manager or SQL screen, and case-style rounds on marketplace metrics, funnels and experimentation. Here is how to prepare for each stage.
$117K
Avg. Base Comp
$143K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Three Product Analyst candidates describe the Uber process, and a recurring theme is to think like someone who already works inside a two-sided marketplace. One candidate was asked how to increase rider supply in a given market and was expected to use Uber-specific language, with concrete metrics for riders, drivers and the balance between them. Generic growth frameworks did not land.
Another candidate reports a case on a product funnel, covering what to measure and how to interpret changes in the numbers, plus behavioral prompts such as why Uber and why you are looking for a new role. A third candidate describes a more demanding loop: a 45-minute live screen with advanced SQL window functions and metric diagnostics, then a five-round onsite. It included a root-cause question about a sudden spike in rider cancellations in one city, experimentation questions on network effects, switchback tests, synthetic controls and CUPED, and a bar-raiser behavioral round about driving business impact and pushing back on product managers.
The experiences differ in depth and in outcome, so treat the more intensive loop as one possible version rather than the standard. Practice walking through ambiguous metric problems out loud, in a clear order. Be ready to explain when a standard A/B test breaks down in a marketplace. Also prepare project stories that show impact beyond writing queries. One candidate also mentions a possible take-home alongside the cases, so leave some time for that.
Synthesized from 5 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 question that stuck with me was how I would increase rider supply in a given market. That came up in the second round, and it was the moment the interview shifted from something I expected to be finance-heavy into a real product exercise. The first round was a recruiter call, and it was the easy part. The recruiter was friendly and informative, and walked me through what the role involved, which made the next step feel less like a gate.
The second interview was a set of mini case questions with interviewers who were not especially warm. They didn't seem very invested in the conversation, and I caught myself filling silences more than I wanted to. What caught me off guard was the expectation for precision. Reasonable answers in general growth language weren't enough. The recruiters had made it clear they wanted Uber-specific terminology, so I needed to talk about the marketplace the way the company does, not just in generic product-speak.
From what I've seen, this role leans heavily on analytics and can include a take-home alongside the cases, so budget time for that. I didn't get an offer. Looking back, I'd spend less time on general frameworks and more on how Uber's two-sided marketplace actually works, with concrete metrics for riders, drivers, and the balance between them. The interview was really testing whether I could think like someone already inside the business, and I didn't convince them I could.
Prep tip from this candidate
Be ready to answer market-growth cases like increasing rider supply in a city using Uber's own marketplace vocabulary and metrics for both riders and drivers. Interviewers expected precise, jargon-accurate answers rather than generic product frameworks.
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.
| Question | |
|---|---|
| Employee Salaries | |
| Button AB Test | |
| Bank Fraud Model | |
| Experiment Validity | |
| Download Facts | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Distance Traveled | |
| Weighted Keys | |
| P-value to a Layman | |
| Top 3 Users | |
| Google Maps Improvement | |
| Third Purchase | |
| Type-ahead Search | |
| Encoding Categorical Features | |
| Uber User Journey | |
| Hurdles In Data Projects | |
| Bloated Mid-Funnel | |
| Size of Joins | |
| Revenue Retention | |
| Christmas Dinner Ingredient Optimization | |
| Assumptions of Linear Regression | |
| Testing Price Increase | |
| Random Forest Explanation | |
| One Million Rides | |
| Random Weighted Driver | |
| Xgboost vs Random Forest | |
| Cancellation Fees | |
| Data Preparation for Imbalanced Data |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening recruiter call about their background, why they want Uber and whether they fit the Product Analyst role. One candidate says it also probed understanding of a two-sided marketplace and company values. It was described as friendly and straightforward.
One candidate reports a 60-minute hiring manager conversation about past work and product thinking. Another describes a 45-minute live coding screen with advanced SQL window functions and basic metric diagnostics. Which format you get may vary, so prepare for both.
Candidates report case questions on a user funnel, increasing rider supply in a market, and a spike in rider cancellations. Expect to structure your approach aloud, name the metrics you would pull and use marketplace vocabulary for both riders and drivers. A take-home may also appear, according to one candidate.
One candidate reports a five-round onsite with product sense, experimentation, applied modeling and a bar-raiser behavioral round. Another describes multiple onsite rounds mixing behavioral and analytical questions, with a Jam-style exercise. Topics may include switchback tests, synthetic controls, CUPED, imbalanced data and business impact.
