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 Live-Service Game Retention

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

Your question is Predict Live-Service Game Retention. 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

NovaForge Studios operates a live-service mobile RPG with 8M monthly active players. The growth team wants a model that predicts whether a new player will still be active on day 7 so they can trigger CRM campaigns, in-game offers, and onboarding interventions.

Dataset

The training data is built at the player-install level using behavior from the first 48 hours after install. The label is whether the player is retained on day 7.

Feature GroupCountExamples
Session behavior14session_count_48h, total_minutes_48h, avg_session_length, last_session_gap_hours
Progression10levels_completed, tutorial_completion_pct, deaths_per_level, quest_completion_rate
Economy & monetization8soft_currency_earned, hard_currency_spent, first_purchase_flag, ad_views
Social & engagement6guild_joined, friends_added, chat_messages, push_opt_in
Device & acquisition7platform, country_tier, install_source, device_ram_gb
Temporal features5install_hour_local, weekend_install, day1_day2_play_delta, recency_hours
  • Size: 1.2M player installs over 6 months, 50 features
  • Target: Binary — retained on day 7 (1) vs not retained (0)
  • Class balance: 28% retained, 72% churned before day 7
  • Missing data: ~12% missing in acquisition metadata, ~6% missing in device specs, sparse missingness in social features for players who never unlocked them

Success Criteria

A good solution should achieve strong ranking quality for intervention targeting, with ROC-AUC >= 0.82, PR-AUC >= 0.58, and top-decile lift >= 2.2 on a strictly future holdout set.

Constraints

  • Predictions must be generated in a daily batch for up to 500K new installs
  • Marketing and game design need feature-level explanations for why players are flagged
  • The model should be robust to changing acquisition mix and live-ops events
  • Retraining budget supports weekly retraining, not continuous online learning

Deliverables

  1. Define the target and leakage-safe feature window
  2. Build and justify a retention prediction model
  3. Describe preprocessing and feature engineering choices
  4. Evaluate the model with business-relevant metrics and thresholding
  5. Explain how you would deploy, monitor, and retrain the model