Amazon Analytics Engineer Interview Questions (2026)

1. 1Online Assessment (SDE OA)60 minMedium

   Two timed coding problems plus a workplace-simulation and logic section; the main gate for freshers and India volume hiring.

2. 2Phone screen45 minMedium

   One coding problem plus 1-2 Leadership Principle STAR questions with an SDE.

3. 3Coding loop round60 minMedium

   DSA problem to working code, followed by assigned-LP behavioral questions in STAR format.

4. 4System design loop round60 minHard

   Design an Amazon-scale service with capacity math, plus LPs; low-level/OOD design substitutes for junior candidates.

5. 5Hiring Manager round45 minMedium

   Team fit, project deep dives, and Deliver Results/Bias for Action stories with the manager you would report to.

6. 6Bar Raiser60 minHard

   An interviewer from outside the team stress-tests LP stories and overall bar with the hardest cross-examination of the loop; holds veto.

1. Q1

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

   MediumStatistics & Experimentation RoundA/B TestingAmazon-specific

   Context: Context: Amazon wants to grow retail conversion while keeping delivery promises and inventory healthy.

   How to answer: A strong answer will define a clear, testable hypothesis, such as 'The new ranking algorithm will increase customer purchases.' The primary metric should directly reflect the hypothesis, like 'Add-to-Cart Rate' or 'Conversion Rate per User.' Guardrail metrics are crucial to ensure no negative impact on other key areas (e.g., 'Page Load Time,' 'Revenue per User,' 'Return Rate'). The randomization unit should be carefully chosen, typically 'User ID' or 'Session ID,' to avoid contamination. Finally, a clear launch decision rule, incorporating statistical significance (e.g., p < 0.05) and practical significance over a defined test duration, should be articulated.

2. Q2

   For Prime, should randomization happen at customer, session, device, seller, or region level? Explain the tradeoffs

   MediumStatistics & Experimentation RoundA/B TestingAmazon-specific

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

   How to answer: Randomization for Prime should primarily happen at the customer level. This ensures a consistent experience for an individual user across sessions and devices, preventing contamination and ensuring independent observations. Session or device level randomization could lead to a single customer being in both control and treatment groups, invalidating results. Seller or region level randomization might be appropriate for specific experiments targeting those entities, but not for core Prime features affecting the customer experience directly.

3. Q3

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

   MediumStatistics & Experimentation RoundA/B TestingAmazon-specific

   Context: Assume assignment logs, exposure logs, and eligibility filters may disagree.

   How to answer: A strong candidate would first define Sample Ratio Mismatch (SRM) and its implications for experiment validity. They would then outline a diagnostic process starting with a chi-squared test on the observed counts to quantify the deviation from the expected 50/50 split. Further investigation would involve checking the bucketing logic for bugs, examining pre-experiment metrics for existing differences, and analyzing the SRM across different dimensions like device type, region, or user segment to pinpoint the source of the imbalance.

4. Q4

   purchase conversion rate is a low-frequency event for Prime. How would you set up an experiment with enough power without waiting too long?

   MediumStatistics & Experimentation RoundA/B TestingAmazon-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 Prime purchase conversion, focus on choosing a more sensitive, higher-frequency proxy metric that correlates strongly with the ultimate business goal. This could involve metrics like 'add to cart' rate, 'proceed to checkout' rate, or even engagement metrics like 'product page views per session' if a direct conversion proxy is too low. Additionally, consider increasing the sample size by expanding the experiment's reach or duration, or employing techniques like CUPED to reduce variance and boost statistical power. Finally, clearly define the minimum detectable effect (MDE) and ensure the chosen proxy metric allows for detecting a meaningful change within a reasonable timeframe.

5. Q5

   The Sponsored Products experiment lifts purchase conversion rate overall, but only for new users and only in one category. How would you evaluate heterogeneous treatment effects?

   HardStatistics & Experimentation RoundA/B TestingAmazon-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 define relevant subgroups based on user tenure (new vs. existing) and product category. Then, I would perform a stratified analysis, calculating the lift in purchase conversion rate and its statistical significance for each subgroup. I'd use interaction terms in a regression model (e.g., OLS or logistic regression) with user tenure and category as covariates to formally test for HTE. Finally, I would consider power implications for smaller subgroups and potential multiple comparisons issues, adjusting p-values if necessary.

6. Q6

   Treatment improves purchase conversion rate but worsens on-time delivery rate for Alexa Shopping. Walk through a launch recommendation

   HardStatistics & Experimentation RoundA/B TestingAmazon-specific

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

   How to answer: A strong recommendation balances the trade-offs between increased revenue (purchase conversion) and potential customer dissatisfaction/churn (on-time delivery). The candidate should propose a phased rollout, starting with a small segment and closely monitoring both primary and secondary metrics. Key considerations include quantifying the monetary impact of both metrics, identifying potential causal links between the treatment and delivery issues, and exploring mitigation strategies for the negative impact before a full launch. The recommendation should be data-driven, risk-aware, and customer-centric, potentially involving further experimentation.

7. Q7

   Amazon's Retail 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 CasesAmazon-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 confirming the data's accuracy and scope (e.g., specific marketplace, region, product category). They would then segment the revenue drop by key dimensions like product category, seller type (FBA vs. FBM), customer segment, and traffic source to pinpoint the affected areas. Next, they would investigate potential causes across three main pillars: internal system issues (e.g., payment processing, site errors), external market factors (e.g., competitor actions, economic shifts), and operational changes (e.g., pricing algorithms, shipping policy changes). Finally, they would propose specific data points and dashboards to monitor for each hypothesis and outline a prioritization strategy.

