Katkat

Topic

Analytics & Experimentation interview questions

560 Analytics & Experimentation questions from 84 companies, with hints, runnable code and solution walkthroughs.

Questions560

74 easy288 medium198 hard

Your progress0/560

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

Showing 181–210 of 560 results

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

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

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

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashProduct AnalystAnalytics & ExperimentationTechnical Screen
  • 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 Pop-up Impact on Partner Referral Conversions states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    DoorDashData ScientistAnalytics & ExperimentationOnsite
  • 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 Measure Impact of Merchant Variety on Consumer Experience states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

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

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DoorDashData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    DropboxData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competency in KPI engineering, causal inference, experiment design, metric validation, and multi-touch attribution within the Analytics & Experimentation domain and is focused on profit-oriented search ranking.

    ExpediaData ScientistAnalytics & ExperimentationOnsite
  • 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.

    Fetch RewardsData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    Fetch RewardsData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to transform an abstract product objective into a rigorous measurement framework, focusing on metric selection and experimental design.

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

    FigmaData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    FigureaiData EngineerAnalytics & ExperimentationTechnical Screen
  • 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.

    FigureaiData EngineerAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competency in product analytics, metric definition, experiment design, and causal inference, including articulation of a north-star metric, supporting funnel and guardrail metrics, and handling confounding, seasonality, and heterogeneous effects.

    GleanData ScientistAnalytics & ExperimentationOnsite
  • A data scientist product case: define how to measure the success of a product, practiced on an enterprise search tool. Tests building a metric hierarchy with a north star, input metrics and guardrails, separating users from paying customers, defining a successful search and attributing changes causally.

    GleanData ScientistAnalytics & ExperimentationOnsite
  • This problem tests the ability to detect structural changes in time-series data and design a rigorous A/B testing strategy to measure the impact of an intervention on count-based metrics.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • 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.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • Choose and measure a malicious-webpage classifier metric using exposure-weighted recall, false-warning guardrails, and unbiased label audits.

    GoogleData AnalystAnalytics & ExperimentationOnsite
  • 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.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • 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.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • 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 Design A/B Test for Google Maps UI Change states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Evaluates experiment design for SaaS subscription pricing and a multivariate sign-up CTA test. Strong answers address pricing-test risks, LTV metrics, factorial design, interaction effects, and guardrails.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • 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.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen

More topics