Interview experience
Zomato Interview Questions
Overview
Section titled “Overview”Zomato’s fresher hiring is a coding-heavy, 4-5 stage loop where even entry-level technical rounds lean on system-design questions mapped to Zomato’s actual product surface rather than generic prompts.
Zomato interview process at a glance
Section titled “Zomato interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online Coding Assessment (OA) | 90-120 min | 2-3 DSA problems, debugging questions |
| Technical Interviews (2-3 rounds) | 45-60 min each | DSA plus system design scoped to Zomato’s product (order tracking, ranking, delivery) |
| Managerial/Team Fit Interview | 45 min | Zomato values, cultural fit |
| HR/Offer Discussion | 20-30 min | Compensation, relocation, company fit |
Online Coding Assessment
Section titled “Online Coding Assessment”A 90-120 minute test with 2-3 DSA problems ranging medium to hard, sometimes paired with short debugging questions. Solving all problems with an optimal (not just working) solution is usually the bar to advance.
Common questions
- Maximum-sum subarray (Kadane’s algorithm)
- Design an LRU cache
- Merge K sorted lists
- Top-K elements from a stream or array (heap-based)
Technical Interview(s)
Section titled “Technical Interview(s)”2-3 rounds of 45-60 minutes each, mixing a live-coded DSA problem with a system-design discussion. Design prompts are usually framed around Zomato’s own product rather than generic systems, and scale up with seniority - SDE-1 gets a single-feature design, SDE-2+ gets a fuller distributed-systems prompt.
Common questions
- Given restaurant ratings, efficiently find the top-K restaurants
- Design a data structure for real-time order-status tracking
- Design a rate limiter or a restaurant recommendation engine (senior roles)
- Graph and dynamic-programming problems (shortest path, coin change variants)
Round-by-round narratives are on the Zomato interview experience page.
Managerial/Team Fit Interview
Section titled “Managerial/Team Fit Interview”A values-alignment round built around Zomato’s stated principles - customer focus, ownership, and comfort with ambiguity. Expect STAR-format behavioural questions rather than technical ones.
Common questions
- Describe a time you showed customer focus even when it was inconvenient
- Give an example of taking ownership of a problem beyond your assigned scope
- How do you handle ambiguity when requirements are unclear?
- Tell me about a time you had to make a fast decision with incomplete information
HR/Offer Discussion
Section titled “HR/Offer Discussion”A short closing conversation on motivation, logistics, and compensation once the technical and managerial rounds are cleared.
Common questions
- Why Zomato, and what interests you about food-tech specifically?
- Are you willing to relocate to Gurugram or Bengaluru?
- What are your salary expectations?
- Do you have any questions about the team or role?
Sample answer frameworks for each of these are on the Zomato HR interview questions page.
Frequently asked questions about Zomato interviews
Section titled “Frequently asked questions about Zomato interviews”What is Zomato placement interview experience like?
Zomato’s fresher SDE loop typically runs 4-5 stages: 1. Online Coding Assessment (90-120 min) - 2-3 DSA problems plus debugging questions. 2. Technical Interview(s) - 2-3 rounds of 45-60 minutes each mixing DSA with system-design questions framed around Zomato’s actual domain (restaurant ranking, order tracking, delivery ETAs). 3. Managerial/team-fit round on Zomato’s stated values (customer focus, ownership, innovation). 4. HR/offer discussion on relocation and compensation. Total timeline is roughly 2-4 weeks for campus drives.
What questions are asked in Zomato interviews?
DSA problems span arrays, trees, graphs, dynamic programming, and heaps (classic examples: maximum-sum subarray, LRU cache design, merge k sorted lists, top-K elements). System-design questions are usually reframed around Zomato’s own problems - designing an order-tracking system, a restaurant recommendation/ranking engine, or a rate limiter - rather than generic textbook prompts. Behavioural rounds use Zomato’s stated values (customer focus, ownership, bias for action) and expect STAR-format answers.
How many rounds are there in the Zomato interview?
Most fresher SDE drives run 4-5 stages: an online coding assessment, 2-3 technical interviews (DSA plus system design), a managerial/team-fit round, and a closing HR/offer discussion. Some drives compress the managerial round into the final technical interview instead of running it separately - confirm the exact structure from your placement cell or recruiter email.
What is the Zomato technical interview like?
Each technical round (45-60 minutes) mixes a DSA problem solved live on a shared screen with a system-design discussion scaled to the role level - SDE-1 candidates get lighter-weight design questions (e.g. a single feature like order-status updates), while SDE-2+ candidates get fuller system-design prompts (recommendation engines, distributed caching, scaling to millions of users). Interviewers weigh code quality, edge-case handling, and how clearly you explain trade-offs, not just whether the code runs.
How should I prepare for Zomato interviews?
Practice medium-to-hard DSA (arrays, graphs, DP, heaps) on a platform where you can talk through your approach out loud, since Zomato interviews are explicitly evaluated on communication as well as correctness. For system design, practice mapping generic patterns (rate limiters, recommendation systems, real-time tracking) onto food-delivery-shaped problems specifically. Prepare 2-3 STAR stories that map cleanly onto ownership, customer focus, and handling ambiguity - Zomato’s HR/managerial rounds ask for these by name.
Does Zomato ask domain-specific system design questions for freshers?
Yes, more than most product companies at the same level. Even SDE-1 candidates are commonly asked to design or extend a slice of Zomato’s actual product - order tracking, restaurant search/ranking, delivery-partner allocation - rather than a generic “design X” prompt. You don’t need production-scale answers, but you should be able to reason about the specific constraints of a real-time, location-based marketplace.