Zomato Interview Questions: 8 Real Q&A + Prep Tips (2026)
Curated Zomato (Zomato (Eternal Ltd.)) interview questions with model answers.
Industry: Food Technology, E-commerce. Difficulty: Hard. Hiring for: Software Development Engineer I, Software Development Engineer II (Backend), Software Development Engineer II (Frontend), Data Scientist. Average package: ₹20-30 LPA (SDE-1), ₹35-50 LPA (SDE-2), ₹50-70+ LPA (SDE-3/Lead).
Selection process
- Online Coding Assessment (DSA)
- Technical Interview 1 (DSA & Problem Solving)
- Technical Interview 2 (System Design / Advanced DSA)
- Hiring Manager / Bar Raiser Round
- HR Round
Real interview questions and answers
Technical: Given a list of restaurant orders with start and end times, merge overlapping time intervals to find the minimum number of delivery slots needed.
This problem requires sorting the intervals by their start times. Iterate through the sorted intervals, merging any current interval with the next if they overlap. If an overlap exists, update the end time of the merged interval to be the maximum of the two. If no overlap, add the current merged interval to the result and start a new one. This approach, using a greedy strategy and O(N log N) time complexity due to sorting, efficiently determines the minimum slots. Consider edge cases like identical intervals or one interval fully containing another.
Technical: Design a data structure to efficiently find the top 'K' trending dishes across all restaurants in real-time.
A combination of a HashMap and a Min-Heap (or Priority Queue) is ideal. The HashMap stores dish IDs to their current counts for O(1) updates. The Min-Heap maintains the top 'K' dishes based on their counts. When a dish's count increases, update it in the HashMap. If it's not in the heap and its count is higher than the heap's minimum, remove the minimum and insert the new dish. This ensures O(log K) operations for updates after initial O(N) HashMap build, maintaining real-time top 'K' efficiently.
Technical: Design a scalable order tracking system for Zomato, considering millions of concurrent users and real-time updates.
The system needs a microservices architecture. Use Kafka or RabbitMQ for asynchronous communication between services (order placement, kitchen, delivery, user notifications). A NoSQL database like Cassandra or MongoDB is suitable for storing order details due to high write throughput and flexible schema. For real-time updates, WebSockets or Server-Sent Events (SSE) can push status changes to users. Implement caching (Redis) for frequently accessed data like live order locations. API Gateway handles routing and authentication. Data partitioning and replication are crucial for horizontal scalability and fault tolerance.
Behavioral: Describe a time you faced a significant technical challenge at a previous role/project. How did you approach it, and what was the outcome?
In my previous role, we faced intermittent latency spikes in our payment gateway integration, impacting user experience. I initiated by deep-diving into logs and monitoring dashboards, identifying the issue stemmed from third-party API rate limiting. My approach involved implementing a circuit breaker pattern and an exponential backoff retry mechanism. I also introduced a local cache for frequently requested payment instrument data. The outcome was a significant reduction in latency spikes by 80%, improving payment success rates and overall system reliability, which was validated through A/B testing and user feedback metrics.
HR: Why Zomato? What excites you about working in the food-tech industry?
Zomato's impact on daily lives in India, from empowering local restaurants to delivering convenience, deeply resonates with me. The food-tech industry presents unique, complex challenges like hyper-local logistics, real-time demand prediction, and ensuring seamless customer experience at scale. I'm particularly excited by Zomato's innovative use of technology to solve these problems, such as their drone delivery trials and robust recommendation engines. My skills in distributed systems and problem-solving align perfectly with contributing to such a dynamic, high-growth environment, where I can directly see my work benefit millions.
Technical: How would you optimize database queries for a frequently accessed leaderboard showing top-rated restaurants?
For a top-rated restaurant leaderboard, pre-computation and caching are key. Instead of calculating ratings on-the-fly, schedule a daily or hourly batch job to aggregate ratings and store them in a separate, optimized table. This table would contain pre-calculated average ratings, number of reviews, and other relevant metrics. The leaderboard query then becomes a simple `SELECT * FROM precomputed_ratings ORDER BY average_rating DESC LIMIT N`. Further, cache this pre-computed result in Redis or Memcached to handle high read traffic, invalidating it only when the batch job completes. Indexing on `average_rating` is also crucial.
Behavioral: How do you handle disagreements with team members or product managers regarding technical implementation details or feature priorities?
I approach disagreements by first seeking to understand the other person's perspective and underlying motivations. For technical details, I present data-driven arguments, outlining pros and cons of different approaches, considering factors like scalability, maintainability, and development effort. If consensus isn't reached, I propose a small-scale prototype or a time-boxed spike to gather concrete evidence. For feature priorities, I align with the product manager on business impact and user value, suggesting trade-offs if necessary. Ultimately, I prioritize team goals and commit to the agreed-upon direction, even if it wasn't my initial preference.
HR: What are your salary expectations for this role at Zomato?
Based on my research into industry standards for an SDE-1 at a product-led company like Zomato, and considering my skills and experience, I am looking for a compensation package in the range of ₹25-28 LPA. This includes base salary, bonuses, and ESOPs. I am confident that my contributions will provide significant value to Zomato, and I am open to discussing the full compensation structure to ensure a mutually beneficial agreement.
Preparation tips
- Master Data Structures & Algorithms: Zomato heavily tests advanced DSA (Graphs, DP, Trees, Heaps). Practice LeetCode Hard problems consistently.
- Focus on System Design for Scale: Understand distributed systems, microservices, databases (SQL/NoSQL), messaging queues. Design for Zomato-specific scenarios like real-time order tracking, delivery logistics, and recommendation engines.
- Deep Dive into Zomato's Business & Tech: Research their recent product launches, tech blogs, and challenges in the food-tech space. Understand how they leverage data and AI.
- Prepare Behavioral Questions with STAR: Practice articulating your experiences using the STAR method (Situation, Task, Action, Result), emphasizing ownership, problem-solving, and collaboration.
- Brush up on Object-Oriented Design (OOD): For SDE-1, expect LLD questions. For SDE-2+, expect HLD. Understand design patterns and principles like SOLID.
Common questions about Zomato interviews
What's the typical SDE-1 salary at Zomato?
For an SDE-1 role, Zomato typically offers a package ranging from ₹20-30 LPA, inclusive of base salary, performance bonuses, and ESOPs. This can vary based on your college tier, prior internship experience, and interview performance.
How difficult are Zomato's interviews compared to other product companies?
Zomato's interviews are considered challenging, on par with top-tier product companies like Swiggy or Flipkart. They place a strong emphasis on advanced DSA, robust system design, and real-world problem-solving, requiring thorough preparation across all technical domains.
Do I need to be from a Tier-1 college to get into Zomato?
While a Tier-1 background can be advantageous, it's not strictly mandatory. Zomato values strong problem-solving skills, a competitive programming background, impactful projects, and relevant experience. A compelling portfolio can open doors regardless of your college.
How long does Zomato's hiring process usually take?
The entire hiring process at Zomato typically spans 3 to 6 weeks. This duration depends on factors like candidate availability, the scheduling of interview panels, and the number of rounds required. Expedited processes are possible for exceptional candidates.