I’d gone through Zomato before and didn’t initially make it through. What changed my experience was that after a rejection—tied to a lack of years of experience—I got reached out to again by the recruiter when another team had an opening.
After a few weeks, I got another opportunity from a different team, and the same recruiter contacted me directly. This time it felt like the process started from the recruiter outreach rather than me having to restart from scratch, and it moved into a new interview opportunity.
3 weeks ago
I applied to Zomato for an SDE-1 UI role by reaching out to a recruiter directly, and I got a response that moved things along quickly. The interview itself was design-focused and felt pretty structured: I walked through a solution for designing a Google Calendar, and I had to cover not just the UI idea but also the bigger picture behind it.
After the calendar design, I was asked to explain architecture and the data flow, including how event management would work and how I’d think about scalability as the system grows. The follow-ups pushed me toward user interactions—what the UI needs to enable, how the experience would behave—and I ended by talking through frontend design decisions and the trade-offs I was making as I went.
3 weeks ago
I applied to Zomato for an SDE-1 UI role by reaching out to a recruiter directly, and I got a response that moved things along quickly. The interview …
2 months ago
My Zomato SDE-2 process followed a fairly standard sequence: a DSA round first, then HR and deeper technical rounds after that. I went into the DSA pa…
2 months ago
Difficult Positive Gurgaon, Haryana
My understanding of the Zomato interview flow was that it typically began with some kind of initial screening round, then progressed into three main r…
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 & Flow
The interview process at Zomato typically consists of multiple rounds, starting with a DSA coding round followed by system design and HR discussions. Candidates noted that the flow was generally well-organized, with clear transitions between technical and behavioral evaluations.
Interview roundsStructureFlow
Technical Evaluation Focus
Candidates experienced a strong emphasis on both data structures and algorithms (DSA) and system design, with many reporting that technical discussions often included real-world applications and architectural reasoning. The interviews required a deep understanding of core concepts and the ability to articulate design choices clearly.
DSASystem designTechnical evaluation
Behavioral & Project Discussion
Interviews often included a deep dive into candidates' previous projects, requiring them to explain their decisions, trade-offs, and technical choices in detail. This aspect highlighted the importance of being able to connect personal experience with technical knowledge.
BehavioralProject discussionTrade-offs
Difficulty Level & Expectations
Candidates described the difficulty of the interviews as challenging, particularly in terms of the breadth of topics covered and the need for clear, structured reasoning under pressure. Many felt that missing edge cases or not articulating thoughts clearly could significantly impact their performance.
DifficultyExpectationsClarity
Recruiter Interaction & Follow-up
Several candidates noted positive experiences with recruiters, who facilitated the process and provided opportunities for re-engagement after initial rejections. This aspect contributed to a feeling of support throughout the interview journey.
Recruiter interactionFollow-upSupport
Preparation for System Design
Candidates emphasized the need to prepare for system design discussions, which often required them to think critically about architecture, scalability, and real-world application scenarios. This preparation was crucial for success in later rounds.