Topic
Analytics & Experimentation interview questions
560 Analytics & Experimentation questions from 84 companies, with hints, runnable code and solution walkthroughs.
74 easy288 medium198 hard
Analytics & Experimentation interview questions by the numbers
Last updated
Katkat has 560 Analytics & Experimentation interview questions from 84 companies; the most come from Meta (21%), Capital One (11%) and DoorDash (9%). By difficulty: 13% easy, 51% medium and 35% hard. The most common round is Technical Screen (55%). Frequent concepts include Causal Inference, A/B Testing, Experimentation and Metrics.
Companies (84)
Difficulty
- Easy13% · 74
- Medium51% · 288
- Hard35% · 198
Interview rounds
- Technical Screen55% · 306
- Onsite39% · 218
- Online Assessment3% · 16
- HR Screen3% · 14
- Other1% · 6
Roles
- Data Scientist92% · 513
- Software Engineer2% · 13
- Data Analyst2% · 10
- Product Analyst1% · 7
- Data Engineer1% · 5
Frequent concepts
- Causal Inference13% · 73
- A/B Testing12% · 65
- Experimentation8% · 42
- Metrics7% · 41
- Product Analytics5% · 30
- Experiment Design3% · 18
Most mentioned in interview experiences
- 1.Analyze ad watch-time with Excel pivots2 reports
- 2.Define Ultra success and detect suspicious transactions2 reports
- 3.Define Ultra success metrics and detect suspicious transactions2 reports
- 4.Design a flu-shot A/B/n campaign experiment2 reports
- 5.Design an experiment to evaluate a new ads algorithm2 reports
- 6.Diagnose a dip in approval/conversion rate2 reports
- 7.Estimate impact without experiments and pick variant2 reports
- 8.Evaluate Factors Before Renewing TV-Series Contracts2 reports
- 9.How would you investigate a metric decline?2 reports
- 10.Investigate marketplace metrics and experiment rollout2 reports
Counted from 120 candidate interview experiences on Katkat. How we collect and count
Showing 151–180 of 560 results
This problem tests the ability to diagnose a service quality issue, define key performance indicators, and design an experiment to evaluate an operational intervention while controlling for confounding variables.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenDesign an automated, data-driven compensation policy for late deliveries on a three-sided marketplace. Formulate delay thresholds, balance customer lifetime value against operational costs, and structure an A/B test with appropriate randomization and guardrail metrics.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question evaluates proficiency in experimental design, causal inference, randomization and contamination control, regression modeling with fixed effects and clustered standard errors, power calculation, and handling of compliance and robustness issues.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis problem tests the ability to design a cluster-randomized experiment in a marketplace setting, focusing on managing network effects (spillover) and defining appropriate inference strategies for geo-based batches.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question evaluates experiment design, causal inference, product-analytics, and metric-definition skills for multi-sided marketplaces, focusing on handling interference, spillovers, heterogeneity, and trade-offs between conversion, retention, credit burn, and monetization.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question tests your ability to design robust A/B tests for marketplace products, focusing on metric selection, identifying interference, and accounting for ecosystem-level trade-offs.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Determine Success Metrics for Biker Dasher Program Launch states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenDoorDash analytics prompt on diagnosing cold food deliveries, covering complaint metrics, lifecycle timestamps, batching, packaging, weather, segmentation, data quality, A/B testing, and operational guardrails.
DoorDashData ScientistAnalytics & ExperimentationOnsiteWork through a product analytics case about diagnosing a delivery-quality problem and deciding whether an intervention should launch. The question tests metric hierarchy, causal reasoning, investigation design, power considerations, and decision criteria.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates a data scientist's skills in marketplace analytics, causal reasoning, metric framework design, and experimentation for diagnosing a decline in successful orders.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates a data scientist's competency in funnel-based diagnostics, causal inference, and experimental design for distinguishing supply-side versus demand-side drivers in a two-sided marketplace, emphasizing metric selection, segmentation, and guardrail monitoring.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenInvestigate an increase in cold food complaints by decomposing fulfillment timestamps, evaluating mix shifts versus operational degradation, and designing a mitigation experiment with balanced marketplace guardrails.
DoorDashData ScientistAnalytics & ExperimentationOnsiteEvaluate a sudden drop in Dasher order acceptance rate by verifying data integrity, decomposing segment-level shifts, and designing an experiment to mitigate downstream marketplace impacts.
DoorDashData ScientistAnalytics & ExperimentationOnsiteTests the candidate's structured metric troubleshooting, funnel decomposition, and root cause analysis for an acute drop in core marketplace volume. Evaluates the ability to separate count effects from conversion rate changes and isolate partner-specific vs. market-wide anomalies.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates a data scientist's competencies in causal inference, metrics engineering, data instrumentation and joining, root‑cause analysis, and experiment design focused on operational delivery performance.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis problem tests the ability to diagnose root causes of operational cost drivers and design a rigorous experiment to validate potential mitigation policies.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates a data scientist's skills in product analytics, metric design, diagnostics, causal inference, and experimental design for diagnosing cold-food complaint spikes using logs, GPS, weather and complaint labels.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question evaluates a data scientist's competency in product analytics, causal inference, funnel and metric decomposition, segmentation, and experimentation for marketplace platforms, focusing on diagnosing sustained drops in completed orders.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Evaluate Account-Partner Onboarding with Success Metrics states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question evaluates experimentation and product analytics skills—metric design, causal inference, and marketplace impact assessment—in the context of a two-sided delivery marketplace, with attention to eligibility, routing, and matching effects.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question tests your ability to design an A/B test for a marketplace feature while accounting for network effects, trade-offs between supply-side control and demand-side fulfillment, and selecting appropriate metrics.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Evaluate Dasher Initiatives with A/B Testing and Metrics states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Evaluate Impact of $1 Fee on Fast-Food Profitability states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationOnsiteEvaluate Top-Dasher Program's Benefits and Challenges evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationOnsiteTests marketplace experimentation design, tackling spatial-temporal spillover effects, metric selection, and decision criteria for a multimodal courier fleet.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis problem tests the ability to design an A/B test for a logistics marketplace, focusing on metric definition, experiment randomization strategy, and identifying potential confounding variables.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis question evaluates expertise in experimentation design and causal inference within two-sided marketplace environments. It tests the ability to handle interference, SUTVA violations, metric selection, and rollout safety when deploying ranking model upgrades — core competencies for data scientist roles focused on product analytics and A/B testing.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis question evaluates a data scientist's skills in experimental design, causal inference, metric definition and aggregation, power/MDE calculation, and cross‑channel attribution for order‑related messaging campaigns.
DoorDashData ScientistAnalytics & ExperimentationOnsiteThis problem tests the ability to design an A/B test, define success metrics, and account for confounding variables when introducing a new logistics channel (bike delivery) to a marketplace.
DoorDashData ScientistAnalytics & ExperimentationTechnical ScreenThis interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Identify Key Drivers of Delivery Decline in Los Angeles states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
DoorDashData ScientistAnalytics & ExperimentationTechnical Screen