##### Question Design a coding platform (e.g., LeetCode) that supports problem execution at scale and provides a live global leaderboard; address test-case storage, execution orchestration, message-queue fault tolerance, and scalability considerations.

This question evaluates system design and distributed-systems skills, including scalable execution orchestration, secure sandboxing of untrusted code, test-case storage/distribution, message-queue resilience, and low-latency real-time leaderboard updates.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Onsite rounds at Meta.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Meta during technical interviews.

Design coding platform leaderboard system

System Design: Scalable Coding Platform with Live Global Leaderboard

Context

Design a coding challenge platform (similar to LeetCode) where users submit code to be compiled and executed against test cases at scale. The system must provide a live global leaderboard that updates in near real time.

Assume:

Millions of users, with peak submission bursts (e.g., during contests).
Multiple languages/runtimes (e.g., Python, Java, C++), each with time/memory limits.
Hidden and public test cases; hidden cases must never be leaked to clients.
Fairness and isolation: untrusted user code must run in sandboxed environments.

Requirements

Design the system to address:

Test-case storage and distribution to executors.
Execution orchestration (compile, run, shard across test cases, aggregate results).
Message-queue fault tolerance (retries, idempotency, DLQs, ordering where needed).
Scalability and elasticity across services.
Live global leaderboard with low-latency updates.

Call out key APIs, data models, high-level architecture, and operational considerations.

Context

Assume:

Millions of users, with peak submission bursts (e.g., during contests).

Multiple languages/runtimes (e.g., Python, Java, C++), each with time/memory limits.

Hidden and public test cases; hidden cases must never be leaked to clients.

Fairness and isolation: untrusted user code must run in sandboxed environments.

Requirements

Design the system to address:

Test-case storage and distribution to executors.

Execution orchestration (compile, run, shard across test cases, aggregate results).

Message-queue fault tolerance (retries, idempotency, DLQs, ordering where needed).

Scalability and elasticity across services.

Live global leaderboard with low-latency updates.

Call out key APIs, data models, high-level architecture, and operational considerations.

Design coding platform leaderboard system

Quick Overview

System Design: Scalable Coding Platform with Live Global Leaderboard

Context

Requirements

Solution

Comments (0)

Design coding platform leaderboard system

Quick Overview

System Design: Scalable Coding Platform with Live Global Leaderboard

Context

Requirements

Solution

Comments (0)