Zomato system design interview
Design appears early: even SDE-I and intern loops include a rate limiter, notification or ordering design with schema work. Senior loops lean on HLD and probe Kafka partitions, Redis and database indexing in depth.
| Progress | Question as candidates report it | Next step |
|---|---|---|
| Rate limiter (fixed window, sliding window, token bucket)Rate limiter | Watch | |
| Notification system with dedup and cooldownsNotification system | Watch | |
| Online food ordering systemFood delivery | Watch | |
| Nearby restaurant discoveryWalkthrough being added | Coming soon | |
| Real-time support chatWalkthrough being added | Coming soon | |
| Order API counting orders in the last X minutesWalkthrough being added | Coming soon | |
| Rewards system for ZomatoWalkthrough being added | Coming soon | |
| Calendar like Google CalendarWalkthrough being added | Coming soon |
Which levels get a design round
How to answer any design question: the LADDER method · How the design round is scored by level
Questions people ask
When does Zomato ask system design?
A design round is part of the loop at SDE 1 (SDE-I), SDE 2 (SDE-II), Senior Software Engineer (SDE 3) (SDE-III / Senior Software Engineer). Design appears early: even SDE-I and intern loops include a rate limiter, notification or ordering design with schema work. Senior loops lean on HLD and probe Kafka partitions, Redis and database indexing in depth.
What system design questions does Zomato ask?
Rate limiter (fixed window, sliding window, token bucket); Notification system with dedup and cooldowns; Online food ordering system; Nearby restaurant discovery; Real-time support chat; Order API counting orders in the last X minutes; Rewards system for Zomato; Calendar like Google Calendar.