Zomato's system-design rounds are built around hyperlocal, real-time constraints: live order tracking, restaurant search and ranking by pincode, surge pricing during rain or peak demand, and ordered notifications at dinner-time scale.
Design the live order-tracking system that shows a customer their delivery partner moving on a map in real time. What are the write and read paths at peak dinner load?
Think of your answer first, then reveal how to structure it.
In 2026 interviewers care less about textbook diagrams and more about how you handle high-frequency location writes, demand-supply imbalance, and correctness of the customer's order timeline. Strong candidates separate the signal from the policy and are explicit about trade-offs like update frequency versus battery and cost.
Recruitment process
Online coding assessment or resume shortlist
Technical coding round on DSA and problem-solving
System-design round on a hyperlocal, real-time service
Hiring-manager round on depth, trade-offs, and ownership, then offer
Interview rounds
Round 1 (60 min): coding round on data structures and algorithms
Round 2 (60 min): system design of a real-time service such as live tracking or restaurant search and ranking
Round 3 (45-60 min): design deep-dive plus behavioral, focused on trade-offs and correctness under load
Real-Time Estimate-First framework
Start from load estimates (orders, riders, ticks per second at dinner peak), then design write and read paths separately, then defend the trade-offs
Practice questions
01
Design the live order-tracking system that shows a customer their delivery partner moving on a map in real time. What are the write and read paths at peak dinner load?
IntenseZomato system design centres on hyperlocal, real-time constraints: high-frequency GPS writes, geospatial fan-out, and dinner-peak spikes. Expect probes on location update frequency vs. battery/cost trade-offs.
How would you design the restaurant search and ranking service so results reflect delivery time, availability, and personalisation for a given pincode?
Design a surge/dynamic-pricing engine for delivery fees during rain or peak demand. How do you avoid oscillation and keep it explainable?
IntenseZomato loves demand-supply imbalance problems. Strong answers separate the signal (demand, rider availability) from the policy (caps, smoothing) and address fairness/explainability.
Design the notification system that tells a customer their order is confirmed, being prepared, picked up, and arriving. How do you guarantee ordering and avoid duplicate pushes?
The typical Zomato recruitment process has 4 stages: Online coding assessment or resume shortlist → Technical coding round on DSA and problem-solving → System-design round on a hyperlocal, real-time service → Hiring-manager round on depth, trade-offs, and ownership, then offer.
Zomato typically conducts 3 interview rounds: Round 1 (60 min): coding round on data structures and algorithms; Round 2 (60 min): system design of a real-time service such as live tracking or restaurant search and ranking; Round 3 (45-60 min): design deep-dive plus behavioral, focused on trade-offs and correctness under load.
HireStepX recommends the Real-Time Estimate-First framework for this type of interview: Start from load estimates (orders, riders, ticks per second at dinner peak), then design write and read paths separately, then defend the trade-offs.
Zomato system design centres on hyperlocal, real-time constraints: high-frequency GPS writes, geospatial fan-out, and dinner-peak spikes. Expect probes on location update frequency vs. battery/cost trade-offs.
Zomato loves demand-supply imbalance problems. Strong answers separate the signal (demand, rider availability) from the policy (caps, smoothing) and address fairness/explainability.
Live delivery tracking on a map, restaurant search and ranking, surge or dynamic delivery pricing, and a reliable order-status notification system, all framed around real dinner-peak load.
Very. Expect probes on GPS write frequency versus battery and cost, geospatial fan-out, and how you keep the customer's order timeline correctly ordered and free of duplicate pushes.
Yes. Begin with rough numbers for orders, active riders, and location updates per second at peak, then let those estimates drive your data-structure and storage choices.