Dataford
Interview QuestionsInterview GuidesExperiencesCoaching
New
Pricing
Get started
Dataford
Popular roles
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Browse
Browse All RolesEvery role hub, from analyst to MLBrowse All CompaniesCompany-specific interview loopsAll Interview GuidesThe full guide library
Top questions by role
Software EngineerData AnalystData ScientistData EngineerBusiness AnalystAI EngineerMachine Learning EngineerProduct Manager
Top questions by skill
SQLPythonStatisticsMachine LearningA/B TestingSystem DesignGenerative AIProduct SenseMetricsBehavioral
Browse all questions →Try a mock interview
Experiences
Practice
Mock InterviewsTimed interview simulations with feedbackCoaching1:1 coaching with people at your target companiesSuccess PathYour 6-week structured planModulesCurated lessons by topicWebinarsTalks from ex-Big Tech data leadsPlaygroundA free-form scratch editor
Learn
BlogInterview strategy and career adviceTech Job Market ReportHiring trends across data and AI rolesFor UniversitiesDataford for career centersAbout DatafordWho we are and how we build
Pricing
Build my plan

Predict Loan Default with Ensembles

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

Your question is Predict Loan Default with Ensembles. 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

NorthBridge Finance issues unsecured personal loans to roughly 120,000 applicants per month. The risk team wants a production-ready model that predicts whether an applicant will default within 12 months so underwriting can reduce losses without rejecting too many good customers.

Dataset

You are given a historical loan-origination dataset built at application time only. Do not use post-loan repayment behavior as features.

Feature GroupCountExamples
Applicant demographics6age, region, housing_status, dependents
Credit bureau variables14bureau_score, delinquencies_12m, credit_utilization, inquiries_6m
Income & employment9annual_income, employment_length, employer_type, income_to_debt_ratio
Loan application details8loan_amount, term_months, interest_rate, purpose, channel
Engineered temporal signals5applications_last_30d, days_since_last_inquiry, bureau_file_age
  • Rows: 420,000 funded loans from the last 24 months
  • Target: default_12m = 1 if the borrower becomes 90+ days past due within 12 months, else 0
  • Class balance: 11.4% positive, 88.6% negative
  • Missing data: 18% missing in employment fields, 7% in bureau variables for thin-file applicants, <2% elsewhere

Success Criteria

A good solution should achieve strong ranking performance and support threshold-based underwriting decisions. Target ROC-AUC >= 0.84, PR-AUC >= 0.42, and recall >= 0.70 at precision >= 0.35 on a held-out out-of-time test set.

Constraints

  • Inference must complete in <50 ms per application in an online API
  • The risk team needs feature-level explanations for adverse action review
  • Retraining can happen weekly; feature generation must be reproducible in batch and online
  • The model must be robust to missing values and moderate class imbalance

Deliverables

  1. Build a binary classification pipeline for default_12m
  2. Compare at least one linear baseline and one tree-based ensemble
  3. Explain feature engineering, leakage prevention, and validation design
  4. Select an operating threshold for underwriting based on precision/recall tradeoffs
  5. Report final test metrics and the top risk drivers