InterviewLegend

Design a Job Scheduler for CI/CD and Cron

Alex Chen32 min readGuide updated

Cursor has asked for a scheduler twice in 2026 software engineer technical screens. The August version is the CI/CD one above. The April version was a durable cron scheduler. Both share a core: work has to survive crashes, and a job that runs twice must do no harm. This lesson works the CI/CD version in full, then covers what changes for cron.

Picture a normal morning. A developer pushes a commit, and the Git host calls our webhook. That push becomes a pipeline: build first, then twelve test shards and a lint job in parallel, then a deploy that runs only if every test passed. Two thousand other teams are doing the same on one shared fleet of machines. Three things go wrong on a fleet like that. One team kicks off a 3,000-job release matrix and everyone queued behind it waits. A machine dies eight minutes into a ten-minute test shard. And the scheduler process itself restarts during a deploy. The design is mostly about those three moments. The happy path is short.

The Cursor angle
Cursor's screens run 45 to 60 minutes, paired with one engineer, and candidates say interviewers push on many details. Five deep dives won't fit. Get the job table, the ready rule and leases on the board in the first twenty minutes, then let the interviewer pick where to dig.

CursorPremium lesson · System design round

The Cursor design, worked end to end.

  1. Requirements and scopeSystem design
  2. The API and data model
  3. The design, drawn out1 diagram
  4. 5 deep divesWith the tradeoffs
Get the Cursor questions

$49 a year · all 107 companies · instant access

20,000+ candidate reports

Cursor interview guide

Know what Cursor asks before you walk in.

9 coding · 4 system design · 16 behavioral questions

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

Get their questions first.

Had your Cursor interview?How we research

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