Design a Hotel Search Page Frontend for Several Teams
Try the prompt first
Design the frontend of a hotel search page. Date, city and guest inputs sit on top, filters on the left and result cards on the right. A million people a day use it, and several teams ship parts of it on their own schedules. Decide where the search state lives and how the page splits into deployable units. Say what the CDN and the browser cache, and how a regression is traced to one deploy.
Constraints
- The URL is the source of truth.
- Each team deploys its unit on its own schedule.
- Prices change every few minutes.
Challenge summary
Design a hotel search page frontend where the URL owns the search, several teams deploy their units behind one shell, and a regression is traced to one deploy.
What you'll practice
- Split the page by ownership into a shell and three units with a typed contract.
- Keep the search and the filters in the URL and derive every unit from it.
- Ignore a late reply for a superseded query and cache prices with a short lifetime.
- Trace a regression to one unit build with vitals and funnel events.
What Premium unlocks
Premium unlocks the worked example of a filter change during a slow fetch, the typed unit contracts, the search API semantics and the release playbook.
Free related practice
Public interview reports: LeetCode (July 2026) · Agoda frontend interview questions
Upgrade to FrontendAtlas Premium to access this system design scenario. Already upgraded? Sign in to continue.