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 Factory Equipment Failures

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

Your question is Predict Factory Equipment Failures. 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

Northline Components operates 18 manufacturing lines across 3 plants and loses significant production time to unplanned machine stoppages. The operations team wants a model that predicts whether a machine will fail in the next 7 days so maintenance can be scheduled before breakdowns occur.

Dataset

You are given historical machine-level daily records built from sensor streams, maintenance logs, and machine metadata.

Feature GroupCountExamples
Sensor aggregates22avg_temperature_24h, vibration_rms_24h, pressure_std_24h, motor_current_max_24h
Usage and load8runtime_hours_7d, cycles_completed_7d, load_factor_avg, shift_count
Maintenance history7days_since_last_service, service_type_last, parts_replaced_30d, prior_failures_90d
Machine metadata6machine_type, line_id, manufacturer, install_age_days, plant_id
Derived trend features9temp_slope_7d, vibration_delta_3d, rolling_fault_code_count
  • Size: 420K machine-day rows covering 30 months, 52 features
  • Target: Binary label indicating whether the machine fails within the next 7 days
  • Class balance: Failures are rare; about 4.6% positive class
  • Missing data: 12% missing in some sensor fields due to telemetry dropouts; 6% missing in maintenance fields for newly installed machines

Success Criteria

A good solution should identify at least 75% of upcoming failures while keeping precision high enough that maintenance teams are not overwhelmed. The model should produce ranked risk scores and explain the main drivers of each alert.

Constraints

  • Batch scoring runs every 6 hours for ~9,000 active machines
  • Predictions must be explainable to reliability engineers
  • False negatives are costly, but excessive false positives create unnecessary maintenance work
  • Retraining should be feasible on a monthly cadence

Deliverables

  1. Build a binary classification pipeline for failure prediction within 7 days.
  2. Explain feature engineering, leakage prevention, and validation strategy.
  3. Compare at least one baseline model against a stronger tree-based model.
  4. Choose an operating threshold based on maintenance capacity and failure recall.
  5. Report final test metrics and the most important features.