Metrics question

Imagine you are a PM of Uber's search map. How would you calculate its success?

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

Metrics design: can you build a metric tree for a specific product surface (search/map) that ties to the business outcome (completed rides), including guardrails.

How to approach it

  1. Define the user job: find a pickup point or destination quickly and accurately via search/map.
  2. Set the north-star metric: search-to-ride-request conversion rate.
  3. Build supporting metrics: search success rate (result selected without re-searching), time-to-select, and map load/accuracy issues.
  4. Add guardrails: search latency and rate of 'no results found', since a fast but inaccurate search hurts trust.
  5. Segment by context: new vs unfamiliar addresses, dense urban vs suburban, since search difficulty varies a lot.
  6. Tie back to the business outcome: completed rides and driver-passenger match time.

What a strong answer includes

Common mistakes

Likely follow-up questions

More metrics questions

More questions from Uber

Learn the skill behind it

Chapters of the AI PM course that teach what this question tests.

Preparing for a specific role?

Book summaries for this kind of question

Browse all 4,000+ questions in the bank