← AppLovin Interview Insights

AppLovin·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Jun 2026

Summary

System design round at Applovin for a software engineer role. One question, video storage at scale, pretty much the whole session.

Questions Asked (1)

Q1

Design a system for storing and serving videos at scale, similar to YouTube.

System DesignTechnical Trade-offsData Modeling
Author's notes

This is the kind of question where you think you know what to say and then realize mid-sentence you have no idea how transcoding actually works at scale.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale (e.g., daily uploads, views, storage). Then design a high-level architecture covering upload, storage, transcoding, and delivery, and dive into key components like CDN, database sharding, and caching. Discuss trade-offs and bottlenecks, and iterate based on feedback.

Pro tip: Focus on the unique challenges of video (large files, transcoding, adaptive bitrate streaming) and how they influence design decisions. Show awareness of cost and operational complexity, and propose pragmatic solutions rather than over-engineering.

1. Clarify Requirements and Scale

Ask questions to understand expected scale (e.g., daily uploads, concurrent viewers, storage growth), functional requirements (upload, view, search, recommendations), and non-functional requirements (latency, availability, durability).

2. High-Level Architecture

Outline the main components: upload service, transcoding pipeline, storage (object store + CDN), metadata database, and serving layer. Explain how they interact.

3. Deep Dive into Key Components

Detail the design of critical parts: how to handle large uploads (resumable, chunked), transcoding (parallel, format conversion), storage (tiered, replication), and delivery (CDN, adaptive streaming).

4. Data Modeling and Metadata

Design the schema for video metadata (title, description, tags, user, etc.) and how to store and query it efficiently at scale (e.g., sharding, NoSQL vs SQL).

5. Trade-offs and Bottlenecks

Discuss trade-offs (e.g., consistency vs availability, cost vs performance) and identify potential bottlenecks (e.g., transcoding queue, database hotspots) and mitigation strategies.

Key Points to Mention

  • Use of CDN for global video delivery and caching
  • Transcoding pipeline with parallel processing and multiple formats/resolutions
  • Storage tiering (hot vs cold) and object storage like S3
  • Database sharding and replication for metadata
  • Adaptive bitrate streaming (HLS/DASH) for smooth playback
  • Handling large file uploads with resumable/chunked uploads

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