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

   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.

2. Q2

   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.

3. Q3

   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).

4. Q4

   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.

5. Q5

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

   MediumProduct Analytics & Business CaseBusiness CasesFlipkart-specific

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

   How to answer: A strong candidate would outline a framework for estimating business impact, starting with identifying the specific metric to optimize (e.g., GMV, profit, customer acquisition). They would then propose modeling the direct impact on revenue/cost components for each change (e.g., price elasticity for pricing, take rate for commission). Key assumptions would include market size, competitor actions, customer price sensitivity, and operational capacity. Sensitivities would explore how changes in these assumptions (e.g., varying price elasticity, different competitor responses) alter the estimated impact, providing a range of outcomes rather than a single point estimate.

6. Q6

   Fraud, abuse, or policy gaming is suspected in Flipkart Marketplace. Size the financial impact and propose an analytics approach to reduce it

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-specific

   Context: Balance loss prevention with false positives and user/partner experience.

   How to answer: A strong candidate would first define the scope of 'fraud, abuse, or policy gaming' in Flipkart Marketplace, identifying key areas like seller fraud (fake products, non-delivery), buyer abuse (returns fraud, promo abuse), or affiliate gaming. They would then propose a structured approach to sizing the financial impact, including identifying relevant metrics (e.g., chargebacks, lost revenue, operational costs), data sources (transaction logs, return data, customer service tickets), and estimation methodologies (e.g., sampling, extrapolation). For the analytics approach, they would suggest a multi-pronged strategy involving anomaly detection (e.g., using historical data, rule-based systems, machine learning models), network analysis to identify colluding entities, and predictive modeling to flag high-risk transactions or accounts. Finally, they would emphasize the importance of A/B testing proposed interventions and continuous monitoring to adapt to evolving fraud patterns.

7. Q7

   Big Billion Days is preparing for a high-traffic event or sale. What metrics and analyses would you use to prevent a business-critical failure?

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-specific

   Context: Think capacity, inventory, payments, support load, latency, and real-time alerting.

   How to answer: A strong candidate would outline a multi-faceted approach focusing on pre-event load testing, real-time monitoring, and post-event analysis. Key metrics would include server response times, error rates (5xx, 4xx), database connection pool utilization, API latency, and order processing success rates. They would detail analyses like capacity planning based on historical data, anomaly detection for sudden spikes, and A/B testing of infrastructure changes. The candidate should also mention rollback strategies and incident management protocols.

8. Q8

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

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-specific

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

   How to answer: A strong candidate would first identify the core objective: maximizing long-term customer value and profitability for Flipkart Plus. They would then propose a framework for prioritization, likely involving a multi-factor scoring model. Key factors would include customer lifetime value (CLTV), strategic importance of categories/regions, immediate profitability, and operational feasibility. Finally, they would suggest A/B testing and continuous monitoring to refine the prioritization strategy based on real-world impact.

9. Q9

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

   HardProduct Analytics & Business CaseBusiness CasesFlipkart-specific

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

   How to answer: A strong answer would first define ROI for a fashion loyalty program, focusing on incremental revenue (increased purchase frequency, AOV, new customer acquisition) versus program costs (discounts, marketing, tech). It would then detail a robust methodology to isolate program impact from selection bias, likely involving A/B testing (randomized control trials) or quasi-experimental methods like difference-in-differences or propensity score matching if A/B testing isn't feasible. Key metrics to track would include member vs. non-member LTV, churn rates, and category penetration, adjusted for baseline differences. Finally, it would discuss how to operationalize these insights for program optimization.

10. Q10

    You need to create a self-serve dashboard for Flipkart Plus that PMs and business teams will use weekly. How do you define metrics and prevent misuse?

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-specific

    Context: Include metric glossary, data freshness, filters, caveats, and examples.

    How to answer: A strong candidate would first identify key user segments (PMs, business teams) and their primary goals (growth, engagement, retention, monetization) for Flipkart Plus. They would then define a hierarchical set of metrics, starting with high-level KPIs (e.g., Plus Subscriber Growth, Plus Order Frequency, Plus AOV) and drilling down to supporting metrics (e.g., Plus Activation Rate, Feature Adoption Rate, Churn Rate by cohort). To prevent misuse, they would emphasize clear metric definitions, data sources, calculation logic, and refresh frequency within the dashboard. Finally, they would suggest implementing user training, contextual help, and potentially data governance policies or access controls.

