Account Takeover Prediction

System DesignStripeLast reported August 2025Low Frequency
Reported
2× across candidate reports
First seen
January 2025
Last reported
August 2025
Reported outcome
unknown

Problem Overview

You work for a company providing a payment API. Design an end-to-end ML system to predict whether an Account Takeover (ATO) risk exists — i.e., detect if a bad actor is attempting to take over a legitimate user's account via credential theft or identity fraud. The problem is intentionally under-specified;…

  • 3 candidate-reported follow-ups — the exact probes interviewers asked, with the trigger for each
  • The rest of the problem statement — full requirements, constraints, and edge cases
  • Approach and trade-offs — what passing candidates did, and the mistakes that sink people
Unlock the full Stripe catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Stripe question.
Unlock with Pro
Already a member? Sign in
Verified Source
Every question is reconstructed from multiple independent candidate reports. Verbatim follow-ups, not invented ones.
Codex Fact-Checked
Technical claims, formulas, and scale numbers are reviewed against primary sources.
Interviewer Follow-ups
The exact follow-ups reported by candidates, with the trigger that prompts each one — plus the mistakes that sink people.
Is this helpful?