ScaleCrafts

Design a distributed job scheduler

Run millions of one-off and recurring jobs at the right time across a fleet of workers, like a distributed cron.

Functional requirements

  • Schedule a job to run once or on a cron schedule
  • Retry failed jobs
  • See job status and history

Non-functional requirements

  • Jobs start within a few seconds of their time
  • Each run happens once, even when machines fail
  • Scales to millions of jobs

Scale

  • 10M scheduled jobs
  • 50K job runs per minute at peak
  • Runs last from seconds to hours

How you’ll be scored

9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works

What interviewers look for

  • Clarify before you draw. State what is in and out of scope. For “Design a distributed job scheduler”, that starts with: Schedule a job to run once or on a cron schedule; Retry failed jobs; See job status and history. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (10M scheduled jobs; 50K job runs per minute at peak; Runs last from seconds to hours) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
  • Show how each quality is met. Your design should visibly deliver: Jobs start within a few seconds of their time; Each run happens once, even when machines fail; Scales to millions of jobs. Saying that it does isn’t enough; point to the part of the design that makes it true.
  • Expect follow-ups on the hard parts. Interviewers usually probe scheduling, queues and reliability here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
  • Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.

Related problems

Loading your workspace…