Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Evaluate Customer Churn Model Performance

EasyModel Evaluation00:00
Practice interviewer
In session
5 left
00:00

Your question is Evaluate Customer Churn Model Performance. 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

Context

StreamWave uses a binary classification model to predict which paid subscribers are likely to cancel in the next 30 days so the CRM team can send retention offers. The current model was deployed 2 months ago, but leadership is concerned that campaign ROI is below target despite seemingly strong overall accuracy.

Current Performance

MetricValidation SetCurrent ProductionChange
Accuracy0.910.89-0.02
Precision0.620.48-0.14
Recall0.710.36-0.35
F1 Score0.660.41-0.25
AUC-ROC0.840.79-0.05
Churn Rate0.120.10-0.02
Users flagged / month18,0009,500-8,500
Actual churners / month12,00010,000-2,000

The Problem

The model still shows high accuracy, but it is identifying far fewer churners than expected. As a result, many at-risk users are not receiving retention offers, and the retention team wants to know whether the issue is threshold choice, class imbalance, drift, or segment-specific underperformance.

Requirements

  1. Interpret the current metrics and explain why accuracy may be misleading here.
  2. Diagnose the most likely reasons recall dropped from 0.71 to 0.36.
  3. Use the confusion matrix and business constraints to assess whether the current threshold is appropriate.
  4. Identify which additional validation or error analysis you would run.
  5. Recommend specific model or process improvements to improve performance.

Constraints

  • Retention budget supports at most 15,000 offers per month.
  • Each offer costs $8.
  • Saving a true churner is worth $95 in expected annual gross profit.
  • Product and pricing changed 6 weeks after deployment.