Design a File Converter

File conversion service inspired by CloudConvert and Smallpdf: uploads go to object storage, conversion jobs run on workers from a queue, and results are downloaded from the edge.

Functional requirements

  • Upload a file (up to 100 MB) and choose the output format; large files go straight to object storage
  • Convert the file in the background using workers that pick jobs from a queue
  • Show the job's status (queued, converting, done, failed) and let the user download the result when done
  • Retry a failed conversion automatically, and show a clear error if the file cannot be converted
  • Delete both the source and the result 24 hours after the job completes
  • Limit how many uploads one user or IP can start per minute, to protect the workers

Non-functional requirements

  • Upload accepted < 500ms p99 for the request itself (the file transfer goes to storage directly)
  • Status check < 100ms p99, served from the status cache; 10K status checks and downloads per second at peak
  • A small file (under 5 MB) converts within 30 seconds of upload
  • 99.9% of jobs finish successfully; failed jobs retry up to 3 times with backoff before being marked failed
  • Workers scale with queue depth, so a burst of 200 uploads per second waits instead of failing
  • Results are served from the CDN; nothing is kept longer than 24 hours, so storage cost stays flat
  • 99.9% availability for upload and status

How the design evolves

Stage 1: Convert While the User Waits

See why converting inside the request and storing files in the database does not scale.

What was missing: A conversion should not run inside the request, and files should not live in database rows.

Why that's risky: A heavy conversion occupies a worker thread for seconds, and a handful of large files blocks every other request.

What gets added: One server that receives each upload, converts it while the user waits and keeps the result in the database.

Trade-offs: Simple, but cannot grow.

Stage 2: Object Storage and Separate Services

Keep file bytes in object storage and split uploading from checking.

What was missing: File bytes sit in the database and conversion runs in the request.

Why that's risky: Every status check still hits the job database.

What gets added: File bytes move to object storage and a job database keeps each job's owner, format, status and file location, with separate upload and status services.

Trade-offs: Two stores to keep in sync: store the file first, then write the job.

Stage 3: CDN and Status Cache

Serve downloads from the edge and status from memory.

What was missing: Every status check and download reached storage.

Why that's risky: A cached status can show 'pending' for a moment after a job finishes.

What gets added: A cache for job status, which is what clients poll most, and a CDN that serves converted files through short-lived signed links.

Trade-offs: Status may lag by a second or two, which is fine because users poll.

Stage 4: Conversion Workers, Limits and Monitoring

Run conversions in the background and protect uploads.

What was missing: Conversions ran in the request and nothing limited uploads.

Why that's risky: Uploaded files are untrusted input: a malformed file can crash or hang a converter, so each job runs isolated with a time limit.

What gets added: A conversion queue with workers that read the original, convert it and save the result, an upload rate limiter and monitoring.

Trade-offs: Results arrive after conversion finishes, not instantly; the user polls or gets a notification.

PRISM
System Design Interview
Round 1 of 4 · Architecture Design · 60:00 remaining
PRISM logo PRISM logo
Problems
AI Interview
Interview Challenges
Build & Stress Test NEW
System Architectures
Design & Fix NEW
Interactive Roadmap
Problems
Today's mission
Notifications
    Theme
    Pricing Community NEW Send feedback Report a problem NEW
    Sign in
    Theme
    Community NEW Send feedback Report a problem NEW
    All problems
    Phase
    Build & Stress Test
    Phase 01: Thinking in Systems
    Upcoming

    Components

    User
    CDN
    Load Balancer
    Server
    Cache
    Database
    Blob Storage
    Search Index
    Queue
    Worker
    Rate Limiter
    Service
    API Gateway
    Reverse Proxy
    WebSocket Server
    Third-party API

    Inspector

    Notes
    Use clear names so your design intent is easy to understand.
    Good
    Name by business meaning
    "Order API", "Restaurant Service"
    Avoid
    Generic names = zero signal
    "Server 1", "API", "Queue"
    A short description for each component makes feedback much better.
    100%
    Start by identifying:
    • Users & entry points
    • APIs & services
    • Databases & storage
    • Traffic flow & scale

    Round 1 of 4 Architecture Design

    Run a simulation to see results.

    Time Remaining
    60:00
    System Design Interview

    What are the core functional requirements?
    What are the key non-functional constraints?

    Questions

    Start Evaluation to unlock questions.

    Test yourself like it's the real thing.

    Interview prep guide
    Architecture Design
    Draw your system on the canvas. Define components, connections, and data flow.
    FR & NFR Requirements
    Answer functional and non-functional requirement questions about your design.
    MCQ Round
    Multiple choice questions testing your depth on the chosen system.
    Tradeoff Analysis
    Justify your design decisions and defend your architectural tradeoffs.
    AI interviews left 0left
    This week 0 / 0
    Used today 0 / 0

    Choose a Problem
    No problem selected
    • 30 min
    • 45 min
    • 60 min
    Round 2 of 4
    MCQ Round
    Answer multiple-choice questions based on your design.

    Exit Interview?

    You're in the middle of an interview session. Leaving now will end your current attempt.

    Your progress will be saved.

    Open a saved design

    Select a design to load into the canvas.

    My Evaluations

    Your past evaluation sessions

    Here’s a simple request flow that follows the expected layer order.

    External User
    →
    Edge CDN → API Gateway → Load Balancer
    →
    Compute App Servers / Services
    →
    DataAccess Cache
    →
    Storage Database / Search Index
    →
    Async Queue → Worker

    Tip: keep arrows moving forward through layers (Edge → Compute → Storage). Avoid sending storage back to compute.

    Evaluation Instructions

    Read the rules carefully before starting. The test auto-submits on refresh.

    Before you start

    • Build your architecture on the canvas. The timer starts when you click Start Evaluation.
    • Don't forget to answer Functional Requirement and Non Functional Requirements.
    • When satisfied with your design, click Next to lock it and view the questions.
    • Please answer final step questions to complete the evaluation.

    Dos

    • Do read each question carefully before answering.
    • Do include required components to maximize component coverage.
    • Do save a copy of your design if you want to keep it before submission.

    Don'ts

    • Don't refresh or close the tab during an active evaluation — this will auto-submit your answers.
    • Don't switch app modes or open another tab while the evaluation is running.
    • Don't attempt to edit the design after clicking Next; the workspace will be locked.

    All the best!!

    Confirm

    Input

    Notice

    Evaluation Report
    Report a problem

    Evaluation Complete

    Generating Your Report

    Hang tight — our AI is evaluating your design…

    Did you know?

    Loading…

    Share feedback

    Tell us what worked well and what we can improve.

    Let's personalize this

    Answer a couple of quick questions so we can tailor your journey and missions.

    Your welcome gift: of Full PRISM Access

    Your Pro access starts as soon as you press Start my journey.

    SYSTEM BRIEF

    System Constraints

    What the system must do — every item is a user-facing behaviour your architecture must support.

      ↑ Engineering Constraints

      These are the failure modes you must design against — latency SLAs, durability targets, traffic ceilings.

        ⇆ Architecture Constraints

        Core Concepts to Master

        Your Journey
        PHASE – –
        0 / 0 0%
        0
        Mock Interview Checklist

        Pick a topic to start

        Explore concept overviews, real-system examples, key tradeoffs, and interview talking points for each roadmap section.

        Phase Mastered

        You've conquered this phase. These are the skills you now own:

          +500 XP

          Company Interview Paths

          Progress Summary