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

Choose Metrics for Ticket Escalation

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

Your question is Choose Metrics for Ticket Escalation. 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

Abzooba has built a binary classifier in its customer support workflow to predict whether an incoming enterprise support ticket should be escalated to a senior resolution team. The current model is used in production to prioritize tickets in Abzooba’s support intelligence stack, but stakeholders disagree on whether accuracy, precision, recall, or F1 should be the primary success metric.

Current Performance

The model was evaluated on 10,000 labeled tickets, of which 1,200 truly required escalation.

MetricValue
Accuracy0.90
Precision0.68
Recall0.57
F1 Score0.62
Escalation rate predicted by model10.0%
Actual escalation rate12.0%

Confusion matrix counts:

Predicted EscalatePredicted Do Not Escalate
Actual Escalate684516
Actual Do Not Escalate3168,484

The Problem

The Head of Support points to 90% accuracy and argues the model is strong. The senior operations manager is more concerned that 516 high-priority tickets are missed, causing SLA breaches and delayed enterprise responses. Meanwhile, the support team also wants to avoid too many unnecessary escalations because senior agents are capacity constrained.

Your Task

  1. Explain how you would choose between accuracy, precision, recall, and F1 for this use case.
  2. Interpret the current metrics in business terms, not just mathematically.
  3. Identify which metric should be optimized first under the stated constraints.
  4. Recommend what additional analysis you would run before changing the model or threshold.
  5. Propose concrete next steps to improve performance.

Constraints

  1. Senior escalation team can handle at most 1,300 tickets/day.
  2. Missing a true escalation is estimated to cost 8x more than an unnecessary escalation.
  3. Product leadership wants a single primary metric for model reporting.