Analytics & Experimentation Interview Questions

Showing 91–120 of 306 results

• DoorDashHard·Data Scientist
  Diagnose LA completed-order drop and design experiment

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

  Analytics & ExperimentationTechnical Screen
• DoorDashMedium·Data Scientist
  Diagnose a One-Day Drop in Successful Deliveries

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

  Analytics & ExperimentationTechnical Screenmetric-troubleshootingfunnel-analysismarketplace-analytics
• DoorDashHard·Data Scientist
  Diagnose and experiment to reduce late deliveries

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

  Analytics & ExperimentationTechnical Screen
• DoorDashHard·Data Scientist
  Diagnose and reduce cold-food refund costs

  This problem tests the ability to diagnose root causes of operational cost drivers and design a rigorous experiment to validate potential mitigation policies.

  Analytics & ExperimentationTechnical ScreenCausal InferenceExperimentationMarketplace Analytics
• DoorDashMedium·Data Scientist
  Evaluate a Bike Dasher Program with a Controlled Experiment

  Tests marketplace experimentation design, tackling spatial-temporal spillover effects, metric selection, and decision criteria for a multimodal courier fleet.

  Analytics & ExperimentationTechnical ScreenA/B TestingMarketplace ExperimentationCausal Inference
• DoorDashMedium·Data Scientist
  Evaluate a Bike-Delivery Pilot with Marketplace Metrics

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

  Analytics & ExperimentationTechnical ScreenA/B TestingMarketplaceLogistics
• DoorDashEasy·Data Scientist
  How would you test a bike delivery option?

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

  Analytics & ExperimentationTechnical ScreenA/B TestingMetricsMarketplace Analytics
• DoorDashHard·Data Scientist
  Identify Key Drivers of Delivery Decline in Los Angeles

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

  Analytics & ExperimentationTechnical Screen
• DoorDashMedium·Data Scientist
  Investigate Causes of Cold Food Deliveries and Solutions

  This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Investigate Causes of Cold Food Deliveries and Solutions states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  Analytics & ExperimentationTechnical Screen
• DoorDashMedium·Data Scientist
  Investigate Causes of Cold Meal Deliveries

  DoorDash data scientist case on cold meal deliveries, covering lifecycle timestamps, complaint metrics, segmentation, root-cause analysis, dispatch and packaging fixes, A/B testing, and marketplace guardrails.

  Analytics & ExperimentationTechnical Screen
• DoorDashMedium·Data Scientist
  Investigate Causes of Increased Driver Wait Time

  This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Investigate Causes of Increased Driver Wait Time states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

  Analytics & ExperimentationTechnical Screen
• DoorDashHard·Data Scientist
  Investigate Declining Successful Orders

  This question tests your ability to decompose a high-level drop in a key business metric into granular segments and formulate testable hypotheses to explain the underlying root causes.

  Analytics & ExperimentationTechnical ScreenProduct AnalyticsFunnel AnalysisHypothesis Testing
• DoorDashHard·Data Scientist
  Investigate Falling Successful Orders

  This question evaluates a data scientist's ability to diagnose a drop in a product metric through anomaly verification, data validity checks, funnel and cohort analysis, causal attribution across marketplace sides (customer, restaurant, delivery), and experiment design.

  Analytics & ExperimentationTechnical Screen
• DoorDashHard·Data Scientist
  Investigate Falling Successful Orders in LA

  This problem tests your ability to decompose a drop in a high-level business metric into granular segments, formulate testable hypotheses, and propose methodologies to identify the root cause.

  Analytics & ExperimentationTechnical ScreenRoot Cause AnalysisFunnel AnalyticsMarketplace Dynamics
• DoorDashMedium·Data Scientist
  Investigate LA Order Drop

  This question evaluates marketplace analytics, causal inference, hypothesis-driven investigation, funnel decomposition, and experimentation design skills in a data science context.

  Analytics & ExperimentationTechnical Screen
• DoorDashEasy·Product Analyst
  Investigate LA successful orders drop

  This question tests your ability to methodically decompose a performance metric drop, isolate potential root causes using data dimensions, and suggest analytical steps to distinguish between technical issues and marketplace dynamics.

  Analytics & ExperimentationTechnical ScreenProduct AnalyticsFunnel AnalysisRoot Cause Analysis
• DoorDashEasy·Data Scientist
  Reduce Cold-Food Incidents with Metrics and an Insulated-Bag Experiment

  Design an A/B test and metric framework to evaluate whether equipping couriers with insulated bags reduces cold-food complaints while guarding marketplace efficiency.

  Analytics & ExperimentationTechnical ScreenExperimentationA/B TestingMetrics Design
