Zomato Interview Questions (2026)
6 questions · 5 experiences · GeeksforGeeks (10) · LeetCode (1)
Browse by role
11 entries
Zomato Interview Experience for FTE (On-Campus) 2023
Zomato Recruitment process
Zomato Interview Experience | On-Campus 2021
Zomato Interview Experience for Frontend Intern
Zomato Interview Experience for SDE Internship (Off-Campus)
Zomato Interview Experience (1+ Year Experienced)
Zomato x Blinkit Interview Experience for SDE-I | On-Campus 2024
Zomato Interview Experience | SDE
Zomato Interview Experience (On - Campus)
Zomato Interview Experience for Software Engineer
#240 Search a 2D Matrix II
Zomato Interview Experience for FTE (On-Campus) 2023
Question Details
Aug-Dec 2023 (7th Semester - Placement Season) The placement season in our IIT kickstarted right from the beginning of the semester. Zomato Limited was open to all the B.Tech branches during the campus placements. Before beginning the Online Assessment, they requested the details of all the students' past internships, projects, and CP scores. Initial shortlisting was done based on the resume and the above-asked details. From around 500 candidates, 164 were shortlisted for the online test. The process was: Resume Shortlisting Online Assessment Offline Interviews (3 Rounds)
Online Assessment The test was for 90 minutes and had three coding questions. I vaguely remember the questions. There was one easy, one medium, and one hard question. The easy question was related to Data Stream and Parsing, the medium question was related to binary search, and the hard one was on Dijkstra Algorithm. I solved the easy question completely and the remaining two with half the test cases each. Out of 164 candidates, 18 were shortlisted for final interview rounds.
Interview Round 1 (30 mins) Zomato was given a Day 1 slot for interviews. The interview panels were ready by early 6:00 AM. Initially, I was asked to brief myself, and following that, I was asked a small ice-breaker question. It was a simple and one-word answer. The question was related to bit manipulation (https://www.geeksforgeeks.org/dsa/find-element-appears-array-every-element-appears-twice/). Next, the interviewer pulled up a detail from my introduction, my interest in cryptography and cybersecurity. So, I was asked basic questions about password hashing, and he gave me a hashed string with specific rules and asked me to decode the hash based on the rules. It was, again, simple. I immediately explained the most optimal approach and was asked to code it. The code was to be written on paper, and I completed it within 2-3 minutes. The interviewer next asked about one of my projects, and I had to explain the entire project in detail. We even went beyond the current scope of my project. Next, the interviewer asked me to choose any topic in the tech field of my choice and develop an interest in him. The interviewer's aim here was to test my communication and the depth of my understanding. I chose cryptography as my topic and went on for almost 15 minutes, explaining that I also used concepts from computer networks. He was pretty impressed. Finally, I was asked whether I follow any blogs or websites for the latest updates in the tech industry. I said no; he was shocked and asked whether I follow math-related blogs, and the answer was yes; I'm a student majoring in Mathematics (MnC Branch).
Interview Round 2 (Almost 1 hr 30 mins) I was immediately notified that I proceeded with Round 2. Out of 18, only three were selected for round 2. This round had two interviewers. The interviewer from round 1 was also present. Just before starting the round, I was pretty confident about myself, and the interviewers' expressions said that they were optimistic about me. Here in this round, I was asked about my internship experience and my project. I interned as an SDE Intern during 3rd-year of summer break at Amazon India. As I successfully delivered my project, I had a strong understanding of the concepts used and the design architecture. I was asked to explain every aspect of the architecture, the metrics, and the impact of my project on the organization. The interviewers also invited me to come up with my architecture, different from the one I used at Amazon; I successfully developed a new design. Finally, I was given a simple puzzle, which I solved after one hint (https://www.geeksforgeeks.org/aptitude/puzzle-mislabeled-jars/).
Interview Round 3 (
HR Round 15 mins) This round was just a formality. Immediately after I came out of round 2, in less than a minute, I was told that I was
hired. During this round, I wasn't asked any questions. Instead, the HR and another senior developer gave me insights into the working culture of Zomato. All three students who went to round 2 got
hired. That sums up the interview experience at Zomato in our IIT. It was 500 -> 164 -> 18 -> 3 -> 3. Preparation Tips It's a standard thumb rule to be well-versed in Data Structures & Algorithms. Apart from DSA, be thorough with OS, DBMS, Computer Networks, Compilers, and System Design. The primary focus can be given to OS and System Design. Be crystal clear with your projects. If the interviewer likes your project, they can deeply investigate it. Not just projects; any point mentioned in your resume should be crafted carefully. Finally, stay calm, don't feel nervous. This helps. During the process, I kept telling myself it doesn't matter even if we don't get Zomato; many other companies are lined up. Take a deep breath before going into the interview lobby. Cheers. All the best!
Topics
More from Zomato
Related companies
Zomato Interview Process Overview
The Zomato interview process typically includes a recruiter screen, one to two technical phone screens, and a 4-6 round on-site or virtual on-site loop. Each round serves a distinct calibration purpose: coding rounds measure correctness, code quality, and complexity reasoning; system design rounds measure architectural judgment at the appropriate level; behavioral rounds measure ownership, leadership scope, and collaboration. Reports tagged on LeakCode from 2024-2026 show Zomato runs a calibrated process consistent with industry norms for companies of its tier.
Difficulty calibration: Zomato coding rounds typically run medium difficulty with follow-up depth as the senior discriminator. System design rounds expect production-grade trade-off articulation at L4+ levels. Behavioral rounds expect quantified outcomes ("reduced p99 latency from 800ms to 120ms") rather than vague impact claims. The candidates who advance consistently demonstrate clear thinking out loud rather than perfect final answers.
How To Use Zomato Question Reports
Real candidate-reported interview questions are a calibration tool, not a memorization target. Zomato updates its question pool every 2-4 months; memorizing exact problems risks misleading you when the interviewer uses a variant. The high-leverage approach: identify the patterns that appear repeatedly in Zomato reports, practice those patterns on similar (not identical) problems, and use the reports to understand the interviewer's typical follow-up depth.
Filter the questions above by round type, difficulty, and recency. Focus first on reports from the past 6-12 months; older reports may reference questions that have since rotated out of Zomato's pool. Reports tagged with quantified difficulty and explicit round type are higher-signal than reports without those tags. The metadata filters help you build a focused study plan in 1-2 hours rather than 8-10 hours of unstructured browsing.
Common Zomato Interview Mistakes
Reports tagged "no hire" at Zomato consistently surface a few patterns: jumping into code without clarifying requirements, coding silently for extended periods, missing edge cases (empty input, single element, large input, overflow), producing working code the candidate cannot refactor when probed, and behavioral stories that use "we" instead of "I" diluting individual signal. Strong candidates explicitly avoid these patterns by following a consistent round template.
The single most predictive failure mode in recent reports: not asking clarifying questions. Interviewers are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into implementation immediately. Strong candidates also verbalize their approach before writing code; weak candidates code in silence and lose the communication dimension of the round's calibration.