ScaleCrafts

Design an online coding judge

MediumSandboxingQueuesContests

Let users solve coding problems, submit code in many languages and get it graded against test cases, like LeetCode.

Functional requirements

  • Browse problems and submit solutions
  • Run code against hidden test cases
  • Live contests with a leaderboard

Non-functional requirements

  • User code can’t harm the system
  • Results within 5 seconds normally
  • Contests handle 100K concurrent users

Scale

  • 5M users
  • 1M submissions per day
  • Contest peaks of 5K submissions per second

How you’ll be scored

11 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 an online coding judge”, that starts with: Browse problems and submit solutions; Run code against hidden test cases; Live contests with a leaderboard. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (5M users; 1M submissions per day; Contest peaks of 5K submissions per second) 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: User code can’t harm the system; Results within 5 seconds normally; Contests handle 100K concurrent users. 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 sandboxing, queues and contests 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…