Metrics question
How will you double the Uber Pool revenue?
- Microsoft
- Metrics
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests building a metric-driven growth plan for a specific product line, requiring the candidate to decompose revenue into concrete, actionable levers.
How to approach it
- Break Uber Pool revenue into its components: number of pool rides, average fare per pool ride, and take rate, since doubling could come from any combination.
- Segment riders: price-sensitive commuters who'd use Pool if wait and detour times were acceptable, versus riders who default to UberX and never consider Pool.
- Identify the biggest known barrier to Pool adoption: longer pickup and detour times compared to a solo ride, which discourages trial and repeat use.
- Propose a lever to grow ride volume: reduce match wait time and detour penalty through better real-time matching algorithms, directly addressing the top adoption barrier.
- Propose a lever to grow fare or take rate: dynamic Pool pricing that reflects real-time match likelihood, capturing more value on high-match-probability routes.
- Define the plan as targeting both volume and per-ride economics, with a guardrail that rider satisfaction (measured by repeat Pool usage) doesn't drop as volume grows.
What a strong answer includes
- Decomposes revenue into volume, fare, and take rate instead of proposing a single vague growth idea.
- Identifies detour and wait time as the specific, well-known adoption barrier for pooled rides, grounding the plan in a real constraint.
- Uses illustrative numbers as assumptions: assume Pool rides are currently 15% of total rides in dense urban markets, with matching improvements able to lift that meaningfully.
- Adds a guardrail on rider satisfaction, since pushing volume by degrading the ride experience would hurt long-term retention.
Common mistakes
- Proposing only a price increase without addressing the volume side of the equation.
- Ignoring the detour and wait-time barrier, which is the central known friction point for pooled rides.
- Not adding any guardrail against a volume push hurting rider experience or driver earnings.
Likely follow-up questions
- How would you improve the real-time matching algorithm specifically?
- What's the trade-off between more matches and longer individual trip times?
- How would you measure rider satisfaction with Pool specifically?
More metrics questions
- How would you measure the performance and health of a Netflix Original?Microsoft · Metrics · Hard
- You are a PM for LinkedIn Trust Team. A number of senior influencers at LinkedIn have complained that they receive innumerable spam connection requests and they threaten to leave the platform or launch a tirade against LinkedIn. What do you do?Amazon · Metrics · Hard
- You notice a spike in the number of user-uploaded videos on your platform in June. What do you think is the cause, and how would you test it?Microsoft · Metrics · Medium
- Pick any favorite product of your choice . Find any one functionality you find missing in the same product which would make life simpler.Microsoft · Metrics · Easy
- How would you measure the success of Zoom?Google · Metrics · Medium
- How will you deliver a project during the unseen pandemic situation with a contract already signed?Microsoft · Metrics · Hard
More questions from Microsoft
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 2: Data fluency: SQL, logs, and reading the truth yourself
- Chapter 14: Get the job: the AI PM interview loop