How hard are Zomato Product Analyst interviews, and what do candidates report about difficulty?

In reported experience stats for this role, the most common difficulty is “difficult.” Candidates also report 23 interviews, based on the collected responses. The difficulty label aligns with a process that includes technical, case-style, and behavioral evaluation.

What is the interview loop for Zomato Product Analyst candidates?

The process starts with an online assessment to filter for technical proficiency. After that, there are technical interviews focused on skills and problem-solving, followed by behavioral interviews that assess cultural fit and behavioral competencies. The guide also notes the pace can be fast with multiple rounds potentially occurring in short succession.

What topics get tested most in Zomato Product Analyst SQL and data interviews?

SQL is a top tested area, including SQL joins such as INNER, OUTER, and SELF. The role also commonly tests SQL window functions, Python, and pandas-based data analysis for case study thinking. You should also be prepared for guesstimation under uncertainty and root cause analysis (RCA).

What kind of SQL questions does Zomato ask for a Product Analyst interview?

You may be asked to write a query like: “Write a query to identify the top 5 restaurants by order volume in a specific city for the last 30 days.” Other common patterns include diagnosing duplicate records from joins, comparing window functions versus GROUP BY, and deciding when to use a CTE over a subquery. The guide also includes questions on calculating retention and optimizing slow SQL with multiple joins and millions of rows.

What product sense and case study questions show up for Zomato Product Analyst interviews?

Expect questions that require measurable product thinking, for example: “How would you measure the success of a new 'Priority Delivery' feature?” You can also get root cause analysis scenarios such as: “If the number of daily orders dropped by 10% overnight, how would you conduct a root cause analysis?” The guide further emphasizes designing metrics for product quality, like tracking the quality of restaurant listings.

What compensation do candidates report for Zomato Product Analyst roles?

No compensation figures are provided in the available materials for this role, so pay cannot be stated from the supplied data. If you are using candidate-reported sources for Zomato Product Analyst, be sure to match the level and location since pay varies by those factors.

ZomatoProduct Analyst

Updated Feb 22, 2026

Zomato Product Analyst Interview Experiences 2026

Real, anonymous reports from people who interviewed for Product Analyst at Zomato, newest first and distilled into what to expect across the loop.

Get your personalized Zomato Product Analyst prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

6 months ago

Average Positive New Delhi

After an initial OA screening, I moved into a fairly structured process: a technical screen where I had to work through SQL and data questions, then a second technical round, and finally an HR conversation. The technical parts felt like an SQL drill overall, but they didn’t stay purely theoretical—there were things like inner and outer joins and even self-join style queries, plus aggregate functions and basic join logic. I also got at least one guesstimate, and the mix included statistics topics that leaned on interpreting measures and simple distributions (one time it even touched box-plot style thinking).

A big part of the format was “talk while you solve.” I ended up sharing my approach as I wrote queries, and I remember the overall difficulty landing in the easy-to-medium zone, not a huge trick-show, just lots of practical concepts. The rounds ran for roughly 40 minutes to about an hour each, and I spoke to multiple interviewers across the two technical stages and then HR.

> 1 year

Difficult Positive India

My process happened in a campus-style setup and it moved fast, like everything was happening in a compressed window. I took a proctored assessment that was clearly split into two parts: an MCQ section covering quantitative aptitude, logical reasoning, data interpretation, and MySQL, followed by a section with coding questions in MySQL that focused on joins and subqueries. The second section felt like the deal breaker for me because the MySQL coding wasn’t in a familiar “DSA style” mold.

Once I was shortlisted, I went into a technical-heavy interview flow on the same day: an initial round centered on product improvement style thinking, plus puzzles, and another round that grilled me on product reasoning—why product, why the company—and then mixed in guesstimates. Even though my overall difficulty felt high, the structure was consistent: quantify the situation with guesstimates, demonstrate reasoning, and show SQL competency.

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.