Top 20 System Design Interview Questions for Indian Startups
If you are applying for an SDE-2, SDE-3, or engineering leadership role at Indian unicorns and hyper-growth startups (think Swiggy, Zomato, Cred, Zerodha, or Razorpay), the System Design round will be the most critical phase of your interview process.
Unlike Data Structures and Algorithms (DSA) rounds which have definite right or wrong answers, System Design is open-ended. Interviewers are not just looking for a functional architecture; they are evaluating your ability to handle scale, deal with ambiguity, make trade-offs, and design for the unique constraints of the Indian market (e.g., patchy internet, massive scale bursts during festivals).
In this article, we cover the top 20 System Design interview questions asked by Indian tech startups, categorized by the core architectural challenges they present.
Category 1: High-Concurrency & Burst Traffic Systems
Indian startups frequently deal with massive spikes in traffic. Whether it's an IPL match on Hotstar, a flash sale on Flipkart, or the lunch-hour rush on Swiggy, designing for burst traffic is a must-have skill.
1. Design a Flash Sale System (e.g., Flipkart Big Billion Days) Core challenge: Handling millions of concurrent read/write requests without crashing, managing inventory accurately to avoid overselling, and implementing queuing mechanisms (like Kafka) to process orders asynchronously.
2. Design a Live Leaderboard System (e.g., Dream11 during IPL) Core challenge: Updating scores in real-time for millions of concurrent users. You will need to discuss Redis Sorted Sets, WebSockets for real-time updates, and handling node failures without losing game state.
3. Design a Ticket Booking System (e.g., BookMyShow) Core challenge: Handling concurrency and locking. If two users try to book the exact same seat simultaneously, how do you handle the database locks? (Hint: Distributed locks, isolation levels in SQL).
4. Design a Video Streaming Service (e.g., Hotstar/JioCinema) Core challenge: Content Delivery Networks (CDNs), video transcoding pipelines, adaptive bitrate streaming, and handling regional traffic spikes.
Category 2: Hyper-Local & Geo-Spatial Systems
Companies relying on physical logistics and deliveries heavily test candidates on geo-spatial architectures.
5. Design a Food Delivery App (e.g., Swiggy/Zomato) Core challenge: Matching algorithms, tracking delivery partners in real-time, handling state machines (Order Placed -> Preparing -> Picked Up -> Delivered), and calculating ETAs based on traffic data.
6. Design a Ride-Hailing Service (e.g., Ola/Uber) Core challenge: Designing a quadtree or utilizing geohashes for efficient proximity searches. How do you find the nearest 5 drivers to a rider within milliseconds?
7. Design a Quick Commerce Logistics System (e.g., Zepto/Blinkit) Core challenge: Dark store inventory management, extremely low-latency order routing, and optimizing picker-to-rider handoffs.
Category 3: Financial & Payment Systems
Fintech is booming in India. Mistakes in these systems don't just result in bad user experience; they result in regulatory action and massive financial loss.
8. Design a Payment Gateway (e.g., Razorpay/PayU) Core challenge: Ensuring ACID compliance, idempotency (ensuring a user isn't charged twice for the same click), handling third-party banking API failures, and reconciliation processes.
9. Design a Digital Wallet (e.g., PhonePe/Paytm) Core challenge: Ledger design, distributed transactions across microservices (Saga Pattern/Two-Phase Commit), and high availability.
10. Design a High-Frequency Trading Platform (e.g., Zerodha) Core challenge: Extremely low-latency architectures, handling high-throughput market data streams, and ensuring strict ordering of buy/sell requests.
Category 4: Social Media & Communication
11. Design a Chat Application (e.g., WhatsApp) Core challenge: WebSockets/long-polling, message ordering, read receipts, and offline message storage. How do you design a system that works efficiently on low-bandwidth networks?
12. Design a News Feed System (e.g., ShareChat/Instagram) Core challenge: Feed generation algorithms, handling the "Celebrity Problem" (fanout-on-write vs fanout-on-read), and caching strategies.
13. Design a Notification System Core challenge: Delivering millions of push notifications, SMS, and emails reliably without duplicates. Rate limiting and prioritization are key discussion points here.
Category 5: E-Commerce & Cataloging
14. Design an E-Commerce Product Search (e.g., Myntra) Core challenge: Implementing Elasticsearch, handling fuzzy matching, facet filtering, and updating the search index near real-time as inventory changes.
15. Design a Recommendation Engine Core challenge: Collaborative filtering vs content-based filtering, batch processing via Hadoop/Spark, and serving recommendations with low latency using Redis.
16. Design a Review and Rating System Core challenge: Handling high write-throughput for popular products, calculating average ratings efficiently without running expensive database aggregations on every load.
Category 6: Infrastructure & Platform Services
These questions test your understanding of foundational systems that other developers build upon.
17. Design a URL Shortener (e.g., Bitly) Core challenge: Generating unique short IDs at scale, handling massive read throughput, and deciding on data retention policies. (This is a classic warm-up question).
18. Design a Rate Limiter Core challenge: Implementing algorithms like Token Bucket or Leaky Bucket using Redis to protect APIs from DDoS attacks or runaway microservices.
19. Design an API Gateway Core challenge: Routing, authentication, rate limiting, and analytics collection without adding significant latency to requests.
20. Design a Distributed Web Crawler
Core challenge: Designing the URL frontier, ensuring you don't crawl the same page twice, respecting robots.txt, and preventing infinite loops.
How to Approach These Questions in an Interview
In an Indian startup interview, the interviewer is looking for a structured thought process. Use the following framework to ace the round:
Step 1: Clarify Requirements (5 mins)
Never jump straight into drawing boxes. Ask questions to narrow the scope.
- Functional Requirements: What exact features are we building? (e.g., "For the chat app, are we supporting group chats or just 1-on-1?")
- Non-Functional Requirements: What is the expected scale? Is it read-heavy or write-heavy? Do we need strong consistency or is eventual consistency acceptable?
Step 2: Back-of-the-Envelope Estimation (5 mins)
Calculate expected traffic (Queries Per Second - QPS), storage requirements, and bandwidth. This proves your design decisions are based on math, not guessing.
Step 3: High-Level Design (10 mins)
Draw the core components: Client, Load Balancer, API Gateway, Application Servers, and Database. Walk the interviewer through the basic flow of data.
Step 4: Deep Dive and Scaling (20 mins)
This is where the interview is won or lost. Address the bottlenecks you identified.
- Database Scaling: Sharding, replication, SQL vs NoSQL.
- Caching: Where can we put Redis/Memcached to reduce database load?
- Asynchronous Processing: Introducing Kafka or RabbitMQ for heavy background tasks.
Step 5: Trade-offs and Bottlenecks (5 mins)
No system is perfect. Discuss Single Points of Failure (SPOFs) and how you would monitor the system (metrics, logging, alerting).
Conclusion
System Design interviews at top Indian startups are rigorous, but they are also highly predictable. The fundamental building blocks—Load Balancers, Caches, Message Queues, and Databases—remain the same. Success lies in knowing how to arrange these blocks to solve specific business problems while balancing scale, cost, and complexity. Review these 20 questions, practice whiteboarding, and you'll be well-prepared for your next big interview.
