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
ExperiencesCoaching
New
Practice
Mock InterviewsTimed interview simulations with feedbackSuccess 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
Get started

Conflicting Experiment Results

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

Your question is Conflicting Experiment Results. 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 would you do if an experiment showed conflicting results across segments?

Explain how you would determine whether the differences reflect a real treatment interaction, random variation, data-quality problems, or aggregation effects. Define the primary metric, guardrails, minimum detectable effect, unit of randomization, and analysis plan you would require before interpreting segments. Address sample-ratio mismatch, multiple comparisons, peeking, Simpson's paradox, and how you would make a ship, don't-ship, or follow-up decision.