Design a Distributed Job Scheduler
The newest Visa version came up in March 2026, in a Staff candidate's first technical round. The interviewer asked for a distributed scheduler and said a working solution wasn't expected. Pseudocode and the approach were the deliverable. The same round then moved on to a few scenario questions about cutting cache latency and updating feature flags. Two older versions show where follow-ups can go. A 2025 Senior Data Engineer round in Foster City asked for a scheduler and named caching and sharding as the concepts to cover. A 2022 Staff round in Bengaluru asked for a multi-tenant job scheduler, then asked the candidate to explain the command design pattern.
The idea sounds small. Cron on one machine already runs jobs on time. The trouble starts when that machine reboots a minute before midnight and the midnight jobs never fire, or when you add a second machine for safety and every job fires twice. A distributed scheduler is mostly an answer to those two failures, zero runs and two runs, at a scale where neither can be fixed by hand.
VisaPremium lesson · System design round
The Visa design, worked end to end.
- Requirements and scopeSystem design
- The API and data model
- The design, drawn out1 diagram
- 6 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports
Visa interview guideKnow what Visa asks before you walk in.
30 coding · 8 system design · 20 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.