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 Email CTA for Demo

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

Your question is Test Email CTA for Demo. 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

The Databricks demand generation team wants to improve conversion from a nurture email campaign that drives prospects to request a product demo. They are considering a new email creative in Marketo with a stronger CTA and more prominent Databricks Lakehouse messaging.

Hypothesis Seed

The team believes the new email will increase demo-request conversion among eligible leads by making the value proposition clearer and reducing friction on the landing path. However, a false positive is costly because the new creative would be rolled out to a large global nurture program, while a false negative means delaying a potentially meaningful pipeline gain for one quarter.

Constraints

  • Eligible traffic: 120,000 marketable leads per week across North America and EMEA
  • Current email send cadence: one nurture email per lead per week
  • Baseline demo-request conversion within 7 days of send: 3.2%
  • Maximum experiment duration: 3 weeks, because the QBR launch calendar requires a decision
  • Allocation can be 50/50 after a small instrumentation ramp
  • The team wants to detect at least a 10% relative lift in demo-request conversion
  • Guardrails: unsubscribe rate and spam complaint rate cannot materially worsen

Deliverables

  1. Define the null and alternative hypotheses, the primary metric, 2-4 guardrails, and at least one secondary metric. Be explicit about the unit of randomization and unit of analysis.
  2. Calculate the required sample size per arm using a clearly stated alpha, power, baseline rate, and MDE. Translate that into expected runtime given the available Databricks campaign traffic.
  3. Propose the experiment design in Databricks terms: allocation, duration, any stratification, and whether you would use CUPED or another variance-reduction approach.
  4. Pre-register the analysis plan: statistical test, peeking policy, multiple-comparison treatment, SRM checks, and how you will handle any mismatch between randomization and analysis units.
  5. State a clear ship / do-not-ship / iterate rule that respects guardrails, and list the main pitfalls that could invalidate the result.