Day 110 of 133
Design real-time fraud detection (Stripe Radar) + DSA review
Velocity / graph / behavioral features; delayed labels; cost-sensitive thresholds.
DSA · NeetCode Backtracking
- Combination SumDSA · Backtracking
Interview questions to prep
- How do you avoid duplicate combinations without a set — what's the index-passing trick?
- Compare with combination-sum-ii where each candidate can only be used once.
ML System Design · Fraud detection
Interview questions to prep
- Walk me through designing Stripe Radar — real-time fraud detection.
- How do you balance false positives (blocked good users) vs false negatives (fraud)?
Interview questions to prep
- What kinds of features (velocity, graph, behavioral) actually catch fraud?
- How do you serve graph-based fraud features in real-time without exploding compute?
Interview questions to prep
- Design a system that detects fake or fraudulent contributed content in maps reviews, photos, or edits.
- How would you combine user reputation, content features, graph signals, velocity features, and human review?
- What metrics balance user trust, false positives on legitimate contributors, and time-to-removal for abuse?
Interview questions to prep
- Fraud labels arrive weeks late (chargebacks). How do you train and monitor under delayed labels?
- How would you use early proxy signals (e.g., risk score, manual review) when chargebacks are slow?
References & further reading