InterviewLegend

Design a Job Scheduler

Frequently asked
Alex Chen45 min readAdded 106 real interview reports

A job scheduler takes "run this at that time" from many callers and makes it happen. It stores each job, notices when one is due, hands it to a worker, and records how the run went. Most of the difficulty sits in the gaps between those steps, when a scheduler or a worker dies with a job half done. At Postman this prompt comes up under a few names: a task scheduler, a job executor service, a scheduling service. It's been reported in SDE-2, SDE-3 and Senior loops from 2024 into 2026. In most reports it fills the whole HLD (high-level design) round. Once it came up inside a broader backend discussion, with a deep dive on indexing and sharding.

The Postman angle
Postman ships scheduled jobs as a product. Monitors and scheduled collection runs fire API requests on a timer and alert someone on failure. Frame your jobs the same way. The payload is an HTTP request with a timeout, the result is a status code and a duration, and failures reach a person through the notification system.

PostmanPremium lesson · System design round

The Postman design, worked end to end.

  1. The API and data modelSystem design · Frequently asked
  2. The design, drawn out2 diagrams
  3. 5 deep divesWith the tradeoffs
Get the Postman questions

$49 a year · all 107 companies · instant access

106 Postman interview reports · guide updated

Postman interview guide

Know what Postman asks before you walk in.

10 coding · 4 system design · 27 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Had your Postman interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.