Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Evaluate Metrics for Rare Player Behavior

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

Your question is Evaluate Metrics for Rare Player Behavior. 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

At ArenaPlay, a binary classification model predicts whether a player will exhibit a rare harmful behavior within the next 30 days. The event rate is only 0.1%: in a validation set of 1,000,000 players, only 1,000 are actual positives.

The team initially celebrated high accuracy, but operations reports show the model is missing many true cases while also generating too many alerts for the review team.

Current Performance

MetricCurrent ModelBaseline: Predict All Negative
Accuracy99.40%99.90%
Precision8.3%0.0%
Recall50.0%0.0%
F1 Score14.3%0.0%
AUC-ROC0.910.50
PR AUC0.190.001
Flagged players6,0000

The Problem

Leadership wants to know which metrics should be used to evaluate this model and whether the current model is good enough to deploy. The main concern is that accuracy looks excellent despite poor practical usefulness in a highly imbalanced setting.

Requirements

  1. Explain which evaluation metrics are most appropriate for this class imbalance and why.
  2. Interpret the current metrics and identify what they imply about model quality.
  3. Discuss whether accuracy and AUC-ROC alone are sufficient here.
  4. Recommend how you would choose an operating threshold based on business tradeoffs.
  5. Propose improvements to evaluation and validation before deployment.

Constraints

  • Manual review team can investigate at most 2,000 flagged players per week.
  • Missing a true positive is estimated to be 20x more costly than reviewing a false positive.
  • Predicted probabilities may be used downstream for prioritization, so score calibration matters.