Uber commute shuttle MVP: scoping a San Francisco to South Bay pilot and app mockup
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager at Uber, and the company is considering a shuttle service for people who commute between San Francisco and the South Bay. How should Uber design it? Your answer must include a UI mock of the core experience (a rough wireframe drawn on a whiteboard or in text is enough), and it should make clear what the MVP is meant to prove and how tightly its scope is drawn.
```hint Scope before screens
A corridor this long has several rider groups, two directions and many possible stop patterns. Decide which single question the first version must answer, and for whom, before you sketch anything.
```
### Clarifying Questions
- Is the first version meant to prove rider demand and repeat use, the economics of filling a pooled vehicle over a long distance, or appetite from employers that would pay for their staff?
- Should riders be individuals paying for themselves, or employees whose company buys the seats, the way some large South Bay employers already run private shuttles?
- Does Uber run the vehicles itself or contract an existing charter operator, and is the route fixed with set stops or flexible?
- Which trips matter first: San Francisco to the South Bay in the morning, the opposite direction, or both legs of a round trip?
### What a Strong Answer Covers
- A stated MVP hypothesis with explicit in-scope and out-of-scope lists for this corridor (riders, direction, hours, stops).
- A chosen commuter segment, justified against how people make this trip today (driving, rail, employer shuttles, solo ride-hail) and the pain each option leaves.
- A UI mock that covers the whole commute, not just checkout: finding and booking a seat, the return trip, getting to the stop, live tracking and boarding.
- Operating choices (vehicles, stops, schedule, reliability, seat economics) and how they shape the rider experience.
- Pilot metrics with guardrails, plus a decision rule for expanding, changing or stopping the service.
### Follow-up Questions
- Morning departures fill up, but the evening return runs half empty. What do you change in the product and the schedule?
- A South Bay employer offers to buy seats for its staff if the shuttle adds a stop at its campus. Do you accept during the MVP?
- How do you keep the shuttle from simply moving profitable solo trips on this corridor onto cheaper seats, and should you even try?
Overview: A product design case asking how Uber could launch a shuttle for commuters traveling between San Francisco and the South Bay. It tests MVP goal setting and scope control, rider segmentation, a sketched UI mock of the booking and ride-day flows, and pilot success metrics.