Zomato Data Analyst 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

   Choose primary and guardrail metrics for a Zomato Gold experiment aimed at improving menu-to-order conversion. What metrics would prevent a harmful launch?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Include user experience, partner health, revenue, reliability, and long-term retention considerations.

   How to answer: The primary metric should directly measure menu-to-order conversion, such as 'Orders per Menu View' or 'Conversion Rate from Menu Page to Order Confirmation'. Guardrail metrics are crucial to prevent negative side effects. Key guardrails would include 'Average Order Value (AOV)', 'Number of Orders', 'User Retention Rate (e.g., 7-day or 30-day)', and 'Customer Support Ticket Volume related to Zomato Gold'. These guardrails ensure the experiment doesn't cannibalize revenue, reduce overall orders, decrease user loyalty, or increase operational costs.

2. Q2

   A new Reviews feature shows a large week-1 lift in menu-to-order conversion, but the effect fades by week 4. What could explain this and how would you design the test duration?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Discuss novelty, learning effects, seasonality, and durable impact.

   How to answer: The fading effect suggests novelty bias or a 'Hawthorne effect' where users initially engage more due to the newness, but revert to baseline behavior once the novelty wears off. Alternatively, it could be a 'selection bias' if early adopters, who are more engaged, were disproportionately in the treatment group initially. Another explanation could be 'seasonal effects' or 'external factors' that coincided with the initial launch. To design the test duration, I would recommend a minimum of 4-6 weeks to capture a full user cycle and account for novelty effects, potentially extending to 8-12 weeks for more robust long-term impact assessment, ensuring the test period covers typical user behavior patterns and potential seasonality.

3. Q3

   menu-to-order conversion is a low-frequency event for Dining. How would you set up an experiment with enough power without waiting too long?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Discuss proxy metrics, variance reduction, larger samples, longer windows, and risk of metric gaming.

   How to answer: To address low-frequency events like menu-to-order conversion for Dining, focus on identifying suitable proxy metrics that occur more frequently earlier in the funnel. This could involve metrics like 'views of menu item details', 'adding items to cart (even if not ordered)', or 'time spent browsing menu'. Ensure these proxy metrics are highly correlated with the ultimate conversion goal. Additionally, consider increasing the sample size or duration if feasible, but prioritize finding a sensitive, earlier-stage metric to detect impact faster.

4. Q4

   Two overlapping experiments on Dining both affect commission revenue per order. How would you detect and manage interaction effects?

   HardStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Discuss experiment registry, factorial design, exclusion rules, and interaction terms.

   How to answer: A strong candidate would first emphasize the importance of pre-experiment planning, including defining clear metrics and potential interaction hypotheses. They would then discuss statistical methods like ANCOVA or regression analysis with interaction terms to detect significant interactions between the two experiment variables on commission revenue. For management, they would suggest either sequential experimentation, mutually exclusive user segmentation for future tests, or a multivariate testing approach if interactions are expected and can be modeled. Finally, they would highlight the need for careful interpretation of results, considering both statistical significance and practical business impact.

5. Q5

   Estimate the business impact of changing pricing, commission, delivery fee, or ad load for Dining. What assumptions and sensitivities would you model?

   MediumProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: The interviewer is testing whether you connect metrics to profit, not just top-line growth.

   How to answer: A strong answer would outline a framework for estimating business impact, starting with identifying the specific metric to optimize (e.g., revenue, profit, customer acquisition). It would then detail the key assumptions needed for each pricing lever (e.g., price elasticity of demand for diners, restaurant churn rate for commissions), and how these assumptions would be modeled (e.g., A/B testing, historical data analysis). The answer should also discuss sensitivities, such as competitor pricing, economic conditions, and seasonality, and how these external factors could influence the model's outcomes. Finally, it would touch upon the interdependencies between these levers and potential unintended consequences.

