Zomato Business 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

   Design an A/B test for a new Food Delivery ranking or recommendation change. Define hypothesis, primary metric, guardrails, randomization unit, and launch decision rule

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

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

   How to answer: A strong answer will define a clear hypothesis, such as 'The new ranking algorithm will increase user engagement and order conversion.' The primary metric should directly reflect this, like 'Orders per user' or 'Conversion rate from search/recommendation to order.' Guardrail metrics are crucial, including 'Average delivery time,' 'Cancellation rate,' and 'Customer support contacts' to ensure no negative impact on user experience or operations. The randomization unit should be the 'User ID' to maintain consistency across sessions, and the launch decision rule should involve statistical significance (e.g., p < 0.05) on the primary metric, sustained over a defined period, with no significant negative impact on guardrails.

2. Q2

   For Dining, should randomization happen at customer, session, device, restaurant, or city level? Explain the tradeoffs

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Consider cross-device behavior, interference, marketplace effects, and operational feasibility.

   How to answer: Randomization for Zomato Dining A/B tests should primarily happen at the customer level to ensure independent observations and minimize bias, especially for features impacting individual user behavior. Session or device level randomization can be considered for very short-term, immediate interaction changes, but risks user contamination across sessions/devices. Restaurant level randomization is appropriate when the feature directly impacts the restaurant's operations or offerings, but requires careful consideration of network effects and potential for user exposure to both variants. City level randomization is generally too broad for Dining features unless the experiment involves a fundamental change in market strategy or regulatory compliance, and significantly reduces statistical power.

3. Q3

   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 for a Zomato Gold experiment to improve menu-to-order conversion should be 'Order Conversion Rate (Menu View to Order)'. This directly measures the desired behavior change. Guardrail metrics are crucial to prevent negative side effects. Key guardrails would include 'Average Order Value (AOV)', 'Number of Orders per User', and 'Restaurant Partner Satisfaction Score' (or a proxy like 'Order Cancellation Rate'). These guardrails ensure the experiment doesn't cannibalize revenue, reduce user engagement, or harm restaurant relationships.

4. Q4

   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 a 52/48 split instead of 50/50, first check the randomization unit (e.g., user ID, restaurant ID) and ensure consistent assignment logic. Next, analyze pre-experiment metrics for both groups to detect any existing differences or biases. Verify the implementation of the A/B testing framework, looking for bugs in the assignment script, filtering rules, or data logging. Finally, examine traffic volume and potential edge cases (e.g., new users, specific device types) that might disproportionately affect one group.

5. Q5

   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: A strong candidate would first acknowledge the PM's enthusiasm but immediately flag the risks of early stopping due to peeking. They would explain that peeking inflates Type I error rates, leading to false positives. The candidate should then propose using sequential testing methods (like Always Valid p-values or Bayesian approaches) if early stopping is truly desired, or, ideally, advocate for letting the experiment run its pre-determined course to achieve statistical significance and power. Finally, they would emphasize the importance of pre-analysis planning for experiment duration and sample size.

6. Q6

   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 lift suggests a novelty effect, where initial user engagement with the new Reviews feature is high due to its newness, but then normalizes as users become accustomed to it or find it less impactful over time. Other explanations could include selection bias if early adopters are more engaged, or a seasonal/external factor coinciding with week 1. To design the test duration, one should consider the typical user lifecycle and decision-making process for ordering food, aiming for at least 4-6 weeks to observe stabilization and account for repeat usage patterns, potentially longer for high-impact features. A control group comparison over this extended period is crucial to differentiate novelty from sustained impact.

7. Q7

   In a marketplace-like Food Delivery feature, treatment users may affect control users. How would network effects or interference bias the experiment?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Examples include restaurant supply, content inventory, delivery capacity, or pricing pressure.

   How to answer: Network effects in a food delivery marketplace can significantly bias A/B tests. If treatment users (e.g., those with a new discount) order more, they might deplete a shared resource like delivery rider availability, leading to slower deliveries for control users. Conversely, if treatment users experience a negative change (e.g., higher prices), they might order less, freeing up resources for control users. This interference means the control group's observed behavior is not a true baseline, as it's influenced by the treatment group's actions, leading to an inaccurate estimation of the treatment's true impact.

8. Q8

   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 the low-frequency conversion, I would first redefine the success metric to an earlier, higher-frequency proxy event, such as 'add item to cart' or 'view cart', rather than 'order placed'. I would then consider a sequential testing approach or Bayesian A/B testing to allow for earlier stopping if a clear winner emerges. Additionally, I would explore increasing the sample size by broadening the experiment's scope (e.g., across more cities or user segments) or extending the experiment duration slightly, while carefully monitoring for novelty effects. Finally, I would ensure the minimum detectable effect (MDE) is set realistically, acknowledging the inherent variance in low-frequency events.

