Zomato Frontend Interview Experience | SDE 2
Note: This interview experience was contributed by a user of devtools.tech platform. You can contribute your interview experiences here and interview questions here.
Round 1: HR Screening
It went for about 30 minutes. It was a brief discussion about my background, ensuring alignment on the role, and setting expectations. Mainly we talked about
- Current role and responsibilities
- Experience with past tech stacks
- Current and expected compensation
- Why switching and why do I want to join Zomato?
💡Tip: Be clear about what you want. It is okay to switch for more open but trick is to better it in a way that it sounds win-win for both the candidate and the company.
Round 2: Technical Screening
This was a mix round of questions around frontend concepts and coding. Topics covered:
- State management in large scale applications: Discussion around Redux, Redux Toolkit, Zustand, and Context API. What makes sense in which scenario.
- What is Virtual DOM? What are the advantages of it?
- Implementation of Debounce method
- React Optimization techniques (memo, useMemo, useCallback, and others)
- Different architectures (Monolith, Micro-frontends, module federation, shared dependencies, auth, and more)
💡Tip: Have strong frontend & JavaScript fundamentals. Practice a wide variety of machine coding questions as in my experience, there could be multiple problem solving or UI based questions. Recommended Resource: https://devtools.tech/questions/all
Round 3: Assignment
It was a 2 day assignment to build a simplified version of Zomato like restaurant listing page. It was aimed at testing topics like
- Inifinite Scrolling (using either Intersection Observer or some third party package).
- Responsive UI
- Filtering
- Loading & Error States
- Testing (Unit and E2E)
- Deployment
Round 4: Frontend System Design
It was like 1.5 hours and I got a question to build something an Order tracking system. The discussion was quite intense and involved topics like
- Frontend architecture
- Data handling
- API discussion
- Different of types users in the system and what type of access they will have.
- UI framework (React/Angular/Vue)
- Communication Strategies (Web Sockets/Polling/Rest)
Recommend frontend system design guide: https://devtools.tech/frontend-system-design
Round 5: Cultural & Leadership Round
It was taken by an Engineering Manager. It was focused on ownership, teamwork, and understanding the mindset. The discussion primarily revolved around -
- Past projects: Challenges, achievements, and balance between tech & speed.
- Did I face any conflict in the past? How did I resolve it?
- What is my decision matrix? Do I consider trade-offs and how?
- If I want to stay IC or move to people track? What is my vision or future mindset?
That's all! I hope it helps the community.
If you are preparing for interviews, then devtools.tech should be your goto resource for quality interview preparation. Make the most of --
- 250+ premium questions with test cases and powerful in-browser IDE
- Real tagged questions from 60+ companies
- Frontend System Design Guide
- Real time AI feedback and review
- Time savers like Focus Areas specific questions
- Access to future updates
- Premium Resume Guide
- Premium Question Collections
- Access to AI Interview Assistant
