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

Resolve Conflicting Metric Test Results

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

Your question is Resolve Conflicting Metric Test 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

Scenario

You work on an AI-assisted customer support product and want to test a new agent workflow that surfaces a more prominent suggested reply and next-best-action panel during live chats. The team believes the change will help agents resolve more conversations without escalation and reduce average handle time, but there is concern that faster resolutions could feel less personalized and lower customer satisfaction. You need an experiment design that can handle a likely lift in one metric and a drop in another.

Constraints

  • Eligible traffic: 180,000 support conversations per day
  • Maximum experiment duration: 21 days
  • Only 60% of conversations are handled by agents eligible for the new workflow
  • Customer satisfaction cannot decline by more than 0.5 percentage points
  • Average handle time cannot worsen by more than 3%

Question

How would you design this experiment so that you can make a clear ship or don’t-ship decision if the treatment improves one key outcome but harms another? Be explicit about your hypothesis, metric hierarchy, power and MDE, randomization choice, analysis plan, and the pitfalls you would guard against before interpreting the result.