Design a Task Scheduling Service

Last updated: August 9, 2025

Quick Overview

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

Notion
System Design
Software Engineer
Notion
August 9, 2025
Software Engineer
Technical Screen
System Design
Hard

94

14

420 solved


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

System design interviews at Notion typically last 45-60 minutes. You are expected to drive the conversation, starting from requirements gathering through to a detailed architecture. The interviewer will evaluate your ability to handle ambiguity and make practical engineering decisions.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
Message queues and async processing
Caching strategies (local, distributed, CDN)
Load balancing and horizontal scaling
Requirements gathering and capacity estimation
Failure handling and fault tolerance
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 migrate from a monolithic to a microservices architecture?
  • How do you ensure data consistency across multiple services?
  • How would you handle schema migrations with zero downtime?
  • How would you implement rate limiting to protect the system?
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

  1. Task Creation: Users can create tasks with details like title, description, due date, priority, and associated tags.
  2. Task Scheduling: Users can schedule tasks...
Capacity Estimation

To estimate capacity, we consider Notion's user base and expected growth:

  • User Base: Assume there are 10 million active users.
  • Requests per User: Each user makes an average of 10 requests...

Submit Your Answer
Markdown supported

Related Questions