8. Q8

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

   HardProduct Analytics & Business CaseBusiness CasesAmazon-specific

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

   How to answer: A strong candidate would first identify key business objectives, such as maximizing profit, customer satisfaction, or long-term market share. They would then propose a data-driven framework for prioritization, likely involving a weighted scoring model incorporating factors like customer lifetime value, product profitability, strategic importance of categories/regions, and potential for customer churn. Finally, they would discuss the need for A/B testing or simulation to validate the prioritization strategy and establish clear KPIs to monitor its effectiveness and iterate.

9. Q9

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

   HardProduct Analytics & Business CaseBusiness CasesAmazon-specific

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

   How to answer: A strong answer will structure the business review into three clear sections: 'What Happened' (key FBA metrics like revenue, units, seller growth, and perhaps a specific recent trend or event), 'Why It Happened' (root causes for observed trends, e.g., supply chain disruptions, new seller incentives, competitive pressures, or operational efficiencies), and 'What's Next' (actionable, data-driven recommendations for the FBA team, such as optimizing fulfillment centers, refining pricing, or enhancing seller tools). The candidate should use specific, hypothetical Amazon FBA examples and metrics to demonstrate depth.

10. Q10

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

    EasyDashboarding, Stakeholder & Hiring Manager RoundDashboardingAmazon-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 overall on-time delivery rate, broken down by region, carrier, and product category, with real-time refresh. They would define clear thresholds: green (>98%), yellow (95-98%), red (<95%), triggering alerts for yellow and red. Alerts would be routed via PagerDuty or Slack to specific operations teams responsible for the affected region/carrier. Ownership would be clearly defined by geographical region and carrier partnership, with a central team overseeing global trends and cross-functional issues.

11. Q11

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

    MediumDashboarding, Stakeholder & Hiring Manager RoundDashboardingAmazon-specific

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

    How to answer: A strong candidate would outline a systematic approach starting with clarifying the specific discrepancies (which numbers, which reports, what's the magnitude). The next step involves a data lineage review, tracing the dashboard's data sources back to their origin and comparing transformations against finance/operations data pipelines. Key areas to audit include data extraction logic (filters, joins), aggregation methods (SUM, AVG, COUNTD), time zone handling, and data refresh schedules. Finally, they would validate the dashboard's underlying SQL queries or ETL processes against the business logic defined by finance/operations, ensuring consistent definitions for key metrics like 'Prime Member' or 'Revenue'.

12. Q12

    Create a dashboard narrative for Finance partner explaining why purchase conversion rate changed for Buy Box. What charts would you show first?

    HardDashboarding, Stakeholder & Hiring Manager RoundDashboardingAmazon-specific

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

    How to answer: The dashboard narrative should start with a clear summary of the conversion rate change (e.g., 'Conversion rate dropped by X% last week'). Then, it should break down the conversion funnel into key stages (e.g., product view, add-to-cart, checkout initiation, purchase) to identify where the biggest drop occurred. Subsequent charts would then deep-dive into potential drivers for that specific stage, such as traffic source changes, pricing fluctuations, inventory issues, or website performance metrics (latency, errors). The narrative should conclude with actionable insights and recommended next steps.

13. Q13

    Prime's conversion from product_view to purchase dropped 15% week over week. Walk through your diagnosis plan

    EasyProduct Analytics & Business CaseProduct AnalyticsAmazon-specific

    Context: Assume no single obvious outage has been announced.

    How to answer: A strong candidate would first clarify the exact metrics and scope (e.g., Prime members, specific products, A/B tests running). Then, they would segment the data by key dimensions like device type, product category, traffic source, and geographic region to pinpoint where the drop is most severe. They would also investigate recent changes (code deployments, marketing campaigns, pricing adjustments) and check for data pipeline issues. Finally, they would form hypotheses based on these findings and propose specific deep-dive analyses.

14. Q14

    A new Sponsored Products feature has 30% adoption but no movement in purchase conversion rate. What analyses would you run before calling it unsuccessful?

    EasyProduct Analytics & Business CaseProduct AnalyticsAmazon-specific

    Context: Consider exposure, eligibility, frequency, quality of adoption, and segment fit.

    How to answer: First, analyze the user journey for the 30% who adopted the feature, comparing their behavior to a control group who did not. Look for changes in upstream metrics like product page views, add-to-cart rates, or time spent on product pages. Segment the analysis by product category, price point, or customer tenure to identify specific use cases or user groups where the feature might be performing differently. Finally, consider the feature's intended goal beyond immediate purchase conversion, such as discovery, consideration, or repeat purchases, and analyze metrics aligned with those goals.

15. Q15

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

    MediumProduct Analytics & Business CaseProduct AnalyticsAmazon-specific

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

    How to answer: To segment Alexa Shopping customers for growth, I would start with behavioral segments like 'New Shoppers' (first 30 days), 'Frequent Shoppers' (3+ orders/month), 'Lapsed Shoppers' (no orders in 90+ days), and 'Category Explorers' (shopping in 3+ categories). Key metrics for these segments would include conversion rate, average order value (AOV), purchase frequency, and category penetration. Potential actions include personalized onboarding for new users, subscription incentives for frequent users, re-engagement campaigns for lapsed users, and cross-category recommendations for explorers to drive growth.

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

Prepare 8-12 STAR stories mapped to Leadership Principles; expect a Bar Raiser; quantify impact

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

Other roles at Amazon

Analytics Engineer interviews at other companies