What Fraud Engineers Actually Build
Fraud engineering spans detection, prevention, and response systems.
Detection Systems
Identifying bad actors:
- Transaction monitoring — Real-time fraud scoring
- Anomaly detection — Unusual behavior patterns
- Rule engines — Configurable fraud rules
- ML models — Predictive fraud detection
- Graph analysis — Network and relationship patterns
Prevention Systems
Stopping fraud before it happens:
- Risk scoring — Assessing transaction/user risk
- Identity verification — KYC, document verification
- Device fingerprinting — Recognizing returning devices
- Velocity checks — Detecting rapid-fire attacks
- Challenge flows — Step-up authentication
Operations Support
Enabling fraud teams:
- Review queues — Manual review workflows
- Case management — Investigation tools
- Reporting — Fraud metrics and trends
- Feedback loops — Model improvement from reviews
- Alert systems — Real-time fraud notifications
Fraud Detection Technology
ML Approaches
| Technique | Use Case |
|---|---|
| Gradient boosting | Transaction scoring |
| Neural networks | Behavioral patterns |
| Graph neural networks | Network fraud |
| Anomaly detection | Unusual behavior |
| Ensemble methods | Combined signals |
Infrastructure
- Real-time: Kafka, Flink for stream processing
- Feature store: Feast, Tecton for ML features
- Rules engine: Custom or vendor solutions
- Data: Snowflake, BigQuery for analysis
Skills by Experience Level
Junior Fraud Engineer (0-2 years)
Capabilities:
- Implement fraud rules and thresholds
- Analyze fraud patterns
- Support model development
- Build review tool features
- Generate fraud reports
Learning areas:
- ML model development
- Feature engineering
- Adversarial thinking
- System design
Mid-Level Fraud Engineer (2-5 years)
Capabilities:
- Develop fraud detection models
- Design feature pipelines
- Analyze fraud patterns deeply
- Build real-time systems
- Balance precision/recall
- Mentor juniors
Growing toward:
- Architecture decisions
- Model strategy
- Technical leadership
Senior Fraud Engineer (5+ years)
Capabilities:
- Architect fraud platforms
- Lead model development
- Design adversarial-resistant systems
- Balance fraud/user experience
- Drive fraud strategy
- Mentor teams
Curiosity & fundamentals
Independence & ownership
Architecture & leadership
Strategy & org impact
Interview Focus Areas
Technical Skills
- "How do you handle class imbalance in fraud models?"
- "What features would you use to detect account takeover?"
- "How do you evaluate a fraud model?"
- "Explain precision/recall tradeoffs for fraud detection"
System Design
- "Design a real-time transaction fraud system"
- "How would you build a rule engine for fraud?"
- "Design a system to detect fake accounts"
Adversarial Thinking
- "How would you circumvent a typical fraud system?"
- "How do you prevent model gaming?"
- "What happens when fraudsters adapt to your model?"
Common Hiring Mistakes
Hiring Generic ML Engineers
Fraud has unique challenges: extreme class imbalance, adversarial adaptation, real-time requirements, business impact. Generic ML engineers need significant ramp-up. Prioritize fraud or security experience.
Ignoring Adversarial Mindset
Good fraud engineers think like attackers. They anticipate how fraudsters will adapt. This mindset is hard to teach—evaluate for security thinking.
Focusing Only on Detection
Prevention, user experience, and operational efficiency matter too. A model that blocks 10% of good users isn't successful. Look for engineers who balance detection with usability.
Underestimating Operations
Fraud fighting requires manual review, investigation, and feedback. Engineers who dismiss "ops work" won't build effective systems.
Where to Find Fraud Engineers
High-Signal Sources
Fraud engineers often emerge from financial services, e-commerce, or trust & safety teams. Look for engineers at companies with significant fraud exposure: payment processors (Stripe, PayPal), marketplaces (Airbnb, eBay), fintech (Chime, Cash App), and social platforms (Meta, Twitter). The fraud detection vendor ecosystem (Sift, Featurespace, DataVisor) also produces strong candidates.
Conference and Community
The Merchant Risk Council (MRC) community attracts fraud professionals. KDD (Knowledge Discovery and Data Mining) conferences feature fraud detection research. Look for engineers presenting on adversarial ML, anomaly detection, or financial crime detection.
Company Backgrounds That Translate
- Fintech companies: Direct fraud detection experience
- E-commerce platforms: Payment fraud and account abuse
- Social platforms: Fake account and spam detection
- Gaming companies: Cheating and bot detection (similar adversarial patterns)
- Ad tech: Click fraud detection uses comparable techniques
Recruiter's Cheat Sheet
Resume Green Flags
- Fraud detection system experience
- ML in adversarial contexts
- Real-time system experience
- Feature engineering for fraud
- Rule engine experience
- Metrics-driven approach
Resume Yellow Flags
- No fraud or security experience
- Only batch ML (no real-time)
- Cannot discuss precision/recall
- Dismisses manual review importance
Technical Terms to Know
| Term | What It Means |
|---|---|
| False positive | Blocking a good user |
| Precision/recall | Detection accuracy metrics |
| Class imbalance | Rare fraud vs common legitimate |
| Feature engineering | Creating fraud signals |
| Adversarial ML | Fraud adapts to models |
| Chargeback | Disputed payment transaction |