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 Telecom Churn with Gradient Boosting

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

Your question is Predict Telecom Churn with Gradient Boosting. 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

NovaTel, a regional telecom provider with 2.3M subscribers, wants to predict which customers will churn in the next 30 days so the retention team can target save offers efficiently. The model will be scored weekly and used to prioritize outreach for the top-risk customers.

Dataset

You are given a customer-level training dataset built from the last 18 months of subscriber history.

Feature GroupCountExamples
Usage14avg_call_minutes_30d, data_gb_30d, dropped_calls_rate, roaming_days
Billing9monthly_charge, payment_method, late_payments_90d, autopay_enabled
Contract6plan_type, tenure_months, contract_term, add_on_count
Support7support_tickets_90d, complaint_flag, avg_resolution_hours
Engagement6app_logins_30d, web_portal_visits, promo_clicks
Geography / Demographics5region, device_type, acquisition_channel
  • Historical table contains one row per customer per month.
  • The modeling snapshot has 240K customer-months and 47 features.
  • Target is whether the customer churns within the next 30 days.
  • Churn is relatively rare and missing values are present in support and engagement fields.

Success Criteria

A good solution should achieve strong ranking quality and be usable by an operations team with limited outreach capacity. Target performance is:

  • Recall >= 75% at precision >= 40% for the intervention threshold
  • ROC-AUC >= 0.84
  • Clear feature importance or reason codes for flagged customers

Constraints

  • Weekly batch inference on ~2.3M customers must finish in under 30 minutes.
  • The retention team can contact only the top 8-10% highest-risk customers.
  • The solution should be explainable enough for business stakeholders and compliant with standard customer analytics governance.

Deliverables

  1. Build a churn prediction pipeline with preprocessing, training, and evaluation.
  2. Explain model choice, leakage risks, and validation strategy.
  3. Show how you would handle class imbalance and missing data.
  4. Propose thresholding logic for retention outreach capacity.
  5. Provide feature importance and monitoring recommendations for production.