• DoorDashMedium·Data Scientist
  Should DoorDash add bicycle dashers?

  This problem tests the ability to design an A/B test for a marketplace intervention, identify success metrics, and account for potential cannibalization and external factors in urban delivery.

  Analytics & ExperimentationTechnical ScreenA/B TestingMarketplace AnalyticsCausal Inference
• DropboxMedium·Data Scientist
  Run org-safe online experiment for recommender

  This question evaluates a data scientist's competency in online experimentation design, causal inference, clustered randomization, metric definition (primary, secondary, guardrails), sample size/MDE computation, variance reduction and sequential monitoring, instrumentation and privacy-aware logging.

  Analytics & ExperimentationTechnical Screen
• Fetch RewardsMedium·Data Scientist
  Design analysis to validate reported decline

  This question evaluates analytical and experimental-design competencies including metric specification, time-series and same-store comparisons, bias and confounder detection, and concise data-driven communication under a tight time constraint.

  Analytics & ExperimentationTechnical Screen
• Fetch RewardsMedium·Data Scientist
  Evaluate Overlapping Shelf Ranking Experiments

  This question evaluates competency in experimental design and causal inference for A/B testing, focusing on handling overlapping traffic, interaction effects between concurrent experiments, metric selection, guardrails, and statistical validity.

  Analytics & ExperimentationTechnical Screen
• FigmaHard·Data Scientist
  How would you measure product success?

  This question tests the ability to define a comprehensive measurement framework for a B2B SaaS collaborative tool, balancing growth, engagement, and retention metrics.

  Analytics & ExperimentationTechnical ScreenProduct AnalyticsMetrics DesignSaaS
• FFigureaiMedium·Data Engineer
  Choose a Metric Hierarchy for a Humanoid-Robot Fleet

  This problem tests the ability to structure a multi-layered metrics dashboard for complex hardware-software systems, balancing operational efficiency against safety and system stability.

  Analytics & ExperimentationTechnical ScreenMetricsData ModelingRobotics
• FFigureaiMedium·Data Engineer
  Diagnose the Leading Cause of Slow or Failed Charging

  This problem tests your ability to define metrics from imperfect telemetry, perform root cause analysis on hardware failure, and design a strategy to identify performance bottlenecks in an autonomous charging system.

  Analytics & ExperimentationTechnical ScreenData EngineeringRoot Cause AnalysisTelemetry
• GoogleHard·Data Scientist
  Boost Google Workspace Chat Usage with Strategic A/B Testing

  Boost Google Workspace Chat Usage with Strategic A/B Testing 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.

  Analytics & ExperimentationTechnical Screen
• GoogleHard·Data Scientist
  Compare two stores’ profits rigorously

  This question evaluates a data scientist's skills in experimental design, causal inference (including difference-in-differences), measurement and metric construction for profitability, uncertainty quantification (confidence intervals and power checks), and operational guardrails for real-world data collection.

  Analytics & ExperimentationTechnical Screen
• GoogleHard·Data Scientist
  Define and apply Gmail user segments

  A Google data scientist analytics screen: propose actionable Gmail user segments from behavioral metadata, validate their stability and separability over eight weeks, design targeted interventions with metrics and guardrails, and run a privacy-aware experiment to measure per-segment lift. Covers segmentation axes, validation metrics, k-anonymity and differential privacy, CUPED, and RICE roadmap prioritization.

  Analytics & ExperimentationTechnical Screen
• GoogleMedium·Data Scientist
  Design A/B Test to Isolate Product Usage Drop Causes

  Evaluates experimentation strategy for diagnosing a simultaneous product usage drop in the U.S. and Mexico. Strong answers identify confounders, design tests or quasi-experiments, control variables, and report causal lift.

  Analytics & ExperimentationTechnical Screen
• GoogleHard·Software Engineer
  Design A/B testing platform

  This question evaluates a candidate's competency in designing scalable, privacy-compliant A/B testing platforms, covering deterministic bucketing, traffic allocation, telemetry and event pipelines, experiment governance, and applied statistical methods in the Analytics & Experimentation domain.

  Analytics & ExperimentationTechnical Screen
• GoogleHard·Data Scientist
  Design an Unbiased Upgrade Experiment

  This question tests the ability to design an A/B test for a software upgrade, specifically focusing on handling non-compliance, selection bias, and the identification of causal effects in a real-world product environment.

  Analytics & ExperimentationTechnical ScreenCausal InferenceExperiment DesignA/B Testing