Flipkart Business 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 hypothesis for the ranking/recommendation change (e.g., 'new algorithm increases conversion'). The primary metric should directly reflect this hypothesis, such as 'add-to-cart rate' or 'GMV per user'. Guardrail metrics are crucial to ensure no negative side effects, like 'bounce rate' or 'seller NPS'. The randomization unit should be carefully chosen, typically 'user ID' to maintain consistency. Finally, a robust launch decision rule based on statistical significance and practical impact on primary and guardrail metrics is essential.

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 for Big Billion Days (BBD) should primarily happen at the customer level to ensure independent observations and avoid contamination, especially for features impacting user behavior over time. However, session or device level might be considered for very short-term, isolated UI/UX changes where customer-level randomization is too slow or complex. Seller or city-tier randomization is generally unsuitable for BBD-specific A/B tests due to high variance, potential for network effects, and difficulty in controlling external factors, making it hard to attribute changes accurately. The key trade-off is between minimizing contamination and achieving statistical power versus operational complexity and potential for indirect 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: The primary metric should directly reflect the experiment's goal: 'Cart-to-Order Conversion Rate' (number of orders / number of carts initiated). Guardrail metrics are crucial to prevent unintended negative consequences. Key guardrails would include 'Average Order Value (AOV)', 'Number of Orders', 'Gross Merchandise Value (GMV)', and 'User Retention Rate' (e.g., 7-day or 30-day retention). Additionally, 'Customer Support Contact Rate' related to orders or cart issues would be a vital guardrail to catch user frustration.

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: A strong candidate would first acknowledge that a 52/48 split is a significant deviation from 50/50 and requires investigation. They would then outline a diagnostic process starting with checking the random assignment mechanism (e.g., hash function, user ID consistency). Next, they would verify data logging and ETL processes for any potential data loss or corruption specific to one group. Finally, they would analyze pre-experiment metrics and user characteristics for both groups to detect any inherent biases before the experiment even began.

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: A strong candidate would first explain that stopping an A/B test early due to 'peeking' at positive results is a significant statistical error, increasing the false positive rate. They would then detail the importance of pre-determining sample size and test duration based on statistical power and minimum detectable effect (MDE). The candidate should recommend continuing the test until the pre-defined duration or sample size is reached, or using sequential testing methodologies if early stopping is truly desired and properly accounted for in the experimental design. Finally, they would emphasize the risk of launching a false positive and the long-term negative impact on business metrics.

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 initial user engagement is high due to the newness of the feature, but then normalizes as users adapt. Another explanation is a 'power user' effect, where early adopters (often more engaged) drive initial lift, but the feature's utility doesn't extend as broadly to the general user base. External factors like seasonality or concurrent promotions could also confound results. To design the test duration, analyze historical data for similar feature adoption curves, consider the typical sales cycle for sellers, and run the test long enough to observe at least one full cycle of seller behavior and account for potential novelty effects (e.g., 6-8 weeks, or even longer if seasonality is a major factor).

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 influence control users (e.g., buyers interacting with those sellers). This interference can lead to an underestimation or overestimation of the true treatment effect. Specifically, positive network effects might make the control group look better than it is, while negative network effects could make the treatment group look worse. This bias invalidates standard A/B test assumptions of independent user behavior and makes it difficult to accurately attribute changes to the feature.

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: A strong candidate would first acknowledge the low-frequency nature and high variability of cart-to-order conversion during BBD. They would propose using a proxy metric that is a leading indicator of conversion and has a higher frequency, such as 'add-to-cart rate' or 'proceed-to-checkout click-through rate'. To ensure power, they would suggest increasing the sample size by broadening the experiment's scope (e.g., all users, not just a segment) or running it for a slightly longer duration if possible, while carefully considering the trade-offs. Finally, they would discuss pre-calculating the required sample size and minimum detectable effect (MDE) based on the chosen proxy metric's baseline and desired confidence levels.

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 geo/city tier-level experiment for Flipkart Plus would involve randomizing entire cities or city tiers (e.g., Tier 1 vs. Tier 2/3) into control and treatment groups. This is preferable to user-level randomization when the treatment has network effects, requires local operational changes (e.g., delivery infrastructure), or risks user-to-user contamination within a geographical area. Key analytical downsides include lower statistical power due to fewer experimental units, increased sensitivity to selection bias if randomization isn't perfectly balanced across geos, and challenges in isolating the treatment effect from confounding local variables.

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) in this scenario, I would first define clear segments (new vs. existing users, specific vs. other categories) and then perform subgroup analysis to quantify the treatment effect within each. Statistical significance for each subgroup's lift should be assessed, potentially using interaction terms in a regression model to formally test for HTE. Further investigation into the 'why' behind the HTE would involve qualitative analysis, user journey mapping, and hypothesis generation around user behavior or product differences in the specific category. Finally, I would recommend a targeted rollout or further experimentation based on these findings, rather than a full launch.

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 requires quantifying the trade-off. First, calculate the monetary value of the cart-to-order conversion improvement (e.g., increased GMV, profit) and the cost of the worsened promise breach rate (e.g., refunds, customer service costs, churn impact). Second, analyze the customer segment most affected by each metric and assess the long-term impact on customer lifetime value. Finally, based on the net financial impact and strategic priorities (e.g., growth vs. customer experience), recommend a launch, no-launch, or phased/segmented launch, potentially with mitigation strategies for the promise breach.

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 would start with a small percentage (e.g., 1-5%) of sellers, monitoring key health metrics like error rates, page load times, and API call successes to ensure stability before gradually increasing traffic. Holdback involves reserving a small, representative control group (e.g., 1-2%) of sellers who never see the new feature, even after full launch, to measure long-term incremental impact and guard against novelty effects or seasonal biases. Post-launch monitoring requires ongoing tracking of primary business metrics (e.g., GMV per seller, seller retention, listing creation rate) and secondary health metrics, establishing clear alert thresholds and rollback plans for any negative deviations.

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's impact on data collection. Then, analyze the pre- and post-change data for key metrics, especially Flipkart Plus related ones, in both control and treatment groups to detect any sudden shifts or discrepancies. Evaluate if the change introduced systematic bias or increased variance that could invalidate the comparison between groups. Finally, based on the analysis, decide if the core experiment metrics remain unaffected and reliable, or if the experiment needs to be restarted or adjusted.

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: To detect interaction effects between two overlapping A/B tests affecting GMV after returns during Big Billion Days, one would first ensure proper orthogonal assignment or use a factorial design if possible. Analyze the individual experiment results for each treatment group and then look for significant deviations in the combined treatment group (e.g., A1B1 vs. A0B0, A1B0, A0B1) that cannot be explained by the sum of individual effects. Statistical methods like ANOVA with interaction terms or regression analysis can quantify these interactions. Management involves prioritizing which experiment to pause or adjust, or designing a follow-up experiment to isolate and understand the interaction.

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 business case would start by clarifying the problem (exact dates, product lines affected, previous trends). Then, it would structure the diagnosis into internal factors (platform changes, marketing campaigns, operational issues like seller onboarding/fulfillment) and external factors (competitor actions, economic shifts, seasonality, regulatory changes). The analysis would prioritize data sources (sales reports, traffic logs, seller performance metrics, customer feedback) and propose a structured investigation plan, starting with high-impact, easily verifiable hypotheses.

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

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

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

Other roles at Flipkart

Business Analyst interviews at other companies