Candidates describe an Uber PM process of recruiter and hiring manager conversations, a case presented to a panel, often a JAM session, and cross-functional interviews, with marketplace tradeoffs recurring in the questions.
$175K
Avg. Base Comp
$300K
Avg. Total Comp
Not reported
Typical Rounds
4-8 weeks
Process Length
Uber PM candidates most often describe a recruiter or HR call, then a hiring manager conversation, then a case or presentation round and a broader loop. One candidate counted seven rounds, and end-to-end timelines range from about four weeks to about two months.
The JAM session shows up in several accounts. One candidate who received an offer said the prompt arrives a few days early and you prepare a strategy presentation for a panel of PMs and engineers. Others describe it as tiring and domain specific, focused on priorities and tradeoffs, with one JAM prompt about designing support for an autonomous vehicle.
Product questions lean on marketplace tradeoffs. Reported prompts include reducing ride cancellations, rider-driver matching, improving the driver experience, marketplace liquidity, launching Uber Train, and the KPIs you would track after a launch. The pattern is weighing riders, drivers and the business together rather than pitching features in isolation.
Hiring manager rounds can go deep. Candidates were asked to defend a past experiment, explain the business impact of a delivery, handle competing stakeholder priorities, or walk through their resume line by line. Later loops reportedly add engineering, data science and leadership interviews, including A/B testing versus pre-post analysis in one data science round. One candidate's take-home tested analytics and SQL before a panel presentation.
Outcomes vary. Several candidates described slow scheduling, about two weeks between interviews, or little feedback after final rounds, so ask your recruiter what comes next at each stage. Prepare three or four product stories with metrics, know those metrics cold, and rehearse the panel presentation aloud.
Synthesized from 27 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 process kicked off with an HR conversation where they walked me through the role and benefits package. That was straightforward enough, but then came the case presentations, which were the real test. I did a quick case with the director overseeing the role, followed by a more comprehensive case with the broader leadership team and their direct reports. The cases weren't incredibly complex, but the questions came fast and relentless. They weren't just asking for my answer—they were pushing hard on my reasoning, challenging my assumptions, and digging into why I'd made certain decisions. One case specifically focused on how I'd manage the rollout of a new onboarding feature, which required thinking through phasing, user impact, and cross-functional coordination. Throughout, I noticed the interviewers used a STAR-like structure to evaluate whether I had real experience backing up my points and could think critically in a structured way. They seemed more interested in understanding my perspective on past experiences and my critical thinking than in me having the "right" answer. The whole process moved quickly—the TA was genuinely helpful in coordinating everything smoothly. Still, despite the efficient logistics, the substantive rigor of the cases and the depth of questioning left me feeling uncertain. The difficulty wasn't in the complexity of the problems themselves, but in articulating decisions under pressure and demonstrating that I had both the experience and the reasoning to back them up.
Prep tip from this candidate
Prepare concrete examples using the STAR method where you can clearly articulate your reasoning and trade-offs on product decisions. For case questions around feature launches and user onboarding, focus on demonstrating both business acumen and structured thinking—they'll push hard on your assumptions, so anticipate follow-up questions on phasing, metrics, and cross-functional dependencies.
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
How would you assess the validity of the result?
| Question | |
|---|---|
| Employee Salaries | |
| Button AB Test | |
| Top 3 Users | |
| Download Facts | |
| WAU vs Open Rates | |
| User Experience Percentage | |
| Distance Traveled | |
| Size of Joins | |
| Google Maps Improvement | |
| Third Purchase | |
| Bank Fraud Model | |
| Encoding Categorical Features | |
| Uber User Journey | |
| Network Experiment Design | |
| Hurdles In Data Projects | |
| Bloated Mid-Funnel | |
| Revenue Retention | |
| P-value to a Layman | |
| Christmas Dinner Ingredient Optimization | |
| Testing Price Increase | |
| Random Forest Explanation | |
| Type-ahead Search | |
| One Million Rides | |
| Random Weighted Driver | |
| Xgboost vs Random Forest | |
| Cancellation Fees | |
| Uniform Car Maker | |
| Demand Metrics | |
| Assumptions of Linear Regression |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR call covering their background, why Uber, and the role. One candidate said the recruiter gave tips and clarification on what to expect. Expect to summarize your PM experience concisely, since later rounds tend to build on it.
Candidates describe conversations of roughly 30 to 45 minutes that can go deep on past work. Reported topics include an experiment run at a previous company, competing stakeholder priorities, a detailed resume walkthrough, and early product questions about improving the driver experience or reducing ride cancellations.
Some candidates report a case study or take-home presented to a panel. One assessment tested analytics and SQL and was followed by behavioral and product questions. Others were given product cases live, such as improving a favorite product or preparing for a launch. Panels pushed beyond surface-level answers.
Several candidates mention a JAM, where you get a prompt a few days in advance and pitch a strategy to PMs and engineers. Candidates describe it as focused on prioritization and tradeoffs, and one prompt involved designing support for an autonomous vehicle. Its placement in the loop appears to vary.
Later rounds reportedly include product design, engineering or tech lead interviews, data science, and leadership or behavioral chats. One candidate described a marketplace liquidity case and a data science round on A/B testing, and another had an extended data science discussion on experimentation. Some candidates waited without much feedback afterward.
