Design a real-time game recommendation system

Quick Overview

Design a real-time game recommendation system evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Design a real-time game recommendation system

Company: Roblox

Role: Machine Learning Engineer

Category: ML System Design

Difficulty: hard

Interview Round: Technical Screen

Design a real-time game recommendation system for a platform with millions of games and tens of millions of users. Focus on the system architecture, not ML model details. Describe: 1) end-to-end request flow and latency SLOs; 2) online/offline data ingestion (user events, game metadata) and schemas; 3) streaming feature computation and a real-time feature store; 4) candidate generation and ranking service interfaces; 5) caching strategy and freshness/TTL; 6) user personalization state and session handling; 7) scalability plans (QPS estimates, partitioning, replication, storage); 8) experimentation and rollout (A/B, feature flags); 9) cold-start strategies; 10) failure modes, consistency, and backfill/lag recovery; 11) privacy, security, and abuse prevention; 12) monitoring, alerting, and cost controls.

Overview: Design a real-time game recommendation system evaluates ML product requirements, data/labeling, modeling, serving architecture, evaluation, monitoring, and trade-offs in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

|Home/ML System Design/Roblox
Roblox logo
Roblox
Jul 16, 2025
hardMachine Learning EngineerTechnical ScreenML System Design
12
0

Design a real-time game recommendation system

System Design: Real‑Time Game Recommendation System (Architecture Focus)

You are designing a real‑time recommendation system for a large gaming platform with millions of games and tens of millions of users. The focus is on system architecture and operations, not the internals of ML models.

Requirements

Describe the following aspects clearly:

  1. End‑to‑end request flow and latency SLOs.
  2. Online/offline data ingestion (user events, game metadata) and schemas.
  3. Streaming feature computation and a real‑time feature store.
  4. Candidate generation and ranking service interfaces.
  5. Caching strategy and freshness/TTL.
  6. User personalization state and session handling.
  7. Scalability plans (QPS estimates, partitioning, replication, storage).
  8. Experimentation and rollout (A/B, feature flags).
  9. Cold‑start strategies.
  10. Failure modes, consistency, and backfill/lag recovery.
  11. Privacy, security, and abuse prevention.
  12. Monitoring, alerting, and cost controls.

Assume:

  • Tens of millions of MAU/DAU, mobile and desktop clients.
  • Real‑time freshness for recent interactions (sub‑second to low seconds).
  • Global user base with multi‑region traffic.
  • The ML models exist but their internals are out of scope; you must define their service contracts and integration points.

Clarifying Questions to Ask Guidance

  • Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
  • State explicit assumptions before making sizing or architecture decisions.
  • Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

  • A scoped requirements summary with concrete non-goals and success metrics.
  • ML-specific data, model, evaluation, serving, and monitoring choices.
  • Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
  • A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

  • What breaks first at 10x traffic or data volume?
  • How would you degrade gracefully during dependency failures?
  • What metrics and alerts would prove the design is healthy after launch?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...