Low-Level Design at Flipkart frequently shows up as a hands-on machine-coding round rather than a whiteboard-only discussion — you're expected to actually write working class code for a booking, ticketing, or trading-style system, not just describe one. Interviewers probe schema extensibility and concurrency handling as much as the class diagram itself.
Design a system covering the core booking entities for an airline: searching flights, booking a ticket for a passenger, and managing fares. Cover entity modeling, a database schema, and a REST API surface for the booking operations.
Requirements to clarify first
- Is a booking one passenger on one flight, or can it hold several passengers and connecting legs under one PNR?
- How long may a seat stay held while the passenger is paying, and what happens to the hold if payment fails or times out?
- Are fares fixed per class, or do they move with demand and days-to-departure — and must a quoted fare be honoured for the whole checkout?
More LLD prompts Flipkart has asked recently
The class design, entity list, schema, concurrency strategy and full worked solution for these — plus the one above — are part of the Placement-Ready PYQ Kit.
2 more LLD prompts with full class designs in the full Placement-Ready PYQ Kit

