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

Classify Resideo Device Support Issues

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

Your question is Classify Resideo Device Support Issues. 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

Resideo wants to reduce manual triage for support cases coming from Honeywell Home thermostats, security devices, and water leak sensors. You need to show when supervised learning is appropriate for predicting known issue categories and when unsupervised learning is better for discovering new patterns in unlabeled support traffic.

Dataset

You are given historical support-case data exported from Resideo customer support systems.

Feature GroupCountExamples
Structured case metadata10product_line, device_model, firmware_version, app_platform, region
Device telemetry aggregates12reconnect_count_24h, battery_level, signal_strength, temp_delta, sensor_fault_count
Customer/account context6install_age_days, homeowner_vs_pro, warranty_status, prior_case_count
Text-derived features20TF-IDF or embedding features from case subject and notes
Labels1known_issue_type for a subset of cases
  • Size: 82K support cases over 18 months, 48 usable features after preprocessing
  • Target: known_issue_type with 6 classes for labeled cases only
  • Label coverage: 61K labeled cases, 21K unlabeled cases
  • Missing data: ~9% missing telemetry fields, ~14% missing firmware_version, sparse text fields in ~7% of rows

Success Criteria

A strong solution should:

  • Train a supervised model on labeled data that achieves macro F1 >= 0.72 on a held-out test set
  • Produce unsupervised clusters on all cases with silhouette score >= 0.20 and a clear interpretation of cluster themes
  • Explain, in practical terms, the difference between supervised and unsupervised learning and when each should be used at Resideo

Constraints

  • Predictions will be used in a support workflow, so results must be explainable enough for operations teams
  • Batch scoring must finish in under 10 minutes for ~10K daily new cases
  • The approach should tolerate mixed structured, categorical, and text-derived features

Deliverables

  1. Build a supervised model to predict known_issue_type for labeled cases
  2. Build an unsupervised model to group all support cases and identify emerging issue patterns
  3. Compare the two approaches, including required labels, objective, outputs, and evaluation methods
  4. Describe how you would deploy both outputs in a Resideo support triage pipeline
  5. Provide code, metrics, and a short explanation of tradeoffs