Flipkart Data Analyst 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 would define a clear null and alternative hypothesis for the ranking/recommendation change, focusing on improving user engagement or conversion. The primary metric should directly reflect this hypothesis, such as 'Add-to-Cart Rate' or 'Conversion Rate to Order'. Critical guardrail metrics like 'GMV per user', 'Average Order Value', and 'Return Rate' must be monitored to detect negative side effects. The randomization unit should be the 'user' (cookie ID or logged-in user ID) to ensure consistent experience, and the launch decision rule should involve statistical significance on the primary metric, positive or neutral impact on guardrails, and a pre-defined effect size.

2. Q2

   For Big Billion Days, should randomization happen at customer, session, device, seller, or city tier level? Explain the tradeoffs

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: Randomization should primarily happen at the customer level for Big Billion Days to ensure independent observations and avoid contamination, as the goal is typically to measure user-centric impacts like purchase conversion or engagement. Session or device level randomization can be considered if the experiment is very short-lived or focused on immediate, non-persistent interactions, but risks user contamination across sessions/devices. Seller or city tier level randomization introduces significant variance and makes detecting smaller effects harder due to the larger unit size, but might be necessary for platform-wide policy changes or supply-side experiments. The key trade-off lies between minimizing contamination and ensuring sufficient statistical power, considering the experiment's objective and potential spillover effects.

3. Q3

   Choose primary and guardrail metrics for a Flipkart Plus experiment aimed at improving cart-to-order conversion. What metrics would prevent a harmful launch?

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: For a Flipkart Plus cart-to-order conversion experiment, the primary metric should be 'Cart-to-Order Conversion Rate' (orders / carts initiated). Guardrail metrics are crucial to prevent negative side effects. Key guardrails include 'Average Order Value (AOV)', 'Number of Orders', 'Revenue per User', and 'Customer Lifetime Value (CLTV)' to ensure the increase in conversion isn't at the expense of order size or long-term customer value. Additionally, 'Return Rate' and 'Customer Support Contact Rate' are important to monitor for product quality or user experience issues.

4. Q4

   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 sample ratio mismatch (SRM), first check the randomization unit (e.g., user ID, device ID) and ensure consistent assignment logic. Next, analyze the SRM across various dimensions like device type, geography, and user cohorts to identify specific segments where the mismatch is more pronounced. Validate the data pipeline for any errors in logging or assignment, and finally, perform a statistical test (e.g., chi-squared test) on pre-experiment metrics to confirm if the observed deviation is statistically significant or merely due to chance.

5. Q5

   The Electronics Store 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 TestingFlipkart-specific

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

   How to answer: Explain that peeking early in an A/B test without proper statistical correction inflates the Type I error rate, leading to false positives. Discuss the concept of sequential testing, where statistical boundaries are pre-defined to allow for early stopping while maintaining the desired alpha level. Propose methods like using O'Brien-Fleming boundaries or other group sequential methods to adjust p-values or confidence intervals for multiple comparisons, ensuring the validity of the early stop decision. Emphasize the importance of pre-determining these methods and stopping rules before the experiment begins.

6. Q6

   A new Seller Hub feature shows a large week-1 lift in cart-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 TestingFlipkart-specific

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

   How to answer: The fading effect could be due to novelty effect, where users initially engage more with the new feature but revert to previous behavior as the novelty wears off. It could also be attributed to selection bias if the initial user group was more receptive, or a learning curve where users take time to fully integrate the feature into their workflow. To design the test duration, one should consider the typical user lifecycle and business cycles, ensuring the test runs long enough to capture both initial impact and sustained behavior, ideally spanning multiple full cycles (e.g., 4-8 weeks, or longer if seasonal).

7. Q7

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

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: Network effects in a marketplace like Flipkart mean that the actions of treatment users (e.g., sellers getting a new feature) can indirectly influence control users (e.g., buyers interacting with those sellers, or other sellers competing with them). This leads to interference, where the control group is not truly isolated, biasing the experiment's results. Specifically, it can lead to an underestimation of positive treatment effects if control users benefit indirectly, or an overestimation if they are negatively impacted. The bias makes it difficult to attribute observed changes solely to the treatment.

