Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Predict Loan Default End-to-End

EasyMachine Learning00:00
Practice interviewer
In session
5 left
00:00

Your question is Predict Loan Default End-to-End. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Business Context

LendWise, a mid-size digital lender processing about 250K personal loan applications per year, wants a predictive model to estimate whether an applicant will default within 12 months of origination. The model will support underwriting decisions and risk-based pricing, so it must be accurate, explainable, and stable in production.

Dataset

You are given a historical loan-origination dataset with one row per funded loan.

Feature GroupCountExamples
Applicant demographics6age, employment_status, residence_type
Financial attributes10annual_income, debt_to_income, revolving_utilization
Credit history9fico_band, delinquencies_2y, inquiries_6m
Loan attributes7loan_amount, term_months, interest_rate, purpose
Behavioral / derived fields6income_to_loan_ratio, recent_credit_velocity
  • Size: 120K funded loans, 38 input features
  • Target: default_12m — whether the borrower defaulted within 12 months
  • Class balance: 11% positive (default), 89% negative
  • Missing data: 8% missing in employment-related fields, 5% in revolving utilization, and up to 18% in some bureau-derived attributes

Success Criteria

A good solution should achieve strong ranking performance and usable recall for the risk team. Target performance is ROC-AUC >= 0.82, PR-AUC >= 0.42, and recall >= 0.70 at precision >= 0.35 on a held-out test set.

Constraints

  • Predictions must be generated in <50 ms per application in an online underwriting API.
  • The model must be explainable enough for risk review and adverse-action reason reporting.
  • Training can run offline daily or weekly; inference cost should remain low.

Deliverables

  1. Build an end-to-end supervised classification pipeline from raw data to evaluated model.
  2. Explain your preprocessing, feature engineering, model selection, and validation strategy.
  3. Compare at least one interpretable baseline with a stronger non-linear model.
  4. Select an operating threshold based on business tradeoffs, not accuracy alone.
  5. Describe how you would deploy, monitor, and retrain the model in production.