What Is the Zomato Interview Process Like? (Round by Round)

Candidates report an online coding round followed by three interview rounds at Zomato. A recruiter call usually comes first, often after a referral from an employee. The coding round runs about 90 minutes, and candidates report it both on Intervue and on HackerRank. Two technical interviews follow: the first pairs data structures with a deep discussion of your projects, and the second covers system design, low level design, and core computer science. A culture fit conversation ends the process. Most reports describe about two to four weeks from the coding round to a decision.

Quick Overview

Stage 1: Referral or Application

Referrals matter more here than at many companies. One candidate report states that Zomato hires largely through referrals, and that referred applicants then receive a recruiter call. Other candidates report long gaps between an online application and any reply at all.

Zomato is part of Eternal, which also runs Blinkit, District, and Hyperpure, and some hiring drives are shared across these brands. The job listing may therefore name one brand while the interview panel works on another.

Stage 2: The Online Coding Round

The format varies by hiring drive, and one candidate reports four questions in 90 minutes on Intervue. Another reports a 90 minute HackerRank test with 20 multiple choice questions plus three coding questions. That multiple choice section asked about operating systems, computer networks, databases, and object oriented programming.

Reported coding problems include matrix operations, the next smallest palindrome, graphs, dynamic programming, and strings. Finish the easier questions completely before you start the hardest one. If this is your first such test, read what an online technical assessment involves.

Stage 3: Technical Round One

This round pairs live coding with a long discussion of your projects. Reported problems include reversing a linked list in groups of a given size, a grid problem similar to counting islands, maximal square, maximum product subarray, and converting a binary tree to a doubly linked list. One candidate also reports questions on SQL joins.

Interviewers ask for the time and space cost of every solution you write. Candidates report that the project discussion covers the reasons behind each decision you made. Frontend candidates report JavaScript and React questions in place of some of the algorithm work.

Stage 4: Technical Round Two

Design work appears in this round, and reported questions include designing a rate limiter, a URL shortener, end to end delivery tracking, and restaurant and menu services. One report describes a geo based design problem that used geohashing and quad trees, and another describes a hands-on concurrency coding task. The full topic list is in the Zomato system design interview.

Stage 5: The Culture Fit Round

This round is conversational, and some candidates report it in person at the Gurugram office. Expect the motivation question, plus questions about taking ownership beyond your defined scope. Candidates also report questions about working under pressure and about unclear requirements. Prepare the motivation answer with how to answer why Zomato.

How the Campus Path Differs

On campus drives begin with a written or online test that shortlists a fixed number of students. One report describes 25 students shortlisted after the coding round and nine final offers. Another describes a drive that narrowed from 18 interviewed students to three hires. Campus interviews often run on a single day, and the HR round there can last only about 15 minutes.

Timeline and Decision

Most candidates report two to four weeks from the coding round to a final answer. Campus candidates sometimes report a result within minutes of a round ending, while off campus candidates report slower scheduling and long silences instead. The reported wait at each stage is in how long it takes to hear back.

Questions to Ask Them

Every round ends with time for your questions, and a specific question proves you researched the business. Useful ones here: how the team measures delivery reliability, how on-call works during peak meal hours, and how much a backend engineer decides about product behavior. Ask which brand in the group your team actually supports.

How to Prepare

• Practice patterns, not problem lists. Grokking the Coding Interview teaches the patterns behind the reported array, string, and grid questions.
• Prepare one project in full depth. Write down your decisions, the alternatives you rejected, and what later failed in production.
• Study design before the second technical round. Grokking the System Design Interview covers the queues, caches, and databases that these questions use.
• Revise the core subjects. The multiple choice section tests operating systems, networks, and databases directly, so spend a full evening on them.
• Write your motivation answer early. It appears first in the recruiter call and then again in the culture fit round.