8. Q8

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

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-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 cart-to-order conversion during BBD, one should consider using a proxy metric that is highly correlated with the ultimate conversion but occurs more frequently earlier in the funnel, such as 'add-to-cart' or 'proceed-to-checkout' clicks. Alternatively, increasing the sample size by broadening the experiment's scope (e.g., across more product categories or user segments) or extending the experiment duration slightly, if feasible, can boost power. Utilizing a sequential testing approach could also allow for earlier stopping if a significant effect is detected, or for re-evaluating the experiment's power mid-way. Finally, ensuring the minimum detectable effect (MDE) is realistically set for the business impact can help manage power requirements.

9. Q9

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

   MediumStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

   How to answer: A strong answer would propose a geo-level experiment design, such as randomizing cities or city tiers (e.g., Tier 1 vs. Tier 2/3) into control and treatment groups for Flipkart Plus features. It would explain that geo-level randomization is superior when there's a risk of 'spillover effects' or 'network effects' between users, where the treatment of one user might influence another's behavior (e.g., word-of-mouth about Plus benefits). The candidate should then detail the analytical downsides, including reduced statistical power due to fewer experimental units (cities vs. users), increased variance, and the challenge of controlling for confounding variables that differ between geos, making it harder to isolate the treatment effect.

10. Q10

    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), I would first segment users by 'new vs. existing' and 'category' to identify specific subgroups. Then, I would perform separate A/B test analyses for each subgroup, focusing on statistical significance and practical impact within those segments. Techniques like CUPED or ANCOVA could be applied within subgroups to reduce variance and increase sensitivity. Finally, I would use interaction terms in regression models or Causal Forests to formally test for HTE and understand the drivers of differential impact.

11. Q11

    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 recommendation would involve a phased rollout, starting with a small, targeted segment where the conversion uplift outweighs the breach rate impact. This requires quantifying the monetary value of increased orders versus the cost of promise breaches (e.g., customer service, returns, reputational damage). Concurrently, the team should investigate the root cause of the worsened breach rate and explore mitigation strategies (e.g., inventory optimization, logistics adjustments) before a broader launch. A continuous monitoring plan with clear success metrics and rollback procedures is crucial.

12. Q12

    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'd start with a small percentage (e.g., 1-5%) of low-impact sellers, gradually increasing exposure while monitoring key metrics and system health. Holdback involves reserving a small, representative control group (e.g., 5-10%) that never sees the new feature, allowing for long-term impact assessment against the original baseline. Post-launch monitoring requires establishing a dashboard with critical business metrics (e.g., seller NPS, GMV, fulfillment rates, support tickets) and technical metrics (latency, error rates) with clear alerts, conducting regular deep-dives, and potentially running follow-up experiments.

13. Q13

    Midway through the Flipkart Marketplace test, tracking for Flipkart Plus changed. How would you decide whether the experiment results are still usable?

    HardStatistics & Experimentation RoundA/B TestingFlipkart-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 tracking change for Flipkart Plus relative to the experiment's start and the change point. Then, analyze the impact on key metrics for both control and treatment groups before and after the change. If the change introduced a systematic bias affecting one group more than the other, or significantly altered the underlying user behavior for Flipkart Plus members, the results are likely compromised. If the change was minor, applied uniformly, and did not materially alter the measurement of the primary success metrics, the data might still be usable with appropriate caveats or adjustments.

14. Q14

    Two overlapping experiments on Big Billion Days both affect GMV after returns. How would you detect and manage interaction effects?

    HardStatistics & Experimentation RoundA/B TestingFlipkart-specific

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

    How to answer: A strong candidate would first identify the need for a robust experimental design, such as a factorial design, to explicitly test for interaction effects between the two overlapping experiments. They would explain how to analyze the results using statistical methods like ANOVA, looking for significant interaction terms beyond the main effects. If interaction effects are detected, they would discuss strategies like segmenting the user base, adjusting the rollout strategy, or re-designing one or both experiments to mitigate negative interactions or capitalize on positive ones. Finally, they would emphasize the importance of pre-experiment power analysis and clear hypothesis formulation for interaction effects.

15. Q15

    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 answer would begin by clarifying the scope (e.g., specific marketplace, product categories, geographies) and then structure the diagnosis into internal and external factors. Internally, candidates should investigate operational issues (e.g., tech glitches, payment failures, logistics disruptions, seller onboarding/offboarding) and marketing/promotional changes. Externally, they should consider competitor actions, macroeconomic shifts, and seasonal trends. The diagnosis should involve data deep dives into key metrics like GMV, conversion rates, average order value, traffic, and seller performance, followed by hypothesis generation and validation.

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

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

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

Other roles at Flipkart

Data Analyst interviews at other companies