After a recruiter call to set things up, my interview process at Zomato moved into coding rounds that were very DSA-focused. The next stage was a coding round with medium-level problems, followed by another coding round that started around medium and stretched into medium-to-hard. I was doing timed problem solving while being pushed to handle edge cases and optimize to get the test cases through.
Between rounds, I also got a sense that the process wasn’t only about coding. There were additional computer-subject style questions mixed in—mostly MCQs on core CS topics—with a few system-design prompts scattered in. At one point the interviewer asked about DSA algorithm time complexities too, which made me slow down and reason carefully instead of just jumping into solutions.
4 months ago
I got pulled into Zomato’s interview for the SDE-1 UI track after cold emailing a recruiter and getting a response. The whole process centered on design, and it was more of a front-end architecture conversation than a coding test.
The main prompt was to design a Google Calendar. I had to walk through the architecture and how data would flow, including event management, what happens when events are updated, and how I would think about scalability. The interviewer also wanted me to describe user interactions clearly—how users would navigate, create, and interact with calendar events—and tie those behaviors back to the frontend design decisions.
6 months ago
Average Positive Bengaluru
My process felt like a mix of coding and evaluation rounds that ramped up quickly. I started with an OA-style coding round where I had two questions t…
8 months ago
My Zomato interview for SWE-1 started with a discussion with a Senior Engineering Manager, and it was tightly focused on payments system design. The c…
12 months ago
Average Positive Bengaluru
The timeline surprised me most. I applied, and almost four months later I got a recruiter call that kicked off the process. Not long after that, I had…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with a recruiter call, followed by an online assessment (OA) that includes DSA problems and core CS questions, leading into multiple technical interviews focused on coding, system design, and behavioral questions. The overall experience is structured but can be lengthy, with some candidates experiencing a timeline of up to four months from application to final decision.
Candidates can expect multiple coding rounds that emphasize data structures and algorithms (DSA), often featuring medium to hard problems that require optimization and edge case handling. The coding rounds are designed to assess not just correctness but also the candidate's reasoning and problem-solving approach under time pressure.
DSAEdge casesOptimization
System Design Emphasis
Several candidates reported a strong focus on system design, with interviews requiring them to articulate the architecture of applications and discuss scalability, user interactions, and operational details. This aspect often involves practical design problems rather than purely theoretical questions.
System designArchitectureScalability
Behavioral & Cultural Fit
The final stages of the interview process typically include behavioral questions and discussions about cultural fit, where candidates are evaluated on their past experiences and how they align with the company's values. This round is less technical and focuses on interpersonal skills and situational responses.
Candidates describe the overall difficulty of the interview process as high, with a significant emphasis on performance under pressure. Many felt that the interviews were demanding, requiring not only technical proficiency but also clarity in communication and reasoning.
High pressureDemandingPerformance
Preparation Insights
Candidates suggest that thorough preparation on DSA, system design, and core CS concepts is crucial, as well as practicing clear communication and structured thinking. Some noted that reflecting on past projects and being able to discuss them in detail helped during interviews.