Booking.com India-Style Machine Coding Round: Format, Tips & Practice Problems
Written and reviewed by Sahil Srivastav
Reservation platforms coordinate guest intent, property availability, cancellation rules, and partner updates. Rounds in the style of Booking.com India test whether those concepts remain consistent when requests repeat or arrive late.
This page uses original Gronex repositories and style-based framing.
What a Booking.com India-style machine coding round looks like
Expect an availability or reservation service with a time box, legal states, and one cancellation policy. Deliver a small runnable domain module.
Follow-ups tend to add overbooking prevention, partial cancellation, or a partner callback. Keep inventory ownership and event identity explicit.
A clear state machine plus a few boundary tests is more useful than a full search stack.
How you’re evaluated
Availability accuracy
A held or booked unit is not offered as available.
Cancellation policy
Refund and expiry rules are deterministic.
Callback safety
Repeated partner events do not move a reservation twice.
Partner isolation
A partner update cannot mutate another property or booking.
Common mistakes that fail this round
- Reading availability without reserving it.
- Applying cancellation windows from the wrong clock.
- Accepting callbacks without an event identity.
- Mixing partner and guest state.
- Ignoring partial cancellation.
Quick tips for the room
- Use a reservation identity.
- Define the cancellation boundary.
- Separate partner events from commands.
- Test a duplicate callback.
How to prepare
Build a reservation service with availability, hold, confirmation, and cancellation.
Use the linked repositories to drill event ordering and money release.
Practice problems in the Booking.com India-style round format
Each is a real backend repository with a failing test suite — the same working-code standard the round applies. Open the brief and read the full problem, no signup required.
FAQ
Were these Booking.com India questions?
No. They are Gronex originals in the style of reservation rounds. Gronex is not affiliated with Booking.com.
How do I avoid overbooking?
Make the availability check and hold one atomic business operation.
How should callbacks be handled?
Deduplicate by event identity and validate booking and partner scope.
What belongs in the demo?
One booking, one expiry or cancellation, and one repeated callback.
Related
Gronex is not affiliated with, endorsed by, or sponsored by Booking.com India. All company names and trademarks belong to their respective owners. The problems on this page are Gronex originals written in the style of such interview rounds — not actual interview questions from Booking.com India.