Plan Advance Ride Booking at Bolt: Target Riders, Dispatch, Metrics and Rollout
Company: Bolt
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager at Bolt, the ride-hailing company, and you are asked how you would build a feature that lets riders book a ride for a later time instead of requesting one immediately. Explain who the feature is for, what the first version includes for riders and drivers, how a booked ride actually gets a driver, how you would measure success, and how you would roll it out.
```hint The booking is a promise
An on-demand request either finds a driver or fails on the spot; a booked ride is a promise made hours ahead. Decide which trips make that promise most valuable to riders, then work out how dispatch keeps it when the time comes.
```
### Clarifying Questions
- Should I assume Bolt has no scheduling today, or am I improving a version that already exists in some markets?
- Is the main goal more completed trips, winning riders who currently book ahead with competitors or taxis, or new revenue such as a booking fee?
- Which ride categories are in scope: standard cars only, or also premium, larger and accessible vehicles?
- Does Bolt want to guarantee a driver for a booked ride, or offer best-effort matching with a clear fallback?
### What a Strong Answer Covers
- A target rider segment chosen with reasons, for example trips where a missed pickup is costly, rather than everyone who might plan ahead.
- The rider's booking flow: how far ahead they can book, the price shown at booking, reminders, changes and cancellation.
- How dispatch keeps the promise: when the request reaches drivers, what happens if nobody accepts, and the effect on drivers and on on-demand supply.
- Success metrics centered on reliable on-time pickups, with guardrails for on-demand service and cancellations.
- A rollout plan and the main risks: failed pickups, no-shows, pricing exposure and local rules.
### Follow-up Questions
- Ten minutes before a booked airport pickup, no driver has accepted. What should the product do, and what does the rider see?
- Would you lock the price at booking? Who absorbs the cost if demand surges at pickup time?
- How would you tell whether scheduled rides are new trips or trips riders would have taken on demand anyway?
Overview: A product strategy question about building advance ride booking for Bolt's ride-hailing app. It tests picking the riders who benefit most from scheduling, designing a booking and dispatch flow that keeps the pickup promise, setting pricing and cancellation rules, and choosing metrics for reliable on-time pickups.