11. Q11

    A Flipkart Marketplace dashboard is slow and users export raw data instead. How would you improve performance and adoption?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-specific

    Context: Discuss aggregated tables, filters, caching, chart pruning, and stakeholder training.

    How to answer: To improve performance, I would first analyze the dashboard's query logs and underlying data sources to identify bottlenecks (e.g., complex joins, unindexed columns, large data volumes). I'd then optimize the data layer through pre-aggregation, materialized views, or denormalization, and ensure efficient indexing. For the dashboard itself, I'd implement data sampling for initial loads, optimize visualization types, and consider caching mechanisms. To boost adoption, I would conduct user interviews to understand specific pain points, provide training and documentation, and implement a feedback loop for continuous improvement and feature prioritization.

12. Q12

    How would you audit a dashboard for Big Billion Days after stakeholders report that numbers do not match finance or operations reports?

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-specific

    Context: Trace metric definitions, source tables, filters, timezones, freshness, and access rules.

    How to answer: A strong candidate would outline a systematic debugging process starting with data source validation: checking if the dashboard pulls from the correct, most up-to-date tables and views. Next, they would verify data extraction and transformation logic, comparing dashboard SQL queries/ETL scripts against finance/operations report logic for discrepancies in filters, aggregations, or joins. They would then validate data freshness and refresh schedules, ensuring the dashboard data is not stale. Finally, they would perform a spot-check by manually replicating a few key metrics for a specific time period, comparing the dashboard's output directly with the finance/operations reports.

13. Q13

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

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingFlipkart-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 access control model, likely Role-Based Access Control (RBAC), mapping specific user roles (e.g., Category Manager, Marketing Analyst, Store Partner, Customer Service) to defined levels of data visibility and interaction. It should detail data masking/anonymization techniques for sensitive customer/partner PII, especially for broader access roles. Key considerations include row-level security (e.g., a Store Partner only sees their store's data), column-level security (e.g., Marketing sees aggregated sales but not individual customer names), and data aggregation strategies to protect privacy while enabling insights. The answer should also touch upon audit trails and data governance policies.

14. Q14

    Define a north-star metric for Flipkart's Flipkart Marketplace. What input metrics and guardrails would you track to ensure it is not gamed?

    EasyProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

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

    How to answer: A strong answer would define 'Number of Successful Orders' as the north-star metric for Flipkart Marketplace, as it directly reflects user engagement, seller activity, and revenue generation. Input metrics would include 'Daily Active Users (DAU)', 'Number of Active Sellers', 'Average Order Value (AOV)', 'Conversion Rate', and 'Number of Product Listings'. Guardrail metrics would focus on 'Return Rate', 'Customer Complaint Rate (CCR)', 'Seller Rating Degradation', and 'Delivery SLA Miss Rate' to prevent gaming and ensure a healthy marketplace ecosystem.

15. Q15

    How would you segment customers for Electronics Store to find growth opportunities? Name segments, metrics, and potential actions

    MediumProduct Analytics & Business CaseProduct AnalyticsFlipkart-specific

    Context: Use behavioral, value, lifecycle, and acquisition dimensions.

    How to answer: To segment customers for Flipkart's Electronics Store, I would primarily use a combination of purchase behavior (recency, frequency, monetary value - RFM), product categories purchased, and engagement level. Key segments would include 'New Customers', 'High-Value Loyalists', 'At-Risk/Churn', 'Category Explorers', and 'Browse-Only Users'. For each segment, I would track metrics like conversion rate, average order value (AOV), repurchase rate, and time spent browsing, then propose targeted actions such as personalized recommendations for explorers, win-back campaigns for at-risk users, and loyalty programs for high-value customers.

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