Design a New Feature for a Ride-Sharing App

What interviewers evaluate

• Do you consider BOTH sides of the marketplace (riders and drivers)?
• Do you anchor on a goal (growth, retention, safety, driver supply) before designing?
• Do you scope to a segment and a specific pain rather than a generic feature?
• Do you weigh marketplace side effects (does helping riders hurt driver supply)?
• Do you define success metrics including guardrails?

A framework to structure your answer

1. Clarify the goal - are we optimizing rider growth, retention, safety, driver supply, or margin? Restate it.
2. Pick a side & segment - choose rider or driver and a segment; name their acute pain.
3. Marketplace check - consider how a change on one side affects the other.
4. Solution - design for the pain, with the marketplace interaction in mind.
5. Prioritize & sequence - impact vs effort, and what to ship first.
6. Metrics - primary metric + guardrails (e.g. don't harm ETA, safety, or driver earnings).

Try structuring your own answer first, then reveal a strong worked example.

Common variants

• Design a feature to improve driver retention.
• Design a safety feature for a ride-sharing app.
• How would you reduce rider cancellations?

Pitfalls to avoid

• Designing only for riders and ignoring driver-side effects (or vice versa).
• Picking a feature with no clear goal behind it.
• Ignoring marketplace economics (e.g. price guarantees that destroy margin).
• No rollout sequencing - launching a supply-dependent feature where supply is thin.
• Vanity metrics (feature usage) without business guardrails.

Likely follow-ups

• What breaks if driver supply is unreliable in a market?
• How would you price this to protect margin?
• What's the smallest pilot that would de-risk the idea?