6. Q6

   How would you grow high-quality restaurant supply for Hyperpure without sacrificing customer trust?

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Include supply quality metrics, incentives, onboarding friction, and long-term health.

   How to answer: A strong answer would first define 'high-quality supply' (e.g., reliable, consistent, compliant) and 'customer trust' (e.g., food safety, ethical sourcing, fair pricing). The strategy should involve a multi-pronged approach: leveraging Zomato's existing restaurant relationships for initial outreach, implementing a rigorous vetting and onboarding process focusing on quality and compliance, and offering value propositions (e.g., better pricing, reliable supply, tech integration) that incentivize high-quality restaurants to join Hyperpure. Simultaneously, transparent communication about Hyperpure's quality standards and sourcing practices to end-consumers, along with a robust feedback loop and dispute resolution mechanism, will maintain and build customer trust.

7. Q7

   Marketing spend for Reviews increased, but menu-to-order conversion did not. How would you evaluate whether spend is inefficient or the measurement is incomplete?

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Consider incrementality, attribution, channel mix, saturation, and lagged effects.

   How to answer: A strong candidate would first define the problem and potential hypotheses (e.g., spend is inefficient, measurement is incomplete, external factors). They would then propose a structured approach to evaluate both possibilities. For inefficiency, they would suggest A/B testing different review prompting strategies, analyzing review quality vs. quantity, and segmenting users to see if specific groups respond differently. For incomplete measurement, they would investigate lag effects (reviews take time to influence), attribution models (was the conversion due to reviews or something else?), and look for proxy metrics (e.g., time spent on menu, review engagement rate) that might show early signs of impact not yet reflected in conversion.

8. Q8

   Inventory, capacity, or availability constraints limit Zomato Gold. How would you prioritize scarce supply across customers, regions, or categories?

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Use margin, fairness, service-level promises, strategic segments, and long-term retention.

   How to answer: A strong candidate would first identify the core objective: maximizing long-term customer value and Zomato's profitability. They would propose a multi-faceted prioritization strategy considering customer segmentation (e.g., high-value, loyal users vs. new users), regional demand and supply dynamics (e.g., high-density areas, emerging markets), and category profitability (e.g., high-margin restaurants, exclusive partnerships). The prioritization framework should incorporate data-driven insights on customer lifetime value, churn risk, and restaurant partner engagement, using A/B testing or controlled experiments to validate allocation strategies and adapt based on performance metrics.

9. Q9

   Evaluate the ROI of a loyalty, subscription, or membership benefit attached to Restaurant Ads. How do you avoid mistaking selection bias for program impact?

   HardProduct Analytics & Business CaseBusiness CasesZomato-specific

   Context: Use cohorts, holdouts, propensity, causal design, and margin-based economics.

   How to answer: A strong answer would first define ROI for this context (e.g., incremental ad revenue/profit vs. program cost + foregone revenue). It would then propose a methodology for calculating incremental impact, likely involving A/B testing or a quasi-experimental design (e.g., difference-in-differences) to isolate the program's effect from selection bias. Key metrics to track would include ad spend uplift, restaurant retention, order frequency/value, and program subscription rates. Finally, the answer would discuss how to mitigate selection bias through rigorous experimental design, careful control group selection, and statistical adjustments.

10. Q10

    Zomato wants to launch or expand an ads/merchant monetization product related to Hyperpure. What business metrics decide whether it is worth scaling?

    HardProduct Analytics & Business CaseBusiness CasesZomato-specific

    Context: Balance advertiser/partner value, customer experience, organic conversion, and incremental profit.

    How to answer: To decide whether to scale a Hyperpure ads/monetization product, Zomato should track merchant adoption rate, average revenue per merchant (ARPM), and the product's contribution to Hyperpure's overall profitability. Key metrics also include customer acquisition cost (CAC) for new merchants and churn rate of monetized merchants. Finally, the impact on Hyperpure's core business (e.g., increased order volume, improved retention) and overall ROI of the monetization product should be evaluated.

