← Whatnot Interview InsightsSoftware Engineer

Whatnot·Software Engineer·Onsite - System Design / Architecture·Intermediate

IntermediatePrefer not to say
May 2026

Summary

System design round at Whatnot for a software engineer role. Just one question, but it was a meaty one.

Questions Asked (1)

Q1

Design a platform like LeetCode from scratch.

System DesignTechnical Trade-offsData Modeling
Author's notes

This is one of those questions that sounds scoped but really isn't.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying functional and non-functional requirements, then design the core components: problem repository, code execution engine, submission and evaluation pipeline, and user progress tracking. Focus on scalability, security, and real-time feedback, and discuss trade-offs between different architectural choices.

Pro tip: Emphasize the importance of sandboxing and resource isolation for running untrusted code, as this is a critical and often overlooked aspect. Also, discuss how to handle peak loads during contests with horizontal scaling and queue-based processing.

1. Clarify Requirements

Ask questions to understand the scope: expected number of users, types of problems (algorithmic, database, etc.), supported languages, and whether real-time collaboration or contests are needed.

2. High-Level Architecture

Outline the main components: web/app servers, database, code execution service, message queue, and caching layer. Draw a simple diagram showing how they interact.

3. Deep Dive into Key Components

Detail the code execution engine: how to securely run untrusted code in isolated containers, manage resource limits, and scale horizontally. Discuss the submission pipeline: queuing, scheduling, and result aggregation.

4. Data Modeling and Storage

Design schemas for problems, test cases, submissions, and user progress. Choose appropriate databases (e.g., relational for user data, object storage for test cases) and discuss indexing and sharding strategies.

5. Scalability and Trade-offs

Address scaling: caching, CDN for static assets, read replicas, and partitioning. Discuss trade-offs between consistency and availability, and between using VMs vs. containers for code execution.

Key Points to Mention

  • Security and isolation for code execution (e.g., Docker, gVisor, seccomp).
  • Scalable and fault-tolerant submission processing using message queues (e.g., Kafka, RabbitMQ).
  • Efficient storage and retrieval of test cases and problem statements (e.g., S3, CDN).
  • Real-time feedback and leaderboard updates during contests (e.g., WebSockets, Redis).
  • Data modeling for problems, submissions, and user progress with appropriate database choices.
  • Monitoring, logging, and alerting for system health and abuse detection.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.