PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/Machine Learning/Twitch

Design real-time live-stream recommendations

Last updated: Mar 29, 2026

Quick Overview

This question evaluates competency in designing real-time recommender systems within the Machine Learning domain, covering objectives and label construction for streaming events, feature engineering across user/creator/stream/context, model and loss choices, bias mitigation, evaluation metrics, and low-latency serving and freshness constraints.

  • hard
  • Twitch
  • Machine Learning
  • Data Scientist

Design real-time live-stream recommendations

Company: Twitch

Role: Data Scientist

Category: Machine Learning

Difficulty: hard

Interview Round: Technical Screen

Design a real-time recommendation system for live streams. Address the following: 1) Objective and labels: Define your primary objective (e.g., maximize post-click 10-minute watch probability) and construct training labels from view_events, including delayed outcomes and censoring when streams end. 2) Features: List user, creator, stream, and context features; handle cold-start for new creators and users. Explain how you’d incorporate short-term session signals and long-term embeddings. 3) Model and loss: Choose a model family (e.g., two-tower retrieval + re-ranker with calibrated probabilities). Specify the loss, negative sampling strategy (in-batch + hard negatives), and how you’d address severe class imbalance. 4) Feedback loops and bias: Mitigate position bias and popularity bias via counterfactual estimation (IPS/DR) or randomized exploration. Describe your exploration policy (e.g., Thompson Sampling or UCB) and safety constraints. 5) Evaluation: Define offline metrics (AUC, PR-AUC, calibration, NDCG@k) and online metrics (watch_time/viewer, session_length, bounce_rate). Explain reliable offline→online correlation using replay evaluation and interleaving. 6) Serving: Provide an end-to-end latency budget (<100 ms p95) including retrieval, feature fetch, and ranking. Describe feature freshness (streamer going live) and how you update embeddings in near-real time.

Quick Answer: This question evaluates competency in designing real-time recommender systems within the Machine Learning domain, covering objectives and label construction for streaming events, feature engineering across user/creator/stream/context, model and loss choices, bias mitigation, evaluation metrics, and low-latency serving and freshness constraints.

Twitch logo
Twitch
Oct 13, 2025, 9:49 PM
Data Scientist
Technical Screen
Machine Learning
3
0

Design a Real-Time Recommendation System for Live Streams

Context: You are designing a recommender for a large live-streaming platform. Assume you have standard logs: impressions, clicks, view_events with join/leave timestamps, and stream metadata. Address the following:

  1. Objective and Labels
  • Define your primary objective (e.g., maximize post-click 10-minute watch probability).
  • Construct training labels from view_events, including how to handle delayed outcomes and right-censoring when a stream ends before the label horizon.
  1. Features
  • List user, creator, stream, and context features.
  • Explain cold-start handling for new creators and new users.
  • Describe how you would incorporate short-term session signals and long-term embeddings.
  1. Model and Loss
  • Choose a model family (e.g., two-tower retrieval + re-ranker with calibrated probabilities).
  • Specify the loss function(s), negative sampling strategy (in-batch + hard negatives), and how to address severe class imbalance.
  1. Feedback Loops and Bias
  • Mitigate position bias and popularity bias using counterfactual estimation (IPS/DR) or randomized exploration.
  • Describe your exploration policy (e.g., Thompson Sampling or UCB) and safety constraints.
  1. Evaluation
  • Define offline metrics (AUC, PR-AUC, calibration, NDCG@k) and online metrics (watch_time/viewer, session_length, bounce_rate).
  • Explain how to establish reliable offline-to-online correlation using replay evaluation and interleaving.
  1. Serving and Freshness
  • Provide an end-to-end latency budget (<100 ms p95) including retrieval, feature fetch, and ranking.
  • Describe feature freshness (e.g., streamer going live) and how you update embeddings in near real time.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More Machine Learning•More Twitch•More Data Scientist•Twitch Data Scientist•Twitch Machine Learning•Data Scientist Machine Learning
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.