HLD prep is optimised for larger screens
Open on a laptop or desktop (1024px+) for the diagram canvas and the section sidebar side-by-side.
Problem Understanding
Restate the problem in your own words.
Design a Distributed Job Scheduler
Design a distributed job scheduler: applications submit cron-like (or one-shot) jobs with retry policies and SLAs; the scheduler picks them up, dispatches to a pool of workers, tracks attempts, surfaces failures. The hard parts are exactly-once dispatch under worker failure (idempotency keys), preventing the scheduler itself from being the bottleneck (sharded by job id), and graceful priority-queueing for SLA-critical tasks.
- Apache AirflowDAG-based job scheduler used widely for data pipelines; rich dependency graphs.
- Kubernetes CronJobsContainer-native cron — the simplest periodic-job answer in modern stacks.
- AWS Step FunctionsManaged orchestrator for workflows; built-in retry + state, billed per state transition.
- TemporalDurable workflow engine — job + workflow + saga in one. Adopted heavily for backend orchestration.
Your task: read the problem above, then write what the system is, who uses it, the rough scale, and the headline UX expectation — in your own words. Submit for AI review when you're ready.
Click any step in the sidebar to jump around — sections don't have to be done in order. Press ? any time to see all shortcuts.