Zomato Interview Experience (On - Campus)
Interview Experience
Recently, Zomato came to our college for hiring for the role of SDE. I will discuss here my experience with the entire hiring process in detail. The detailed experience of...
Full Details
Recently, Zomato came to our college for hiring for the role of SDE. I will discuss here my experience with the entire hiring process in detail. The detailed experience of each round is as follows: Introduction and Project Discussion: Brief introduction about yourself (2 minutes). Discussion about one of your projects (3-4 minutes). DSA Problems: I was given two DSA problems to solve: The first one was to delete a node in a BST. I need to solve this using a recursive approach The second problem was reversing a linked list in groups of size K. I provided the proper approach and wrote code for both problems. Duration: Approximately 40 minutes. SQL Queries: I need to write SQL queries for five different scenarios: Basic and easy queries involving simple clauses and aggregate functions were asked. Intermediate queries with joins between two tables on different conditions. One query involved joins with three tables. Difficulty level: Leetcode. Duration: Around 8-9 minutes.
System Design Music Player: Task: Optimize the time complexity of a single function in a music player system design problem to achieve O(N) time complexity. Considered an easy question. Duration: Approximately 9-10 minutes. Theory Questions from the subjects like DBMS & OOPS Concepts were asked: DBMS joins: Types and specific details (6-7 minutes). OOP pillars:
Explanation and real-life examples (8-9 minutes). Polymorphism: Types, details (overriding, overloading), and dynamic binding (5-6 minutes). No questions about operating systems during the interview. Overall Experience: Total duration: Approximately 1 hour and 22 minutes. Understand CS Fundamentals clearly. Solving DSA problems quickly allowed more time for additional questions. HR announced results, and you were fortunate to be selected for the Zomato opportunity.
About This Question
This is a candidate experience report from a zomato interview for a swe role during the system design round reported in 2024.
It covers the following topics: Linked List, Trees, Oop, Binary Tree, Sql, Recursion, Os, System Design .
Difficulty rating: Easy
More Zomato Interview Questions
About Zomato Interview Reports
This question was reported by a candidate who interviewed at Zomato. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Zomato are the higher-signal extractions to take from this report.
For broader preparation context, the Zomato interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Zomato reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Zomato Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Zomato reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.