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 Primary and Guardrail Results

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

Your question is Conflicting Primary and Guardrail 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

Explain how you would interpret results when an A/B test shows conflicting directional movement between primary and guardrail metrics.

Discuss how you would distinguish statistical significance from practical significance, assess whether the guardrail movement is an acceptable trade-off, and decide whether to ship, iterate, or stop. State the assumptions and analysis checks you would require before making the decision, including the pre-registered MDE, confidence intervals, multiple comparisons, peeking, and possible sample ratio mismatch.