Design a Car Rental Booking Frontend
Try the prompt first
Design the booking frontend for a car rental company. Customers search by pickup and return branch, local times and driver age, compare vehicle classes, add extras and confirm. Prices change, classes sell out and holds expire while they decide. Assign authority among URL state, the booking draft, server offers and holds. Explain how branch-local time, hold expiry, conflicts and accessible timers keep bookings honest.
Constraints
- Server offers set every price and fee.
- Times stay branch-local.
- Holds expire on the server clock.
Challenge summary
Design a car rental booking frontend where server offers own price and rental days, pickup times stay in the branch zone, and expiring vehicle holds recover without losing customer input.
What you'll practice
- Separate shareable search criteria, cached offers, the booking draft and server-owned holds.
- Keep pickup and return times in the branch time zone from the URL to the request.
- Run an expiring vehicle hold on the server clock with an accessible warning and extension.
- Recover from price changes, sold-out classes and lost responses without duplicate holds.
What Premium unlocks
Premium unlocks the expiring-hold worked example, the typed rental contracts, the hold and reservation API semantics, and the sold-out recovery walkthrough.
Free related practice
Public interview reports: Taro (January 2024), Code360 (May 2025) · Tesla frontend interview questions · Agoda frontend interview questions
Upgrade to FrontendAtlas Premium to access this system design scenario. Already upgraded? Sign in to continue.