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

Test Sign-Up Button Color

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

Your question is Test Sign-Up Button Color. 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

AcmeFit, a subscription fitness app, wants to know whether changing the homepage Sign Up button from gray to green increases new-user registration. This is a low-cost UI change, but the team wants a disciplined experiment before shipping globally.

Hypothesis Seed

The product manager believes the current gray button has low visual salience on mobile landing pages. A greener, higher-contrast button may increase the proportion of visitors who complete registration after viewing the landing page.

Constraints

  • Eligible traffic: 120,000 unique landing-page visitors per day
  • Platform mix: 70% mobile web, 30% desktop web
  • Current landing-page-to-sign-up conversion rate: 8.0%
  • Maximum experiment duration: 14 days
  • The team only wants to ship if the change produces a meaningful lift; a false positive is worse than a false negative because the button color would be rolled out to all acquisition traffic and could hurt paid marketing efficiency.
  • The experiment platform supports user-level randomization and daily monitoring for safety, but the team does not want ad hoc peeking for significance.

Deliverables

  1. Define the null and alternative hypotheses, and state whether you would use a one-sided or two-sided test.
  2. Specify the primary metric, 2-4 guardrail metrics, and at least one secondary metric. Include the unit of analysis and a clear minimum detectable effect (MDE).
  3. Calculate the required sample size per arm using the baseline conversion rate, your chosen alpha/power, and the MDE. Translate that into expected runtime given available traffic.
  4. Choose the unit of randomization, allocation strategy, duration, and any stratification or blocking you would use.
  5. Pre-register the analysis plan: statistical test, peeking policy, multiple-comparisons policy, SRM checks, and what decision rule you would use to ship / not ship / iterate.