About the Role
Forward processes payments for thousands of merchants across dozens of partner platforms.
The Risk Data Scientist's job is to build the model-driven intelligence layer that replaces static rules with adaptive, evidence-based decisioning across three risk domains: merchant underwriting and approval optimization, real-time transaction fraud and anomaly detection, and AML/transaction monitoring and SAR prioritization. You will own the full modeling lifecycle - from problem framing and feature engineering to training, validation, deployment, monitoring, and regulatory governance.
This is applied ML in a high-stakes, regulated financial context. Models you build will directly determine approval rates, fraud loss rates, chargeback exposure, and SAR filing quality. They will be scrutinized by bank sponsors, card networks, and regulators. The work demands both technical rigor and regulatory fluency: someone who understands why a gradient boosting ensemble outperforms logistic regression on imbalanced fraud data AND why SHAP explainability is a compliance requirement under ECOA adverse action rules.
Forward is early in this journey. The person who takes this role will define the ML architecture, build the model governance framework, and set the standard for how Forward uses machine learning in regulated financial services.
Key ResponsibilitiesMerchant Risk: Underwriting and Approval Rate Optimization
- Build and own the merchant risk scoring model - the centerpiece of Forward's move from static rules to model-based decisioning. This model drives tier assignment (auto-approve, conditional approve, RFI, decline) for every merchant application, replacing hand-coded thresholds with evidence-based probability scores.
- Design vertical-specific scoring variants for contractor/home services, healthcare, and hospitality - each with distinct chargeback profiles, fraud patterns, and volume distribution that a single generalized model cannot capture.
- Build bust-out fraud detection models that catch the full behavioral arc: months of normal volume cultivating trust, followed by rapid drawdown. Use graph neural network (GNN) approaches to surface shared infrastructure - phone numbers, IP ranges, device fingerprints, bank accounts - across seemingly unrelated merchants in the same fraud ring. At scale, GNN-based ring detection catches 40%+ more coordinated fraud than models that evaluate merchants in isolation.
- Integrate model scores as dynamic inputs to Taktile rules - not as replacements for rules, but as continuous risk signals that allow thresholds to flex based on model confidence. A merchant with a 95% confidence clean score should not face the same velocity friction as one at 60%.
- Measure outcomes in business terms: approval rate lift, false positive rate reduction, and chargeback rate per merchant segment vs. Visa/Mastercard program thresholds.
Transaction Risk: Real-Time Fraud and Anomaly Detection
- Build real-time transaction fraud scoring that operates within the authorization window: sub-100ms latency from scoring request to decisioning output. Design the feature engineering architecture - feature store, pre-computed signals, streaming aggregations - that makes this latency target achievable on Forward's Snowflake-based stack.
- Build card testing detection models using high-frequency, low-value authorization pattern recognition - with explicitly defined precision and recall targets. Flag the pattern before the fraudster pivots to high-value transactions.
- Develop merchant behavioral baseline models that detect deviations before they become losses: MCC drift, refund rate spikes, chargeback ratio changes, velocity anomalies, and settlement manipulation patterns. Build portfolio-level exposure models that surface correlated risk across the merchant book before it crystallizes into loss events.
- Use unsupervised approaches - isolation forests, autoencoders - for emerging fraud typologies that have no labeled training data yet, layered alongside supervised models for known patterns. Unknown unknowns are where bust-out fraud lives before it gets named.
AML and Transaction Monitoring
- Partner with the Compliance team to evolve rule-based transaction monitoring into a hybrid system: rules for explainability and auditability, ML for alert prioritization, coverage, and signal quality.
- Build SAR prioritization models that score open TM alerts by money laundering typology risk - enabling analyst triage to focus on highest-risk cases first. The industry baseline for AML false positive rates is 50-90%. The target here is below 40%, achieved through model-driven scoring rather than alert volume alone.
- Build structuring detection models that complement velocity rules with behavioral pattern recognition: temporal sequencing, counterparty relationships, amount clustering, and network-level coordination signals.
- Own the quantitative side of SAR quality: alert-to-SAR conversion rate, filing timeliness