11. Q11

    Design an executive dashboard for Zomato's Food Delivery. What KPIs, filters, comparisons, and drill-downs would you include?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Audience is leadership; avoid vanity metrics and make actions clear.

    How to answer: A strong answer would propose an executive dashboard focused on Zomato's Food Delivery, segmenting KPIs into key areas like Operational Efficiency (e.g., Average Delivery Time, Order Fulfillment Rate), Customer Satisfaction (e.g., Customer Rating, Repeat Order Rate), and Financial Performance (e.g., Gross Merchandise Value (GMV), Average Order Value, Commission Rate). Essential filters would include Date Range, City/Region, Restaurant Type, and Payment Method. Comparisons should enable period-over-period (e.g., MoM, QoQ) and geographical analysis. Drill-downs would allow executives to investigate specific cities, top/bottom performing restaurants, or reasons for delivery delays.

12. Q12

    Design a real-time operations dashboard for Dining focused on order cancellation rate. What thresholds, alerts, and ownership model would you set?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Assume the team needs to detect issues quickly and prevent alert fatigue.

    How to answer: A strong candidate would design a dashboard with key metrics like total cancellations, cancellation rate (overall and by reason/restaurant/user segment), and average time to cancel. Visualizations would include time-series charts for trends, bar charts for breakdowns, and a prominent real-time cancellation rate gauge. Thresholds should be set at 5% (warning) and 10% (critical) for the overall cancellation rate, with alerts triggered via Slack/email to operations managers and restaurant partners. Ownership would be shared between City Operations (for overall trends and restaurant-level issues) and Product/Tech (for system-related cancellations and dashboard maintenance).

13. Q13

    You need to create a self-serve dashboard for Zomato Gold that PMs and business teams will use weekly. How do you define metrics and prevent misuse?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Include metric glossary, data freshness, filters, caveats, and examples.

    How to answer: A strong answer will first define key Zomato Gold metrics across acquisition, engagement, and retention, such as new subscriptions, active users, average order value (AOV) with Gold, and churn rate. It will then emphasize the importance of clear metric definitions, including calculation methodology, data sources, and business context, documented in a data dictionary. To prevent misuse, the candidate should propose implementing data governance, providing user training, adding contextual annotations directly on the dashboard, and establishing clear communication channels for questions and feedback. Finally, they should mention version control for metrics and dashboards to ensure consistency and traceability.

14. Q14

    Build a cohort dashboard for Restaurant Ads. Which cohort definitions, retention views, and segment controls should it have?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Prioritize clarity over chart count and make denominator definitions visible.

    How to answer: A strong answer will define cohorts based on the 'Ad Campaign Start Date' and 'Restaurant Onboarding Date' to analyze ad performance and restaurant lifecycle. Retention views should include 'Revenue Generated from Ads' and 'Number of Orders via Ads' over time, as well as 'Ad Spend' to calculate ROI. Segment controls are crucial, allowing filtering by 'Cuisine Type', 'Restaurant Tier' (e.g., premium, casual), 'Ad Campaign Type' (e.g., banner, sponsored listing), and 'Geographic Location' to identify high-performing segments and refine ad strategies. The dashboard should enable comparison across different cohorts and segments.

15. Q15

    Design role-based access and privacy rules for a Restaurant Ads dashboard that includes customer or partner-level details

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingZomato-specific

    Context: Include aggregation, masking, row-level security, audit logs, and legitimate use cases.

    How to answer: A strong answer will define distinct user roles like 'Restaurant Owner', 'Zomato Sales Rep', 'Zomato Ad Operations', and 'Zomato Leadership', each with specific data access levels. It will detail privacy rules such as anonymizing customer PII, aggregating performance data for higher roles, and restricting cross-restaurant data visibility. The candidate should also discuss implementation mechanisms like row-level security (RLS) and column-level security (CLS) within the dashboarding tool, and mention audit trails and data governance policies. Finally, they should consider the trade-off between data utility and privacy compliance (e.g., GDPR, CCPA).

Practice these with instant AI feedback in a live mock interview → Start a Zomato Data Analyst mock

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

Indicative Data Analyst pay in India: ~₹6–22 LPA (role-level range, not a Zomato-specific figure).

Other roles at Zomato

Data Analyst interviews at other companies