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

Novelty Bias in Discovery Test

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

Your question is Novelty Bias in Discovery Test. 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 a music-creation platform and want to test a redesigned sample-discovery experience that makes new sounds more visually prominent in the browse surface. The team believes the new design will increase the rate at which users preview and save samples, but worries that any early lift may come from curiosity rather than sustained value. You need to design an experiment that can separate a true product improvement from a short-lived novelty effect.

Constraints

  • Eligible traffic: 120,000 browse-surface visitors per day
  • Maximum experiment duration: 21 days
  • 50/50 allocation after a 1-day instrumentation ramp
  • Save-to-project rate cannot decline by more than 1% relative
  • Crash rate cannot increase by more than 0.2 percentage points

Question

How would you design and analyze this experiment so that you can detect a meaningful lift while accounting for novelty effect risk, and what would your ship decision rule be if early results are strong but decay over time?