InterviewStack.io LogoInterviewStack.io

Hypothesis and Test Planning Questions

End to end practice of generating clear testable hypotheses and designing experiments to validate them. Candidates should be able to structure hypotheses using if change then expected outcome because reasoning ground hypotheses in data or qualitative research and distinguish hypotheses from guesses. They should translate hypotheses into experimental variants and choose the appropriate experiment type such as A and B tests multivariate designs or staged rollouts. Core skills include defining primary and guardrail metrics that map to business goals selecting target segments and control groups calculating sample size and duration driven by statistical power and minimum detectable effect and specifying analysis plans and stopping rules. Candidates should be able to pre register plans where appropriate estimate implementation effort and expected impact specify decision rules for scaling or abandoning variants and describe iteration and follow up analyses while avoiding common pitfalls such as peeking and selection bias.

HardSystem Design
51 practiced
Design a scalable experimentation platform that supports A/B, factorial, and multivariate tests for a consumer SaaS product with 20M monthly users. Describe components for assignment, data collection, metric computation, monitoring (SRM, guardrails), and analysis. Discuss how to handle experiment overlap and interaction detection.
HardTechnical
66 practiced
You observe contradictory experimental signals: Net Promoter Score (NPS) increased but 30-day retention decreased for the treatment. Build a prioritized investigation plan with causal hypotheses (at least four), analyses to run (e.g., funnel, cohort, survival analysis), and potential product actions depending on findings.
MediumSystem Design
52 practiced
Design an instrumentation plan for a checkout A/B test. Include which events to track (with event names and key properties), identity/uniqueness strategy, attribution window, and data pipeline validation steps you would use to ensure results are trustworthy.
HardTechnical
72 practiced
Create a detailed pre-registration template for a high-stakes experiment (e.g., pricing change). Include precise fields for: hypothesis text, primary metric definition (SQL), guardrails, sample size and power calculations, subgroup analyses (pre-specified), stopping rules, analysis models, data exclusions, and unblinding procedure. Provide brief rationale for each field.
HardTechnical
63 practiced
Given an events table with charge_amount per order and assignment per user, describe SQL and bootstrap steps to estimate incremental revenue per user (ARPU uplift) with 95% confidence intervals, accounting for an attribution window of 14 days and censoring for users with incomplete windows. Outline how you'd compute per-user revenue and handle users with no purchases.

Unlock Full Question Bank

Get access to hundreds of Hypothesis and Test Planning interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.