Architect a low-latency Task Scheduling Engine

Last updated: December 28, 2025

Quick Overview

Design a low-latency task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Notion
System Design
Software Engineer
Notion
December 28, 2025
Software Engineer
System Design Round
System Design
Hard

8

5

1,914 solved


Design a low-latency task scheduling system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Notion asks this during the System Design Round to assess your understanding of the full ML lifecycle. They want to see how you translate a business problem into an ML objective, design the feature pipeline, and plan for model monitoring and retraining.

What the Interviewer Expects
  • Design the full ML lifecycle from data collection to model monitoring
  • Address cold start, exploration/exploitation, and model freshness
  • Discuss multi-objective optimization and ranking systems
  • Plan for model debugging, fairness, and bias mitigation
  • Design the feature store and training pipeline for scale
  • Address model versioning, canary deployments, and rollback strategies
  • Discuss the data flywheel and long-term system evolution
Key Topics to Cover
ML objective formulation and metric selection
Feedback loops and model retraining
Training pipeline and infrastructure
A/B testing and experimentation
Model serving and latency optimization
Monitoring and model degradation detection
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you ensure fairness and reduce bias in the model?
  • How would you debug a model that works well offline but poorly online?
  • How would you run A/B tests on different model versions?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements
  • Functional Requirements:
    • The system should support scheduling millions of tasks with low latency (sub-100ms).
    • Ability to prioritize tasks based on user-defined rules, urgency, and system...
Capacity Estimation

To estimate capacity:

  • Assume 10 million users, each making an average of 5 task scheduling requests per day.
  • Total requests per day = 10 million * 5 = 50 million.
  • If we assume a peak load ...

Submit Your Answer
Markdown supported

Related Questions