Zomato Analytics Engineer Interview Questions (2026)

1. 1Coding Screen45 minMedium

   Medium DSA problems focused on arrays, strings, and hashmaps with working code expected quickly.

2. 2Technical Round 250 minMedium

   A harder DSA problem plus practical engineering discussion drawn from your projects and real Zomato features.

3. 3Design / Product-Thinking Round55 minHard

   Design a Zomato or Blinkit feature end to end (e.g. live order tracking or dark-store picker flow), balancing tech design with product judgment.

4. 4Hiring Manager / Culture Round45 minMedium

   Blunt conversation on hunger, ownership, why Zomato, and how you handle chaos and hard feedback.

5. 5HR Round25 minEasy

   Compensation, ESOPs, notice period, and setting expectations on pace and in-office work.

1. Q1

   During a Restaurant Ads experiment, the treatment/control split is 52/48 instead of 50/50. How would you diagnose sample ratio mismatch?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Assume assignment logs, exposure logs, and eligibility filters may disagree.

   How to answer: To diagnose sample ratio mismatch (SRM), I would first check for data integrity issues like incorrect logging or ETL failures. Next, I'd analyze pre-experiment metrics and user characteristics (e.g., signup date, location, device) to see if the randomization unit (e.g., user ID) was properly assigned across groups. I would perform a chi-squared test on the observed vs. expected group counts to statistically confirm SRM. Finally, I'd investigate potential causes such as implementation bugs in the randomization logic, user exclusion criteria applied post-randomization, or issues with how the experiment platform assigns users.

