Interview process
Discussions about frontend fundamentals and my work experience went well. I was supposed to code the solution within 10 minutes after I had thought through the approach, but I took longer because I was supposed to solve the question in JS, while I primarily solve DSA questions in C++.
- Technical interview
Interview rounds
3 questions across 1 roundTechnical interview
3 questionsQuestion types asked
Specific questions asked
What are React Portals?
Questions on z-index.
What is React Fiber? How can it be implemented?
[Since it's in my work experience.] What is virtualization?
How can the list be optimized for performance?
Questions on entity relationship graphs.
DSA - Graph question needs to be done using BFS.
Discussion around time complexity, optimization, etc.
Interview tips
Focus on fundamentals, good practise of machine coding as well as DSA patterns. You should be able to explain the solution well, so practice coding problems(both DSA and machine coding frontend) as much as you can, and practice speaking out loud while solving.
Company culture
The team is group of very talented and hard working engineers.
Get full access with a membership, or share your experience to try it free.
More Zomato interview experiences

“The interview process was conversational but still quite rigorous. The interviewer spent time understanding my background, especially my experience in B2B SaaS, healthcare AI, workflow products, and distributed deployments. What went well was that I got to explain complex product work in depth, especially around AI-enabled clinical workflows, modular deployments across multiple countries, and how AI findings translate into real operational action. What could have gone better was that some of my answers were initially a little broad. The interviewer probed deeply, so I had to tighten my responses and make the product ownership, trade-offs, and metrics clearer. Overall, it felt like a strong product-thinking conversation rather than a standard resume walkthrough.”

“Interviewer was nice. He was kind off to help and explain all clarifying questions. What went well : - indentifying stakeholder What didn't well : -> end user experience could have been explained more clearly”