Scenario
You are designing an end-to-end fraud detection system for an online platform (e.g., e-commerce marketplace, payments, account signup, or ad traffic). The system should detect and prevent fraudulent activity while minimizing impact on legitimate users.
Requirements
-
Goal
: Predict whether an event (transaction / login / signup / ad click) is fraudulent and decide what action to take.
-
Latency
: Support near-real-time decisioning (e.g., sub-second to a few seconds) for high-risk actions.
-
Cold start
: Handle
new users / new devices / new merchants
with little or no historical data.
-
Imbalanced data
: Fraud rate is low (e.g., <1%), so the dataset is highly
class-imbalanced
.
-
Actions
: Decide between actions such as
allow
,
step-up verification (2FA / OTP)
,
manual review
, or
block
.
-
Learning loop
: Incorporate delayed labels (chargebacks, user reports, investigation outcomes) and retrain/refresh models.
What to cover
-
Data sources and feature engineering (real-time + batch)
-
Model choice(s) and how you handle cold start + imbalance
-
Evaluation metrics and offline/online validation
-
System architecture for training, serving, monitoring
-
Abuse/adversarial considerations and how you prevent model exploitation