9. Q9

   Design a geo or city-level experiment for Zomato Gold. When is this better than user-level randomization, and what are the analytical downsides?

   MediumStatistics & Experimentation RoundA/B TestingZomato-specific

   Context: Use matched markets, pre-period balancing, spillover checks, and fewer experimental units.

   How to answer: A strong candidate would propose a geo-level experiment by selecting a set of comparable cities or micro-markets (e.g., neighborhoods within a large city) for treatment and control groups, ensuring pre-experiment metrics are similar. They would define key metrics like Zomato Gold subscriptions, order frequency, average order value, and retention. Geo-level randomization is superior when there are significant network effects, spillover effects between users, or when the feature itself requires market-wide adoption (e.g., merchant-side changes). Analytical downsides include lower statistical power due to fewer experimental units, increased susceptibility to confounding variables unique to specific geos, and potential for selection bias if geo-assignment isn't truly random or comparable.

10. Q10

    The Restaurant Ads experiment lifts menu-to-order conversion overall, but only for new users and only in one cuisine. How would you evaluate heterogeneous treatment effects?

    HardStatistics & Experimentation RoundA/B TestingZomato-specific

    Context: Balance pre-planned segments with exploratory slicing and multiple testing risk.

    How to answer: A strong candidate would first identify the need to segment the data by user type (new vs. existing) and cuisine type to isolate the observed effects. They would then propose statistical methods like interaction terms in regression models or subgroup analysis with appropriate multiple testing corrections to formally test for heterogeneous treatment effects. The evaluation would involve comparing the lift in menu-to-order conversion within the specific new user/cuisine segment against other segments and the overall average. Finally, they would discuss the business implications of these findings, such as targeted ad campaigns or further investigation into the 'why' behind the heterogeneity.

11. Q11

    Treatment improves menu-to-order conversion but worsens order cancellation rate for Hyperpure. Walk through a launch recommendation

    HardStatistics & Experimentation RoundA/B TestingZomato-specific

    Context: Make a decision under conflicting metrics and quantify tradeoffs for stakeholders.

    How to answer: A strong recommendation would involve quantifying the net impact of the treatment by calculating the monetary value of the improved conversion versus the cost of increased cancellations, specifically for Hyperpure orders. This requires understanding the average order value, gross margin, and the cost associated with a cancelled Hyperpure order (e.g., logistics, wasted food, customer service). If the net monetary gain is positive and significant, a phased rollout or targeted launch to specific user segments or geographies might be recommended, alongside further investigation into the root causes of the increased cancellations. If the net impact is negative or marginal, the treatment should be iterated upon or discarded, focusing on mitigating the cancellation increase.

12. Q12

    How would you design ramp-up, holdback, and post-launch monitoring for a successful Reviews A/B test?

    HardStatistics & Experimentation RoundA/B TestingZomato-specific

    Context: Include ramp stages, persistent holdback, alert thresholds, rollback criteria, and owner accountability.

    How to answer: For ramp-up, I would start with a small percentage (e.g., 1-5%) of traffic, primarily in a single, less critical market, closely monitoring key operational metrics like error rates and latency to ensure stability before gradually increasing exposure. Holdback would involve reserving a small, representative segment of the eligible user base (e.g., 2-5%) from the experiment for a longer duration to assess long-term novelty effects and potential cannibalization against the original experience. Post-launch monitoring would establish a dashboard tracking primary metrics (review submission rate, quality), guardrail metrics (app crashes, uninstalls), and business impact metrics (restaurant engagement, order volume) for at least 2-4 weeks, comparing the launched experience against the holdback group and historical trends.

13. Q13

    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: First, identify the exact nature and timing of the Zomato Gold tracking change relative to the experiment's start and the point of change. Then, analyze if the change impacts the primary experiment metrics or key secondary metrics, especially if Zomato Gold membership or usage is a significant factor in the experiment's hypothesis. Compare pre-change and post-change data for both control and treatment groups to detect any sudden shifts or discrepancies in tracking. Finally, based on the impact assessment, decide whether to discard the post-change data, adjust for the change, or restart the experiment.

14. Q14

    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 primary metrics (commission revenue per order) and secondary metrics, and ensuring proper experiment setup with distinct user segments or sequential rollouts if possible. To detect interaction effects, they would propose analyzing the combined treatment group's performance against a pure control, and also comparing each individual experiment's treatment group against the combined treatment group. Statistical methods like ANOVA or regression analysis with interaction terms would be key for quantifying the significance of any observed interactions. Management strategies would include sequential experimentation, segmenting user populations, or designing a factorial experiment if interactions are anticipated and need to be measured directly.

15. Q15

    Zomato's Food Delivery revenue suddenly drops 10% week over week. Structure a business case to diagnose the issue and identify the most likely drivers

    MediumProduct Analytics & Business CaseBusiness CasesZomato-specific

    Context: Consider traffic, conversion, pricing, mix, supply/inventory, outages, marketing, and seasonality.

    How to answer: A strong business case would begin by clarifying the 10% drop, looking at absolute numbers, specific regions, customer segments, and product categories affected. The diagnosis would then follow a structured approach, starting with external factors (competitor actions, economic shifts, regulatory changes, seasonality/events) before moving to internal factors (app/tech issues, delivery partner availability/efficiency, pricing/promotions, menu availability/quality, customer service). Data analysis would be key at each stage, prioritizing drivers based on impact and ease of validation, leading to actionable recommendations for investigation and resolution.

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

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

Indicative Business Analyst pay in India: ~₹7–26 LPA (role-level range, not a Zomato-specific figure).

Other roles at Zomato

Business Analyst interviews at other companies