Flipkart Analytics Engineer Interview Questions (2026)

1. 1Online Coding Screen60 minMedium

   Timed online test or telephonic round with 2-3 DSA problems to qualify for the onsite loop; campus entry often via Flipkart GRiD.

2. 2Machine Coding Round90 minHard

   Build a small working application (e.g. parking lot, Snake & Ladder, splitwise) with clean object-oriented design, working demo, and extensibility within a strict time box.

3. 3PS/DS Round60 minHard

   Two hard problem-solving/data-structures questions where optimal complexity and bug-free code are expected.

4. 4System Design Round60 minHard

   HLD of an e-commerce-scale system such as flash-sale inventory, cart service, or order pipeline for Big Billion Days traffic.

5. 5Hiring Manager Round50 minMedium

   Project deep dives and situational behavioral questions assessing ownership, decision-making at scale, and team fit.

6. 6HR Round30 minEasy

   Compensation, level mapping, ESOPs, and joining logistics.

1. Q1

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

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-specific

   Context: Context: Flipkart wants to grow event-sale conversion without increasing cancellations and returns.

   How to answer: A strong answer will define a clear, testable hypothesis for the ranking/recommendation change, such as 'The new algorithm will increase user engagement (e.g., add-to-cart rate) without negatively impacting revenue or user experience.' The primary metric should directly reflect the hypothesis, like 'Add-to-Cart Rate per Session' or 'Conversion Rate.' Guardrail metrics are crucial for Flipkart's marketplace, including 'Average Order Value,' 'GMV per User,' 'Session Duration,' and 'Number of Complaints,' to detect unintended negative consequences. The randomization unit should be 'User ID' to ensure consistent experience, and the launch decision rule will involve statistical significance on the primary metric, ensuring guardrails are not violated, and considering a minimum detectable effect.

2. Q2

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

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-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 verify the randomization unit (user, session, etc.) and ensure consistent assignment logic. Next, check for implementation bugs in the bucketing mechanism, such as incorrect modulo operations or edge case handling. Analyze the traffic source and distribution over time to identify external factors or specific user segments disproportionately routed. Finally, perform a statistical significance test (e.g., chi-squared) on the observed split to confirm if the deviation is statistically significant or merely random chance.

3. Q3

   The Fashion Store experiment lifts cart-to-order conversion overall, but only for new users and only in one category. How would you evaluate heterogeneous treatment effects?

   HardStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: To evaluate heterogeneous treatment effects (HTE), first define relevant subgroups based on user tenure (new vs. existing) and product categories. Then, perform subgroup analysis by running separate t-tests or chi-squared tests for cart-to-order conversion within each defined segment. For more robust analysis, especially with multiple subgroups, consider using regression-based methods like interaction terms in a linear or logistic regression model, or Causal Forests for non-linear relationships. Finally, validate findings by checking for statistical significance, practical significance, and potential confounding factors, ensuring the observed effects are not due to chance or other variables.

4. Q4

   Treatment improves cart-to-order conversion but worsens promise breach rate for Electronics Store. Walk through a launch recommendation

   HardStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: A strong candidate would first identify the conflicting metrics and the need for a holistic view, likely through a weighted scoring model or a financial impact assessment. They would propose quantifying the monetary value of improved conversion versus the cost of increased breaches, considering factors like customer lifetime value and potential churn. The recommendation would then hinge on which impact is greater, potentially suggesting a phased rollout, a targeted launch (e.g., specific customer segments or product categories), or further experimentation to mitigate the breach rate while retaining conversion gains.

5. Q5

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

   HardStatistics & Experimentation RoundA/B TestingFlipkart-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., 5-10%) of low-impact sellers, gradually increasing exposure while closely monitoring key operational metrics and system health. Holdback involves reserving a small, representative control group (e.g., 1-2%) from the experiment for a longer duration to assess long-term novelty effects and ensure no unforeseen negative impacts. Post-launch monitoring requires establishing a dashboard with key business metrics (e.g., seller NPS, GMV, listing creation rate, support tickets), system performance metrics (latency, error rates), and A/B test specific metrics, with automated alerts for significant deviations. This continuous monitoring helps detect regressions, seasonality impacts, and long-term treatment effects.

6. Q6

   Flipkart's Flipkart Marketplace 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 CasesFlipkart-specific

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

   How to answer: A strong candidate would structure their diagnosis by first clarifying the scope (Marketplace revenue vs. other segments) and the exact time period. They would then propose a top-down approach, starting with the core revenue formula (GMV x Commission Rate) and breaking down GMV into its components: (Number of Orders x Average Order Value) or (Number of Sellers x Number of Listings x Conversion Rate x AOV). The diagnosis would involve checking data integrity, then systematically analyzing each component for a 10% drop, segmenting by key dimensions like category, seller tier, customer segment, and region. Finally, they would prioritize potential root causes (e.g., policy changes, tech issues, competitor actions, seasonality) and suggest data-driven next steps for validation.

7. Q7

   Flipkart is considering launching Flipkart Plus in a new city tier. Build a decision framework and the first 90-day success metrics

   MediumProduct Analytics & Business CaseBusiness CasesFlipkart-specific

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

   How to answer: A strong framework would start with defining the objective (e.g., market penetration, customer acquisition, revenue growth) and then identify key decision criteria such as market potential (demographics, existing competition), operational feasibility (logistics, delivery network), and financial viability (CAC, LTV, breakeven). The 90-day success metrics should be tiered: initial operational metrics (delivery success rate, fulfillment time), early adoption metrics (new Plus subscribers, engagement with Plus benefits), and financial indicators (Plus revenue, ARPU of Plus members). A/B testing or pilot programs in select areas could be part of the decision framework to validate assumptions before a full-scale launch.

