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

Metrics for Experiments

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

Your question is Metrics for Experiments. 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

What metrics would you use?

Asked in the tech round, during the A/B testing and statistics stage. This is a follow-up on choosing primary, secondary, and guardrail metrics for an experiment.

Explain how you would:

  1. Select and define a single primary metric, including its unit of analysis and business rationale.
  2. Choose secondary metrics without allowing exploratory results to drive the launch decision.
  3. Define guardrails and actionable thresholds.
  4. Set an MDE, calculate the required sample size, and explain how you would analyze the result.
  5. State the ship, do-not-ship, and iterate rules, including how you would handle peeking and sample ratio mismatch.