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 211–240 of 560 results

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

    GoogleSoftware EngineerAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design a statistically sound A/B test for a search ranking algorithm, focusing on metric selection, hypothesis formulation, and common pitfalls in experimentation.

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

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • A Google Data Scientist onsite case on measuring the causal impact of reduced YouTube video-start latency on engagement. It spans A/B design (primary metric, diagnostics, error/buffering guardrails), randomization unit and interference, power/MDE for heavy-tailed watch time, variance reduction (CUPED, stratification), analysis of conflicting movements, ratio-metric decomposition with Simpson’s paradox, and propensity score matching when randomization isn’t possible.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Evaluates reliability analytics for Google Meet disconnections and enterprise renewal impact. Strong answers define call drops, use client and server logs to localize root causes, estimate account-level retention impact, and prioritize fixes using quantified business risk.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competency in precise metric and population definition, time‑to‑event and survival/hazard modeling, time‑series decomposition and change‑point analysis, instrumentation and traffic forensics, and experimental design for root‑cause identification.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates a data scientist's competency in product analytics and experimentation, covering precise metric definition and validation, instrumentation and event quality checks, rapid triage of adoption regressions, hypothesis generation, experiment design, and causal inference.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Design an end-to-end measurement and experimentation framework for a generative AI workflow-suggestion tool. Tests metric taxonomy, funnel analytics, instrumentation pitfalls, and causal inference under interference.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • Evaluates metrics and experimentation for an auto-reply suggestion feature in chat. Strong answers define adoption, latency, conversation quality, retention, and safety guardrails, design a causal experiment, and diagnose inconclusive results through funnel, segment, quality, and UI analyses.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • Evaluates A/B test design for Google Maps jogging route recommendations. Strong answers define jogging intent and exposure, measure completed runs and satisfaction, include safety and privacy guardrails, and specify randomization, MDE, power, logging, and rollout criteria.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates competency in experimental design, metric selection and definition, statistical power/MDE calculation, contamination prevention, and operational monitoring for route recommendation features, targeted at Analytics & Experimentation for a Data Scientist role.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • Evaluates proficiency with propensity score matching and broader causal inference concepts for observational treatment effect estimation, including identification assumptions, propensity score estimation and covariate selection, matching algorithms and common support, balance diagnostics, choice of estimand (ATE vs ATT) and uncertainty quantification, plus sensitivity checks and alternative methods. Common in Analytics & Experimentation interviews for Data Scientist roles because it probes understanding of confounding and identification in nonrandomized settings and requires intermediate-to-advanced applied statistics reasoning about methodological trade-offs.

    GoogleData ScientistAnalytics & ExperimentationOnsite
  • Diagnose falling malicious-webpage warnings by decomposing traffic, scoring, flags, rendering, and labels to separate improvement from failure.

    GoogleData AnalystAnalytics & ExperimentationOnsite
  • Use a structured sales-drop investigation covering metric definitions, data quality, funnel decomposition, segmentation, and causal evidence.

    GoogleData AnalystAnalytics & ExperimentationOnsite
  • This question evaluates instrumentation design, telemetry analysis, causal impact estimation, failure deduplication, and decision-making under uncertainty for a Data Scientist, testing competencies in analytics, experimentation, and product-metric prioritization.

    GoogleData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates expertise in analytics and experimentation, focusing on formulating project assumptions, selecting validation methods, and managing end-to-end data workflows and model evaluation.

    Graham CapitalSoftware EngineerAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to design an A/B test for a two-sided marketplace, focusing on network effects, cannibalization of metrics, and the selection of hold-out groups to measure long-term user behavior.

    GrindrData ScientistAnalytics & ExperimentationOnsite
  • A two-part Grindr Data Scientist technical screen on analytics and experimentation. Part 1 designs an advertiser-level causal study for a new ad-optimization product when the eligible advertiser pool is too small, covering MDE/power, CUPED, matched-pair and panel designs, interference, and heterogeneous effects. Part 2 evaluates lowering a free-user paywall from 100 to 80 profiles, balancing short-term conversion against long-term LTV, retention, ad revenue, and one-sided-triggering selection bias.

    GrindrData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a candidate's competence in statistical hypothesis testing and experiment analysis, focusing on A/B/n comparison of conversion rates, p-value computation, confidence interval estimation for lift, multiple-testing considerations, and interpretation of results.

    GustoData ScientistAnalytics & ExperimentationTechnical Screen
  • This question tests the ability to define business-relevant churn metrics for a SaaS platform and design a controlled experiment to optimize user onboarding.

    GustoData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates proficiency in A/B/n experimentation, hypothesis testing for binomial proportions, multiple-comparison correction methods, confidence interval estimation for conversion uplift, and experiment-related decision-making in the Analytics & Experimentation domain at an applied/intermediate statistical-analysis level.

    GustoData 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 Identify Growth Opportunities for New Payroll Feature Launch states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GustoData 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 Payroll Processing Time states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    GustoData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competency in experimental design, rare-event power analysis, precise metric and guardrail definitions, variance-reduction covariate adjustment, sequential-testing decisions, monitoring/dashboard specification, and interpretation of heterogeneous treatment effects.

    HBOData ScientistAnalytics & ExperimentationOnline Assessment
  • This question evaluates proficiency in analytics, experiment design, causal inference, metric definition, and business-impact analysis for a Product Analyst role, including handling noisy cost data and partial customer identifiers.

    Home DepotProduct AnalystAnalytics & ExperimentationOnsite
  • This question tests the ability to design an A/B test across multiple regions while accounting for sample size requirements, variance reduction techniques, and sequential monitoring protocols.

    HuluData ScientistAnalytics & ExperimentationTechnical Screen
  • This problem tests your ability to interpret multivariate regression results for product stakeholders, specifically focusing on distinguishing correlation from causation and identifying risks like collider bias.

    HuluData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's competency in cohort definition, censored-data handling, segmentation and confounding assessment, and uncertainty quantification for measuring free-trial to paid conversion, and it belongs to the Analytics & Experimentation domain within data science.

    IBMData ScientistAnalytics & ExperimentationTechnical Screen
  • This question evaluates a data scientist's skills in experimental design and statistical inference for A/B testing, revenue-impact modeling with skewed and zero-inflated metrics, segmentation for heterogeneous treatment effects, and constrained optimization to balance contribution and operational risk.

    InstacartData ScientistAnalytics & ExperimentationOnsite
  • This question evaluates a data scientist's competency in experimental design and applied statistics, specifically power and sample‑size calculations, accounting for intra‑household clustering and design effects, sequential monitoring for peeking control, and variance‑reduction or stratified randomization to handle day‑of‑week seasonality.

    InstacartData ScientistAnalytics & ExperimentationOnsite

More topics