High-Level Design (system design) rounds at Flipkart lean toward familiar consumer-product domains — trading platforms, streaming services, booking systems — rather than abstract templates. Interviewers reward a structured approach: requirements first, then a service split, a database choice per service, and how consistency is preserved where it actually matters.
Design the architecture for a stock-trading platform (Zerodha-style): user registration and auth, real-time stock price streaming, order management (buy/sell, limit/market orders), and portfolio and fund management, built to hold up around the peak-load stress point of market open/close.
Requirements to clarify first
- What is the latency budget for a price tick reaching the user's screen — a few hundred milliseconds is fine for retail, but is anything stricter expected?
- Does the platform run its own order matching, or does it route orders to an external exchange and only manage the lifecycle around them?
- Which operations must be strictly consistent (fund debits, order state) and which can be eventually consistent (portfolio charts, notifications)?
More system design prompts Flipkart has asked recently
The full architecture, service breakdown, database choices and scaling discussion for these are part of the Placement-Ready PYQ Kit.
1 more system design prompt with a full architecture writeup in the full Placement-Ready PYQ Kit