2. Q2

   The Hyperpure experiment is trending positive after two days. A PM wants to stop early and launch. How do you handle peeking and sequential testing?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Discuss pre-specified stopping rules, alpha spending, business urgency, and risk.

   How to answer: Explain that peeking early can lead to inflated Type I error rates, increasing the chance of false positives. Discuss the need to pre-define stopping rules and sample size based on a power analysis before the experiment begins. Mention sequential testing methods (e.g., A/B testing with O'Brien-Fleming boundaries or Always Valid Inference) as a way to allow for continuous monitoring while controlling the Type I error. Advise against stopping early unless pre-specified criteria are met, emphasizing the importance of statistical rigor and avoiding p-hacking.

3. Q3

   Midway through the Food Delivery test, tracking for Zomato Gold changed. How would you decide whether the experiment results are still usable?

   HardStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Compare instrumentation versions, affected traffic share, raw logs, and sensitivity analyses.

   How to answer: A strong candidate would first identify the specific change in Zomato Gold tracking and its potential impact on the experiment's primary or secondary metrics. They would then analyze the timing of the change relative to the experiment's start and the observed impact on key metrics for both control and treatment groups post-change. The decision hinges on whether the change introduced bias, specifically if it affected one group more than the other, or if it significantly altered the underlying user behavior being measured. If the impact is uniform or negligible, results might be usable with caveats; otherwise, the experiment may need to be restarted or the affected period excluded.

4. Q4

   Zomato is considering launching Zomato Gold in a new city. Build a decision framework and the first 90-day success metrics

   MediumProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Include demand, supply, operations, compliance, cost, and competitive positioning.

   How to answer: A strong candidate would first outline a decision framework for launching Zomato Gold, including market research (competitor analysis, restaurant density, average order value), customer segmentation (demographics, dining habits), and financial modeling (projected revenue, costs, break-even analysis). They would then propose a phased launch strategy, perhaps starting with a pilot. For the first 90-day success metrics, they should focus on early indicators like restaurant sign-ups and engagement (number of Gold partner restaurants, active Gold users, Gold order volume), customer acquisition and retention (new Gold subscribers, churn rate), and initial financial performance (revenue generated from Gold, average transaction value for Gold orders). Qualitative feedback from both restaurants and users would also be crucial.

5. Q5

   Refunds, cancellations, or failures are rising for Restaurant Ads. Quantify the business impact and recommend where to intervene first

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Break the problem into customer experience, partner quality, operations, and policy effects.

   How to answer: Quantify the business impact by calculating the total revenue lost due to refunds/cancellations/failures (refund rate * ad spend) and the associated operational costs (processing refunds, customer support). Segment the data by restaurant type, ad campaign, time of day, and failure reason to identify patterns. Prioritize intervention based on the largest revenue loss segments and the most actionable root causes, such as ad misconfiguration, inventory issues, or payment gateway failures.

6. Q6

   Build a one-page business review for Reviews that explains what happened, why it happened, and what the team should do next

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Make it executive-ready: crisp narrative, key metrics, quantified impact, and action owners.

   How to answer: A strong answer will structure the review with a clear Executive Summary, followed by 'What Happened' (key metrics like review volume, average rating, sentiment trends, user engagement with reviews). 'Why It Happened' should analyze drivers such as product changes (new features, UI updates), marketing campaigns, operational issues (food quality, delivery times), or external factors (competitor actions, seasonality). 'What To Do Next' will propose actionable recommendations, prioritized by impact and feasibility, focusing on product improvements, operational fixes, or user engagement strategies, along with proposed metrics to track success.

7. Q7

   Design a funnel dashboard for Hyperpure from first exposure to delivered order. How would you highlight the biggest conversion opportunities?

   MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

   Context: Include step-level conversion, drop-off contribution, trend, and segmentation.

   How to answer: A strong answer would outline a funnel from 'Hyperpure Awareness' (e.g., ad impression, Zomato app visit) to 'Delivered Order', breaking it down into logical stages like 'Product View', 'Add to Cart', 'Checkout Initiated', 'Order Placed', and 'Order Delivered'. Key metrics for each stage would include unique users, conversion rate to the next stage, and drop-off rate. To highlight conversion opportunities, the candidate should propose identifying stages with the steepest drop-offs using visual cues (e.g., red highlighting, larger percentage display) and then suggest deep-diving into those specific stages with additional dimensions like device type, user segment, product category, or time of day to uncover root causes. Finally, they should mention A/B testing hypotheses based on these insights.

8. Q8

   Set alert thresholds for menu-to-order conversion, commission revenue per order, and order cancellation rate in Reviews. How would you distinguish noise from a real incident?

   MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

   Context: Use seasonality, baselines, statistical thresholds, and business severity.

   How to answer: A strong candidate would first define appropriate alert thresholds for each metric, likely using statistical methods like standard deviations or percentage changes from a baseline (e.g., 2-3 standard deviations for menu-to-order, 10-15% drop for commission revenue, 5% absolute increase for cancellation rate). They would then explain how to distinguish noise by considering the duration and magnitude of the deviation, correlating with other metrics (e.g., a drop in menu conversion alongside a spike in app errors), and checking for known external factors (e.g., marketing campaigns, system outages). Finally, they would suggest implementing a multi-stage alerting system and A/B testing alert sensitivity.

9. Q9

   How would you audit a dashboard for Dining after stakeholders report that numbers do not match finance or operations reports?

   MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

   Context: Trace metric definitions, source tables, filters, timezones, freshness, and access rules.

   How to answer: A strong candidate would outline a systematic audit process starting with understanding the specific discrepancies reported by finance/operations, including exact metrics and timeframes. They would then verify the dashboard's data sources and SQL queries, checking for correct table joins, filters, aggregations, and date logic against the source systems. Key steps include validating data freshness, reviewing data definitions for consistency across reports, and cross-referencing a sample of raw data with the dashboard's output. Finally, they would identify the root cause (e.g., data pipeline issue, definition mismatch, query error) and propose a solution.

10. Q10

    Create a dashboard narrative for Operations lead explaining why menu-to-order conversion changed for Zomato Gold. What charts would you show first?

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Use a top-down story with impact, drivers, segments, and recommended actions.

    How to answer: The dashboard narrative should start by clearly stating the observed change in menu-to-order conversion for Zomato Gold, including the magnitude and direction (e.g., 'a 15% drop'). The initial charts should visualize this trend over time, breaking it down by key dimensions like restaurant type, city, and time of day to identify specific segments most affected. Subsequently, the narrative should explore potential root causes by analyzing related metrics such as menu views, add-to-cart rates, average order value, discount utilization, and restaurant availability/delivery times for Gold users. Finally, it should conclude with data-backed hypotheses and potential next steps for investigation or intervention.

11. Q11

    Define a north-star metric for Zomato's Food Delivery. What input metrics and guardrails would you track to ensure it is not gamed?

    EasyProduct Analytics & Business CaseProduct AnalyticsZomato-specific

    Context: Context: improve discovery and restaurant monetization without hurting customer experience.

    How to answer: The north-star metric for Zomato's Food Delivery should be 'Number of Completed Orders per User per Month'. This metric directly reflects user engagement and revenue generation. Input metrics would include 'Average Order Value', 'Conversion Rate (Cart to Order)', 'Repeat Order Rate', and 'Time from Order Placement to Delivery'. Guardrail metrics would focus on 'Customer Complaint Rate (delivery issues)', 'Delivery Partner Churn Rate', and 'Average Delivery Time' to ensure quality and sustainability are maintained.

12. Q12

    Design a retention analysis for Zomato Gold. Which cohorts, time windows, and segments would you use?

    EasyProduct Analytics & Business CaseProduct AnalyticsZomato-specific

    Context: Make the cohort definition precise and explain how you would separate activation from retention.

    How to answer: To design a retention analysis for Zomato Gold, I would define cohorts by the month of their Zomato Gold subscription activation. The time windows would be monthly, tracking retention for at least 12-24 months post-activation to observe long-term trends. Key segments for analysis would include: subscription type (e.g., 3-month, 6-month, 12-month), acquisition channel (e.g., in-app promotion, partner offer), city tier, and user activity level prior to subscription (e.g., number of orders in the last 30 days). Retention would be measured as the percentage of users from a cohort who made at least one Zomato Gold-eligible order in a given month.

13. Q13

    How would you segment customers for Hyperpure to find growth opportunities? Name segments, metrics, and potential actions

    MediumProduct Analytics & Business CaseProduct AnalyticsZomato-specific

    Context: Use behavioral, value, lifecycle, and acquisition dimensions.

    How to answer: To segment Hyperpure customers for growth, I'd start with behavioral segments like purchase frequency (new, occasional, frequent) and average order value (low, medium, high), and demographic/firmographic segments such as business type (restaurants, cafes, hotels, cloud kitchens) and size. Key metrics for each segment would include customer lifetime value (CLTV), churn rate, average order value (AOV), and product category penetration. Potential actions include targeted promotions for low-frequency customers, upselling higher-margin products to high-AOV segments, and tailored product bundles based on business type.

14. Q14

    Zomato wants to personalize Zomato Gold. What are the risks of optimizing for short-term engagement, and how would you measure long-term quality?

    MediumProduct Analytics & Business CaseProduct AnalyticsZomato-specific

    Context: Discuss filter bubbles, partner fairness, novelty, fatigue, and retention.

    How to answer: Optimizing Zomato Gold for short-term engagement risks user burnout, feature fatigue, and devaluing the subscription's perceived long-term value, potentially leading to higher churn. It could also encourage superficial interactions rather than deep, meaningful usage. To measure long-term quality, I would track metrics like subscriber retention rate (e.g., 6-month, 12-month), average order value (AOV) of Gold users over time, cross-category usage, and Net Promoter Score (NPS) or Customer Satisfaction (CSAT) specifically from Gold subscribers. Additionally, I'd analyze the lifetime value (LTV) of different Gold user segments to understand sustained profitability.

15. Q15

    A new Dining initiative may cannibalize Zomato Gold. How would you measure incremental value rather than just shifted demand?

    HardProduct Analytics & Business CaseProduct AnalyticsZomato-specific

    Context: Use holdouts, customer-level paths, category/market controls, and margin impact.

    How to answer: To measure incremental value, first define clear success metrics for both the new Dining initiative and Zomato Gold, focusing on long-term engagement and revenue. Implement a robust A/B test or a quasi-experimental design (e.g., geo-based rollout) where a control group does not have access to the new Dining initiative. Compare key metrics between the test and control groups, specifically looking for a net increase in overall user spend, frequency, and retention across both programs combined, rather than just within the new initiative. Analyze user behavior to understand cross-program engagement and identify if new users are acquired or existing users are reactivated due to the Dining initiative, contributing to overall Zomato ecosystem growth.

Practice these with instant AI feedback in a live mock interview → Start a Zomato Analytics Engineer mock

Practise DSA and system design for scale; prepare product-thinking; expect a strong culture-fit round

Indicative Analytics Engineer pay in India: ~₹9–40 LPA (role-level range, not a Zomato-specific figure).

Other roles at Zomato

Analytics Engineer interviews at other companies