Experiment design for emails introducing a new product to existing customers

Quick Overview

A product manager interview question on how to A/B test emails that announce a new product to Capital One customers. It tests choosing an adoption-based success metric, randomization and holdout design, sample sizing, guardrails such as unsubscribes and spam reports, and how to read and act on the results.

Experiment design for emails introducing a new product to existing customers

Company: Capital One

Role: Product Manager

Category: Analytics & Experimentation

Difficulty: medium

Interview Round: Other

You are a product manager at Capital One, and the company is about to email customers to announce a new product. How would you A/B test those announcement emails? ```hint Decide what success means first Ask what the email exists to achieve, then check whether the metric that is easiest to move is the one that reflects it. ``` ### Clarifying Questions - Which product is being announced, and what should a reader do next: apply, turn on a feature, or simply learn that it exists? - Who receives the email: all customers, or only those who have opted in to marketing email and are eligible for the product? - Is the test about the content (subject line, message, call to action), about timing and targeting, or about whether sending the email helps at all? - Is this a one-time send, or a template that future product launches will reuse? ### What a Strong Answer Covers - A hypothesis and a primary metric tied to product adoption, with opens and clicks treated as diagnostics - Randomization at the customer level, variants that change one element each, and a no-email holdout - A sample-size estimate for the chosen metric and a fixed measurement window - Guardrails such as unsubscribes, spam and phishing reports, plus compliance review of every variant - Analysis and decision rules, including unreliable open tracking and the risk of false winners across several variants ### Follow-up Questions - The variant with the best open rate produced the fewest sign-ups. Which one do you ship, and why? - Your eligible list is too small to detect a change in sign-ups. What would you do instead? - How would you test ten subject lines at once without being fooled by a false winner?

Overview: A product manager interview question on how to A/B test emails that announce a new product to Capital One customers. It tests choosing an adoption-based success metric, randomization and holdout design, sample sizing, guardrails such as unsubscribes and spam reports, and how to read and act on the results.

Capital One logo
Capital One
May 4, 2025
mediumProduct ManagerOtherAnalytics & Experimentation
0
0

You are a product manager at Capital One, and the company is about to email customers to announce a new product. How would you A/B test those announcement emails?

Clarifying Questions Guidance

  • Which product is being announced, and what should a reader do next: apply, turn on a feature, or simply learn that it exists?
  • Who receives the email: all customers, or only those who have opted in to marketing email and are eligible for the product?
  • Is the test about the content (subject line, message, call to action), about timing and targeting, or about whether sending the email helps at all?
  • Is this a one-time send, or a template that future product launches will reuse?

What a Strong Answer Covers Guidance

  • A hypothesis and a primary metric tied to product adoption, with opens and clicks treated as diagnostics
  • Randomization at the customer level, variants that change one element each, and a no-email holdout
  • A sample-size estimate for the chosen metric and a fixed measurement window
  • Guardrails such as unsubscribes, spam and phishing reports, plus compliance review of every variant
  • Analysis and decision rules, including unreliable open tracking and the risk of false winners across several variants

Follow-up Questions Guidance

  • The variant with the best open rate produced the fewest sign-ups. Which one do you ship, and why?
  • Your eligible list is too small to detect a change in sign-ups. What would you do instead?
  • How would you test ten subject lines at once without being fooled by a false winner?