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

Measure Novelty in Feature Launch

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

Your question is Measure Novelty in Feature Launch. 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

Context

PulseChat, a consumer messaging app, is testing a new feature called Quick Reactions that lets users respond to messages with one-tap animated reactions. Product leadership wants to know whether the feature creates durable engagement or just a short-lived novelty spike.

Hypothesis Seed

The team believes Quick Reactions will increase meaningful conversation engagement by making lightweight responses easier. However, they are explicitly worried that users may overuse the feature in the first few days because it is new and visually salient, with the effect fading after novelty wears off.

Constraints

  • Eligible traffic: 240,000 daily active users per day
  • 80% of DAU are eligible for the experiment after app-version filtering
  • Maximum decision window: 21 days
  • Randomization must be user-level because the feature is persistent in the UI
  • A false positive is costly: shipping a novelty-only feature adds long-term UI clutter and engineering maintenance
  • A false negative is acceptable if the true lift is very small
  • The team wants at least 80% power at a 5% significance level

Task

  1. Define the null and alternative hypotheses, making clear how you will distinguish a novelty effect from a durable treatment effect.
  2. Choose a primary metric, 2-4 guardrails, and at least one secondary metric. State the baseline and an explicit MDE.
  3. Calculate the required sample size and show whether the experiment can be completed within 21 days given available traffic.
  4. Propose the experiment design: unit of randomization, allocation, duration, and any stratification. Explain how your design helps detect novelty effects rather than just average lift.
  5. Pre-register the analysis plan, including the statistical test, peeking policy, multiple-comparison policy, and how you will make the final ship / don’t-ship decision if week 1 is positive but week 3 is flat or negative.

Be concrete: use real numbers, not placeholders. Your answer should explicitly address novelty effects as a first-class risk, not just mention them in passing.