Design Ride Pricing & Payments
A Backend Engineer technical screen asked this in August 2026, the same month and role as a live robotaxi map prompt. The weight sits on idempotency, reconciliation and failure handling, ahead of matching supply to demand. Expect the interviewer to steer.
Picture the moment that makes this hard. A ride ends on a busy Friday night. The payment service asks the provider to capture $23.40, and the request times out after ten seconds. Did the money move? The service has no way to tell yet. Retry carelessly and the rider may pay twice. Give up and the ride is never paid for. Most of the round goes on making that moment safe, and on proving afterwards that every ride's money ended up where the books say. Pricing matters in a narrower way. The fare the rider saw when booking has to be the fare the charge is based on, even if the city's rates change mid-ride.
ZooxPremium lesson · System design round
The Zoox design, worked end to end.
- The API and data modelSystem design
- The design, drawn out1 diagram
- 6 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports
Zoox interview guideKnow what Zoox asks before you walk in.
21 coding · 4 system design · 30 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.