Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Power Analysis for Survey Experiment

HardA/B Testing & Experimentation00:00
Practice interviewer
In session
5 left
00:00

Your question is Power Analysis for Survey Experiment. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Scenario

You are planning a customer survey or product experiment and need to decide whether the design is adequately powered before launch. The team wants confidence that the study can detect a meaningful change without over-sampling or drawing conclusions too early.

Question

How would you think about sample size and statistical power for this survey or experiment? Walk through how you would choose an MDE, define the primary metric and guardrails, and decide whether the planned test is large enough to support a decision.

What matters

  • Primary metric must be defined before sizing the test
  • MDE should reflect a meaningful business or user impact
  • Guardrails prevent shipping a treatment that improves one metric while harming others
  • Power depends on baseline rate, variance, alpha, and desired detectable lift