Food & delivery · Gurugram

Zomato.

Food delivery and restaurant discovery, plus District (going-out and ticketing) and Hyperpure supplies, under Eternal.

its questions lean on

notifications at scale
rate limiting
order and delivery-partner data models
Kafka and Redis internals
ads and pacing

The rounds, as candidates describe them

Technical roundsTwo technical interviews mixing DSA, CS fundamentals, resume deep dive and system design.source ↗
Culture fitA final round with a senior engineering leader, usually in person.source ↗

Reported by candidates

From public interview write-ups; each links its source.

Design a Notification SystemSystem design
IP-06 · Design a Notification System →W06 · DAY 01 · Notification Platform — Problem Understanding & High-Level Design →W06 · DAY 04 · Scale, Reliability & Edge Cases →reported in:LeetCode Discuss · Zomato/District SDE-1 interview experience (2026) ↗LeetCode Discuss · Zomato / Eternal SDE-1 interview experience (2026) ↗
Design a Rate LimiterSystem design
IP-02 · Design a Rate Limiter →W01 · DAY 03 · Rate Limiting at Scale →LLD-03 · Design a Rate Limiter →reported in:LeetCode Discuss · Zomato SDE off-campus interview experience (2025) ↗LeetCode Discuss · Zomato / Eternal SDE-1 interview experience (2026) ↗
Design an ad pacing service for restaurant campaignsSystem design
IP-16 · Design an Ad Click Aggregation System →W01 · DAY 03 · Rate Limiting at Scale →reported in:LeetCode Discuss · Nugget by Zomato SDE-1 interview experience (2025) ↗
Design a peer-to-peer chess gameSystem design
W05 · BOSS · Multiplayer Game Matchmaking System →reported in:LeetCode Discuss · Nugget by Zomato SDE-1 interview experience (2025) ↗
Design the schema for delivery partners and ordersSystem design
SQ-17 · Swiggy Food Delivery →W06 · BOSS · Food Delivery Order System →reported in:LeetCode Discuss · Zomato / Eternal SDE-1 interview experience (2026) ↗
Design a paginated transaction-history APISystem design
W08 · DAY 05 · Query Layer and Optimization →W01 · DAY 01 · Partitioning Deep-Dive →reported in:LeetCode Discuss · District by Zomato SDE-1, round 2 (2026) ↗
Design an API that counts orders in the last X minutesSystem design
IP-16 · Design an Ad Click Aggregation System →W08 · DAY 02 · Streaming vs Batch Processing →reported in:LeetCode Discuss · Zomato SDE off-campus interview experience (2025) ↗
Design a Snake gameLow-level design
no lesson for this one yetreported in:LeetCode Discuss · Zomato SDE-2 interview experience (2026) ↗
Why is Redis fast while being single-threaded?Concept
IP-11 · Design a Distributed Cache →W04 · DAY 01 · Caching Patterns →reported in:LeetCode Discuss · Zomato SDE-2 interview experience (2026) ↗
What happens when Kafka consumers lag behind producers?Concept
W03 · DAY 03 · Backpressure and Flow Control →W03 · DAY 01 · Queue vs Stream →reported in:LeetCode Discuss · Zomato SDE-2 interview experience (2026) ↗
How do Kafka partitions affect ordering and consumer idempotency?Concept
W03 · DAY 01 · Queue vs Stream →W02 · DAY 02 · Idempotency in Practice →reported in:LeetCode Discuss · District by Zomato SDE-1, round 1 (2026) ↗

Likely, from what they build

Our pick, not a report: questions that fit Zomato's products.

Design a Food Delivery SystemSystem design
SQ-17 · Swiggy Food Delivery →W03 · BOSS · Event-Driven Food Delivery Order System →
Design a Proximity ServiceSystem design
IP-13 · Design a Proximity Service →
Design a Ticket Booking SystemSystem design
SQ-16 · BookMyShow Seat Booking →LLD-05 · Design a Movie Ticket Booking System →

Study path

Every lesson the questions above point to, once, in order.

Company names and logos are trademarks of their owners, shown only to identify each company. This course isn't affiliated with or endorsed by any of them.