Address Fraud Detection with Imbalance and Concept Drift Solutions
NetflixData Scientist · OnsiteLast updated
Evaluates end-to-end fraud detection ML system design for online payments under drift and imbalance. Strong answers handle delayed labels, class imbalance, feature engineering, cost-sensitive validation, real-time deployment, threshold actions, monitoring, retraining, and concept drift.
Scenario
You are tasked with building a fraud-detection model for an online payments product.
Question
Outline the end-to-end ML workflow: data collection, feature engineering, model selection, validation, deployment, and monitoring. How would you handle severe class imbalance and concept drift in this context?
Hints
Discuss resampling, cost-sensitive learning, ROC-AUC, sliding windows, and automated retraining triggers.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.