Real, anonymized candidate journeys from recent (2025) Zomato SDE-1 and SDE-2 loops in India — round by round, including what was asked, how the candidate approached it, and the outcome.
One complete journey, start to finish
Round 1 — DSA + System Design
A DSA problem (minimum number of swaps to sort an array of consecutive integers 1..n, solved via cycle detection in O(n)), followed by a system-design discussion on sketching a schema for scheduling promotional banners with frequency-tracking tables.
Round 2 — Project Deep-Dive + LLD + DSA
A deep dive into a past project, then low-level design of a restaurant menu configuration system (modeling configurable size, crust, and topping combinations with pricing), followed by a DSA optimization problem: recommend a dish price falling between the 1/3rd and 2/3rd percentile of historical pricing, solved using two heaps.
Round 3 — Managerial
A relaxed conversation with the hiring manager about motivation, career goals, and culture fit.
Key takeaway: Practice designing schemas for real product features (promotions, menu configuration) alongside pure DSA rather than only abstract system-design templates — Zomato's rounds pull design questions directly from its own product surface. This candidate received a same-day offer after round 3.
More real interview journeys
The first round of each journey below is shown in full; the rest of each candidate's journey — every remaining round, verbatim — is part of the Placement-Ready PYQ Kit.
Single Technical Round
Started with conceptual infra questions — why Redis achieves high performance despite being largely single-threaded and how it scales, then how to optimize Kafka consumer throughput and handle consumer lag. Moved into a SQL exercise: given orders moving through five states, write queries to fetch the latest state per order within a one-hour window while excluding already-delivered orders, plus a discussion on indexing at scale. Closed with a machine-coding exercise to implement the Snake and Food game with O(1) movement per tick, requiring a data-structure trade-off discussion (deque vs. array) for handling growth when food is eaten.
Key takeaway: Even a single generalist SDE-2 round can go deep into infra internals (Redis, Kafka) alongside SQL and machine coding — don't prepare only algorithms. Despite covering every topic asked, this candidate was ultimately rejected, a reminder that breadth alone doesn't guarantee depth was demonstrated well enough on each one.