Swiggy Analytics Engineer Interview Questions (2026)

1. 1Problem Solving Screen45 minMedium

   One or two medium DSA problems in a shared editor, judged on working code and complexity analysis.

2. 2Problem Solving / DSA Round 255 minHard

   Harder algorithmic round covering trees, graphs, or DP, often with a follow-up that adds a real-world constraint.

3. 3Design Round (LLD/HLD)60 minHard

   LLD machine-coding of a module (e.g. a splitwise-style ledger or rate limiter) for SDE-1/2, or HLD of a delivery-scale system for SDE-3 and above.

4. 4Data / Analytics Round50 minMedium

   SQL on order and delivery datasets plus a metrics case such as diagnosing a drop in Instamart conversion or designing an experiment.

5. 5Hiring Manager Round50 minMedium

   Deep project walkthrough plus situational behavioral questions on ownership, customer focus, and handling conflicting priorities.

6. 6HR Round30 minEasy

   Offer discussion covering compensation structure, ESOPs, notice period, and team allocation.

1. Q1

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

   MediumStatistics & Experimentation RoundA/B TestingSwiggy-specific

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

   How to answer: Randomization for Instamart should primarily happen at the customer level to ensure consistent user experience and accurate measurement of user-centric metrics like conversion rate, retention, and average order value. Randomizing at the session or device level risks a single user seeing multiple variants, leading to contamination and biased results. While restaurant or city level randomization might be considered for specific experiments (e.g., supply-side changes, localized features), it introduces higher variance and makes it harder to detect smaller effects, requiring significantly larger sample sizes or more complex analysis to account for network effects.

2. Q2

   The Genie experiment lifts order conversion rate overall, but only for new users and only in one meal_slot. How would you evaluate heterogeneous treatment effects?

   HardStatistics & Experimentation RoundA/B TestingSwiggy-specific

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

   How to answer: A strong candidate would first acknowledge the overall positive lift but immediately highlight the need for segmentation by user type (new vs. existing) and meal_slot. They would propose using interaction terms in a regression model (e.g., OLS or logistic regression for conversion) to formally test for heterogeneous treatment effects (HTE). This involves creating interaction variables like `treatment * new_user` and `treatment * meal_slot_X` and assessing their statistical significance. Finally, they would discuss the implications for rollout strategy, recommending a targeted launch to the identified segments rather than a full-scale rollout.

3. Q3

   Swiggy'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 CasesSwiggy-specific

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

   How to answer: A strong business case would begin by segmenting the revenue drop by key dimensions like geography (city/zone), customer type (new/existing), restaurant type (cuisine/chain), and order characteristics (time of day, average order value). Next, identify if the drop is due to fewer orders or lower average order value (AOV), and then deep dive into the contributing factors for each. This involves analyzing user behavior funnels (impressions to order completion), restaurant supply changes, competitor activity, and internal operational issues (app bugs, delivery partner availability). Finally, prioritize potential drivers based on data impact and ease of investigation, proposing specific data points to validate hypotheses.

4. Q4

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

   MediumProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong answer would frame the business impact around key metrics like Gross Merchandise Value (GMV), Revenue, Contribution Margin (CM), and Customer Lifetime Value (CLTV). It would involve modeling the elasticity of demand for each change (pricing, commission, delivery fee, ad load) and its subsequent impact on order volume, average order value, and take rate. Key assumptions would include price elasticity, competitor actions, customer acquisition cost, and retention rates. Sensitivity analysis would explore a range of elasticity values and their effect on profitability and market share.

5. Q5

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

   HardProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong candidate would first define 'high-quality supply' (e.g., restaurants with good ratings, low cancellation rates, diverse cuisine, high order volume potential). They would then propose strategies to identify and onboard these restaurants, such as data-driven targeting (using existing Swiggy data), dedicated sales teams, and incentive programs (e.g., initial ad credits, performance bonuses). Crucially, they would address customer trust by ensuring ad placements are clearly labeled, relevant to user preferences, and do not promote low-quality or irrelevant restaurants, potentially using A/B testing to monitor user experience metrics.

6. Q6

   Marketing spend for Delivery Partner App increased, but order conversion rate did not. How would you evaluate whether spend is inefficient or the measurement is incomplete?

   HardProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong candidate would first define 'order conversion rate' and identify potential lagging indicators or attribution model issues. They would propose segmenting the marketing spend (e.g., by channel, geography, campaign type) and the user base (new vs. existing, app install source) to pinpoint specific inefficiencies or areas of impact. They would then suggest investigating external factors (competitor activity, seasonality) and internal factors (app performance, A/B tests on landing pages) that could influence conversion. Finally, they would recommend evaluating the attribution model's accuracy and completeness, considering multi-touchpoints and the time lag between impression and conversion.

7. Q7

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

   HardProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong answer would first define the objective, likely maximizing long-term customer lifetime value or overall platform profitability. Then, it would propose a multi-faceted prioritization framework considering factors like customer segmentation (e.g., high-value, new users), strategic importance of regions (e.g., growth markets, competitive pressure), and category profitability/strategic fit (e.g., high-margin restaurants, grocery). Finally, it would discuss the data and metrics needed to inform these decisions and the iterative nature of such a prioritization process, emphasizing A/B testing and continuous monitoring.

8. Q8

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

   HardProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong answer would first define key metrics for ROI (e.g., incremental GMV, retention, frequency, AOV) and the costs associated with the Genie benefit. It would then propose a robust experimental design, likely an A/B test or a quasi-experimental method like Difference-in-Differences, to isolate program impact from selection bias. The answer should detail how to construct control and treatment groups, measure the incremental lift, and calculate the net ROI. Finally, it should acknowledge potential confounding factors and discuss ongoing monitoring and iteration.

