How do you decide when an A/B test result is trustworthy enough to ship, especially when the result is close to flat?

role-specific · Senior level · product-management

What the interviewer is really asking

Assesses experimentation rigor — whether the candidate understands power, significance, peeking, and the difference between 'not significant' and 'no effect' rather than treating any positive number as a win.

What to say

What to avoid

Example answers

Strong: When a redesign test came back +0.8% but not significant, I checked the math first: we were underpowered for an effect that small, so it was inconclusive, not flat. The change was low-risk and reversible and qualitative feedback was positive, so I shipped behind a flag and kept measuring with a longer holdback rather than declaring victory. Had it been a pricing change, I'd have demanded a clean, powered, significant read before touching it.

Weak: It was up 0.8%, so even though it wasn't quite significant the direction was positive, so I'd go ahead and ship it.

Want questions matched to your role? Paste a job title, job description, or CV and get a personalized set, or go Pro to unlock the full bank.