Design Ride-Hailing for the Zoox Fleet
An engineering manager loop in 2023 asked for ride-hailing "for the Zoox fleet," and a backend onsite in October 2025 had a ride-hailing design. The 2025 round tested geospatial indexing and matching, real-time state, consistency and fault tolerance, which is a fair map of where the depth will go.
On paper this is the Uber question. A Zoox engineer said in October 2026 that the company's design rounds are "domain focused, won't be like design a Uber/Slack/etc." The prompt survives that comment because the fleet changes it. Uber's matcher makes an offer and waits for a driver to accept. Here nobody accepts. The system picks a car and tells it where to go, so a match is a command. Zoox also owns the supply. Every car's battery, position and idle time is the system's problem, including the hours when nobody is riding. And the scale shifts. The system tracks one company's fleet, so the location stream is small. The hard parts are choosing which car serves which rider, making sure a car never ends up with two rides, and knowing what's true when a car drops off the network in the middle of a trip.
ZooxPremium lesson · System design round
The Zoox design, worked end to end.
- The API and data modelSystem design
- The design, drawn out1 diagram
- 4 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.