9. Q9

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

   HardProduct Analytics & Business CaseBusiness CasesSwiggy-specific

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

   How to answer: A strong answer would structure the review into three main sections: 'What Happened' (key metrics and trends, e.g., DAU, session duration, crash rate, order acceptance rate, earnings per hour), 'Why It Happened' (root cause analysis for observed trends, linking to recent feature releases, A/B tests, operational changes, or external factors like weather/competitor actions), and 'What Next' (actionable recommendations with clear ownership, impact, and timelines, focusing on product improvements, operational adjustments, or further investigation). The candidate should select 2-3 critical metrics and provide a data-driven narrative, demonstrating an understanding of the Delivery Partner App's ecosystem and Swiggy's business objectives.

10. Q10

    Design a real-time operations dashboard for Instamart focused on delivery SLA breach rate. What thresholds, alerts, and ownership model would you set?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingSwiggy-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 current SLA breach rate (overall and by city/store), number of breached orders, and average delay for breached orders, updated every 1-5 minutes. Visualizations should include a trend line for breach rate over the last hour/day and a breakdown by root cause (e.g., rider unavailability, store delay, traffic). Thresholds would be set at 2% (amber, monitor) and 5% (red, immediate action), triggering alerts via Slack/PagerDuty to city operations managers and on-call tech teams. Ownership involves city ops for immediate resolution, central ops for trend analysis, and product/engineering for underlying system issues.

11. Q11

    Set alert thresholds for order conversion rate, contribution margin per order, and delivery SLA breach rate in Delivery Partner App. How would you distinguish noise from a real incident?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingSwiggy-specific

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

    How to answer: A strong answer would define initial alert thresholds using historical data (e.g., 2-3 standard deviations or percentage drops) and business context. To distinguish noise from real incidents, candidates should propose a multi-faceted approach: cross-referencing with other metrics (e.g., app crashes, payment failures), segmenting data (e.g., by city, time of day, app version) to localize the issue, and considering external factors (e.g., major events, network outages). They should also mention implementing a delay or requiring sustained breaches before triggering high-priority alerts to avoid transient spikes.

12. Q12

    Create a dashboard narrative for Growth lead explaining why order conversion rate changed for Swiggy One. What charts would you show first?

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingSwiggy-specific

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

    How to answer: The dashboard narrative for the Growth Lead should start with an executive summary highlighting the overall change in Swiggy One order conversion rate (OCR) and its impact on key business metrics like GMV and subscription renewals. The initial charts should disaggregate the OCR change by critical dimensions: user segment (new vs. existing Swiggy One subscribers, free trial vs. paid), platform (iOS vs. Android vs. Web), and time (daily/weekly trends, pre/post-feature launch). Subsequent analysis would drill down into funnel drop-offs (e.g., cart abandonment, payment failures), A/B test impacts, and potential external factors (e.g., competitor promotions, app updates).

13. Q13

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

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingSwiggy-specific

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

    How to answer: A strong answer will propose a multi-layered approach to role-based access control (RBAC) and data privacy for the Genie dashboard. This includes defining distinct user roles (e.g., L1 Support, L2 Operations, City Head, Product Manager) with specific permissions for data visibility (e.g., aggregated vs. granular, specific regions/partners). Data masking and anonymization techniques should be applied for sensitive PII/SPI, especially for lower-level roles. Implement row-level security (RLS) based on user roles and associated attributes (e.g., city, partner ID) to filter data dynamically. Finally, discuss audit logging and regular access reviews to ensure compliance and prevent unauthorized access.

14. Q14

    Delivery Partner App has rising churn or inactivity among high-value customers. How would you quantify the problem and identify drivers?

    MediumProduct Analytics & Business CaseProduct AnalyticsSwiggy-specific

    Context: Include cohort trends, leading indicators, competitor/substitution signals, and service quality.

    How to answer: Quantify the problem by defining 'high-value customer' (e.g., top X% by deliveries/earnings) and 'churn/inactivity' (e.g., no deliveries for Y days after Z active period). Measure churn rate, average revenue per active partner (ARPP), and lifetime value (LTV) for this segment, comparing it to previous periods or other segments. To identify drivers, use a funnel analysis (login -> online -> accept order -> complete order) to pinpoint drop-off points. Supplement with cohort analysis by acquisition channel or tenure, A/B test results of recent feature changes, and qualitative insights from partner surveys or support tickets, looking for correlations with the observed churn.

15. Q15

    For Food Delivery, how would you measure supply-demand balance between customers and restaurants?

    MediumProduct Analytics & Business CaseProduct AnalyticsSwiggy-specific

    Context: Examples include availability, wait time, search zero-results, acceptance, inventory, or partner response rate.

    How to answer: A strong answer would define supply (restaurant availability, capacity) and demand (customer orders, search volume) and propose key metrics for each. It would then suggest metrics to measure the balance, such as 'Order Acceptance Rate' (restaurants accepting orders), 'Customer Wait Time' (time from order to delivery), 'Restaurant Online Rate' vs. 'Customer Session Rate', and 'Cancellation Rate due to Supply'. Finally, it would discuss how to segment these metrics by time of day, geography, and restaurant tier to identify specific imbalances and suggest potential actions like dynamic pricing or supply incentives.

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

Prepare coding/SQL and analytical cases; show product/data sense; quantify impact

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

Other roles at Swiggy

Analytics Engineer interviews at other companies