Capital One·Data Scientist·Onsite - Product Sense / Strategy
Jul 2026
Capital One data scientist loop with a single massive product case question that covers basically everything: market framing, revenue modeling, metrics, prioritization, experiment design, and a finance pushback scenario. It's a lot to hold in your head at once and the sample size calculation at the end will catch you off guard if you haven't practiced it recently.
- Pick a consumer digital app you love and explain the product to someone who has never heard of it. Cover the core jobs it does for users, who the main audience segments are, its top three competitors, and what makes it different from those competitors.
- Walk through all the current revenue streams for the app you chose and explain the unit economics. Then propose one entirely new revenue stream and build out a six-month ROI model for it.
- Define three success metrics for the new revenue stream you proposed. Each metric needs a clear numerator, denominator, and event plus time window definition. Also define two guardrail metrics with explicit thresholds.
- Come up with six concrete product improvements for the app, then choose one to ship first and explain why you'd prioritize it over the others.
- Design an A/B test for the product improvement you just prioritized. Specify the unit of randomization, who is eligible and who gets excluded, how assignment works, and what bias mitigations you'd put in place. Then compute the minimum sample size and estimated test duration using these inputs: 500,000 daily active users, 15% baseline conversion per user-day, expected absolute lift of 2 percentage points, 80% power, two-sided alpha of 5%, and a 1:1 split. Show your formula and state your assumptions.
- Finance pushes back and says the improvement is too expensive to build. Walk through your cost-benefit model, identify the breakeven point, and explain what decision you'd make if interim results after two weeks are underperforming the minimum detectable effect.
“I picked Duolingo and immediately regretted it because the competitive landscape is kind of shallow if you don't prep it in advance.” The rest of the author's notes on Data Scientist interview at Capital One, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post