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.
- Cover a microservices split across user, order, portfolio, funds, market-data, and notification concerns.
- Justify a database choice per service rather than one database for everything.
- Cover how strong consistency is preserved for money-moving operations inside an otherwise event-driven design.
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