Zomato Interview Process 2026 — Rounds, Tips & Questions

Customer support tickets increased by 40% after a recent product release. How do you approach root cause analysis as a BA?

Design Zomato's delivery time prediction system. Before placing an order, show "Delivers in 35 minutes". The estimate must account for restaurant preparation time, distance, traffic, and number of parallel orders the partner is handling.

Given a list of restaurant ratings and a minimum threshold, return the top-k restaurants sorted by rating using a min-heap. Explain why a heap beats a full sort for large k, and the time complexity of both approaches.

Design Zomato Pro (subscription). Members get free delivery, discounts, and priority support. Cover: subscription lifecycle, prorated upgrades/downgrades, cohort-based analytics to measure retention, and how you handle payment failures.

Design Zomato's surge pricing engine. When demand spikes (rain, IPL final), delivery fees increase automatically. Cover: demand signals, pricing formula, fairness constraints, A/B testing pricing strategies, and how to avoid customer backlash.

Explain Zomato's restaurant onboarding data pipeline. A new restaurant submits menus, photos, and operating hours. How do you validate, normalise, and make this data searchable within minutes of submission?

How does Zomato calculate a restaurant's "delivery fee"? The fee depends on distance, demand, time of day, and partner availability. Implement a pricing function given these inputs and discuss fairness trade-offs.

Tell me about a time you had to optimise a system under pressure (peak load, Black Friday equivalent). What specific changes did you make and what was the measurable impact?

Explain the difference between at-most-once, at-least-once, and exactly-once delivery semantics in Kafka. Which one requires the consumer to handle duplicate processing?