Context
At a major financial product company, the loan origination flow is a balance between risk mitigation and conversion. Crucially, Employment Verification (EV) happened at the very end of the funnel—after the user had already invested time and effort.
The Problem
We were seeing massive drop-offs at this comprehensive final step.
The Hypothesis: These weren't just "lazy" users. They were high-intent applicants who, faced with a friction-heavy verification step, were likely taking offers from competitors who approved them faster.
The bank assumed EV was a necessary shield. But if the shield isn't stopping bad actors—only slowing down good ones—it's not a shield; it's a leak.
The Solution
Part 1: Causal Discovery
Before suggesting we remove a risk control, I needed proof. I applied causal inference techniques (using XGBoost feature importance and correlation analysis) on historical loan performance data.
The finding was stark: For applicants with FICO > 720, the Employment Verification status had zero correlation with default rates (p > 0.05). The signal was noise.
Part 2: Stratified Randomization Test
We couldn't just turn it off globally (too risky). I designed a stratified randomization A/B test. We isolated the "High FICO / Low Risk" segment and split them:
- Control: Standard flow (EV Required)
- Treatment: Frictionless flow (EV Skipped)
Results
- ➜ Conversion: Treatment group saw a massive lift, capturing 300+ additional customers monthly.
- ➜ Risk: No statistically significant increase in early payment defaults (EPD) in the treatment group.
- ➜ Impact: $50M in realized loan volume during rollout, with a $114M annualized projection.
Technologies
Lessons
- Rigorous testing challenges "obvious" assumptions. "More verification = Less risk" seems intuitive, but data proved it wrong for specific segments.
- Stratified randomization is surgical. It allowed us to innovate in a high-risk environment without exposing the entire portfolio.
- Translate statistics into operations. The XGBoost insight wasn't just a chart; it became a decision tree rule that automatically routed users.
About the author
Suyash
I build software that solves real problems — currently ClinicOS, a clinic management system I designed sitting in my brother's clinic, watching him work. When I'm not writing code, I'm behind a camera shooting landscapes, working a bag, swinging a steel mace, or on a yoga mat. The through-line across all of it: discipline, craft, and an obsession with doing things right.