8. Q8

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

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-specific

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

   How to answer: A strong candidate would first define the problem: increased spend without conversion lift. They would then propose a structured approach to evaluate inefficiency vs. incomplete measurement. This involves analyzing marketing channel performance, attribution models, and potential external factors affecting conversion. Finally, they would suggest A/B testing or controlled experiments to isolate the impact of the increased spend and recommend actionable next steps based on findings.

9. Q9

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

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-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 into key sections: Executive Summary, What Happened (Key Metrics & Trends), Why It Happened (Root Causes & Analysis), and What's Next (Recommendations & Action Plan). It should identify critical Seller Hub metrics (e.g., seller NPS, active sellers, GMV from new sellers, feature adoption) and analyze their trends, linking performance to underlying drivers like new feature launches, policy changes, or market dynamics. Recommendations must be data-driven, actionable, and prioritized, focusing on improving seller experience and platform growth.

10. Q10

    Design a real-time operations dashboard for Big Billion Days focused on promise breach rate. What thresholds, alerts, and ownership model would you set?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-specific

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

    How to answer: A strong answer would outline a dashboard with key metrics like real-time promise breach rate (overall and segmented by product, region, logistics partner), total orders, and orders at risk. It would define clear thresholds (e.g., green <1%, yellow 1-2%, red >2%) and trigger automated alerts via Slack/email to specific teams (e.g., logistics operations, customer service, tech support) based on severity. The ownership model would assign primary responsibility for monitoring and resolution to a central 'Big Billion Days War Room' with clear escalation paths to functional teams for investigation and mitigation.

11. Q11

    Create a dashboard narrative for Logistics lead explaining why cart-to-order conversion changed for Flipkart Plus. What charts would you show first?

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-specific

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

    How to answer: The narrative should start by clearly stating the observed change in cart-to-order conversion for Flipkart Plus, including the magnitude and direction. The initial charts should focus on breaking down the conversion funnel (e.g., cart adds, checkout initiated, payment successful) to pinpoint the exact stage where the drop occurred. Subsequent analysis should investigate potential drivers such as changes in product availability, shipping options/speed, payment gateway issues, or A/B test impacts specific to Plus members. The narrative should conclude with actionable recommendations based on the identified root cause.

12. Q12

    Big Billion Days's conversion from listing_view to purchase dropped 15% week over week. Walk through your diagnosis plan

    EasyProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

    Context: Assume no single obvious outage has been announced.

    How to answer: Start by clarifying the exact timeframes and product categories affected. Then, investigate potential data issues (tracking errors, definition changes) before looking at external factors (marketing changes, competitor actions). Next, deep dive into user behavior within the funnel: analyze listing page changes (price, stock, reviews), cart abandonment rates, and payment gateway success rates. Finally, segment the drop by device, region, and user cohorts to identify specific impacted groups.

13. Q13

    You own the weekly business review for Flipkart Marketplace. What metrics go on the first page, and what drill-downs should be ready?

    HardProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

    Context: Design for executive actionability rather than metric dumping.

    How to answer: A strong answer will prioritize key marketplace health metrics on the first page, focusing on GMV, Number of Orders, and Active Sellers/Buyers, as these represent the core transaction volume and participant engagement. For drill-downs, candidates should propose breakdowns by product category, seller tier (e.g., gold, silver), geographic region, and new vs. repeat customers/sellers to understand performance drivers. Additionally, key operational metrics like fulfillment rate, return rate, and seller NPS should be readily available for deeper dives into marketplace efficiency and satisfaction. The candidate should also mention week-over-week and year-over-year comparisons for all primary metrics.

14. Q14

    A new Big Billion Days initiative may cannibalize Flipkart Plus. How would you measure incremental value rather than just shifted demand?

    HardProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

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

    How to answer: To measure incremental value, establish a robust A/B test or a quasi-experimental design (e.g., difference-in-differences) where a control group does not receive the Big Billion Days (BBD) initiative. Define clear success metrics beyond just BBD sales, such as overall customer lifetime value (CLTV), retention rates, average order value (AOV) across all Flipkart properties, and cross-category purchases for both groups. Analyze the net change in these metrics for the BBD initiative group compared to the control group, specifically looking for uplift that cannot be attributed to a decline in Flipkart Plus engagement or other existing programs. Segment analysis by customer tenure and Plus membership status will further isolate true incremental value versus internal cannibalization.

15. Q15

    Define success for an onboarding, referral, or activation flow in Flipkart Plus. What would you measure on day 0, day 7, and day 30?

    HardProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

    Context: Include activation quality, retention, referral quality, and fraud/abuse guardrails.

    How to answer: Success for an onboarding, referral, or activation flow in Flipkart Plus is defined by the user's progression through the funnel and their sustained engagement with the Plus program's core value propositions. For onboarding, this means completing setup and making a first Plus-eligible purchase. For referral, it's the referred user's activation and subsequent engagement. For activation, it's the user performing the key action that unlocks Plus benefits and then utilizing those benefits. Day 0 metrics focus on immediate completion rates and initial usage, Day 7 on early retention and feature adoption, and Day 30 on sustained engagement, repeat purchases, and contribution to Plus program health (e.g., LTV, churn reduction).

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

Practice DSA + machine-coding rounds; prepare system design; know your projects

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

Other roles at Flipkart

Analytics Engineer interviews at other companies