Metrics question

What are product success metrics for the Uber Split Fare and how you measure it?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Metrics fluency, building a metric tree for a specific niche feature and picking the right success and guardrail metrics.

Clarify the goal of Split Fare, is it rider retention, group ride growth, or reducing payment friction for shared trips.
Identify the primary user segments, groups of friends, coworkers commuting together, and families.
Define the north star metric, e.g. percent of group rides that use Split Fare successfully.
Build a metric tree: awareness of the feature, activation (first use), completion (payment collected from all riders), and repeat use.
Add guardrail metrics, such as payment dispute rate or time to collect all payments, to catch a broken experience.
State how you would segment results by group size and relationship type to find where adoption is weakest.

Distinguishes activation from completion, since a rider might start a split but not everyone pays, which is the real failure mode.
Proposes a concrete guardrail, e.g. percent of splits with at least one unpaid rider after 24 hours.
Ties the metric back to business value, reduced payment friction increases group ride frequency and driver utilization.
Gives an illustrative benchmark, e.g. targeting 90 percent full payment completion, marked as an assumption.

Only naming usage volume without a completion or quality metric.
Ignoring the multi-party nature of the feature, one rider's behavior affects others.
Not segmenting by group size or relationship type.

How would you improve completion rate if it were low.
What would you do if Split Fare use is high but drivers complain about payment delays.
How would you segment this metric across markets.