PracHub
QuestionsPremiumLearningGuidesCheatsheetNEWCoaches
|Home/System Design/Apple

Design video platform and catalog system

Last updated: Mar 29, 2026

Quick Overview

This System Design question evaluates proficiency in large-scale architecture, API and storage design, data modeling, scalability and consistency trade-offs, ingestion and indexing pipelines, CDN and caching strategies, and operational concerns such as reliability, observability, security, and multi-region deployments across video-sharing and marketplace catalog domains. It is commonly asked in technical interviews to test architectural judgment and trade-off reasoning, emphasizing high-level practical application and operational planning rather than low-level implementation details.

  • hard
  • Apple
  • System Design
  • Software Engineer

Design video platform and catalog system

Company: Apple

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

Design two systems. For each, define scope, APIs, storage choices, scalability strategy, consistency model, and reliability/observability plans: 1) Video sharing platform: A YouTube-like service supporting video upload, transcoding to multiple bitrates, storage tiering, CDN delivery, metadata and search, user actions (watch, like/comment), and a recommendations interface. Estimate traffic/storage, design the ingestion pipeline, thumbnail generation, indexing, caching, and rate limiting; discuss multi-region availability, encryption/DRM, and cost trade-offs. 2) Catalog system: A large marketplace catalog modeling categories, attributes, and product variants; support item ingestion, versioning, deduplication, and moderation; design services for search/browse indexing, localization, and incremental updates; outline read/write APIs, caching, and consistency between source of truth (SQL/NoSQL) and the search index; address schema evolution, multi-tenant isolation, and backfill/reprocessing strategies.

Quick Answer: This System Design question evaluates proficiency in large-scale architecture, API and storage design, data modeling, scalability and consistency trade-offs, ingestion and indexing pipelines, CDN and caching strategies, and operational concerns such as reliability, observability, security, and multi-region deployments across video-sharing and marketplace catalog domains. It is commonly asked in technical interviews to test architectural judgment and trade-off reasoning, emphasizing high-level practical application and operational planning rather than low-level implementation details.

Related Interview Questions

  • Design a smartwatch sensor subsystem - Apple (hard)
  • Design CI/CD for AI Services - Apple (medium)
  • Design TikTok Data Engineering Systems - Apple (medium)
  • Design ad click aggregator and file sync service - Apple (medium)
  • Design an Accurate Click Aggregator - Apple (medium)
Apple logo
Apple
Sep 6, 2025, 12:00 AM
Software Engineer
Onsite
System Design
4
0

System Design: Two Independent Systems

You are asked to design two large-scale systems. For each system, provide:

  • Scope and key requirements
  • External APIs (read/write) and internal service interfaces
  • Storage choices and data modeling
  • Scalability strategy and high-level architecture
  • Consistency model and data flow
  • Reliability, availability, and observability plans

Where relevant, estimate traffic/storage, and discuss cost and security trade-offs.

1) Video Sharing Platform (YouTube-like)

Requirements:

  • Video upload, validation, and asynchronous transcoding into multiple bitrates and codecs
  • Storage tiering (hot/warm/cold), CDN delivery with adaptive streaming (HLS/DASH)
  • Metadata and search, user actions (watch, like, comment)
  • Recommendations interface (feature and event APIs to interact with a separate recs system)
  • Estimate traffic/storage; design ingestion pipeline, thumbnail generation, indexing
  • Caching (metadata, watch pages), rate limiting and abuse controls
  • Multi-region availability, encryption/DRM, and cost trade-offs

Deliver:

  • Architecture, APIs, queues, storage choices
  • Consistency choices for user actions and metadata vs search
  • Scalability strategy for upload, transcode, playback, and indexing
  • Reliability and observability plan

2) Marketplace Catalog System

Requirements:

  • Large catalog with categories, attributes, products, and product variants (SKUs)
  • Item ingestion (batch/stream), versioning, deduplication, and moderation workflows
  • Services for search/browse indexing with localization and incremental updates
  • Read/write APIs, caching, and consistency model between the source of truth (SQL/NoSQL) and the search index
  • Address schema evolution, multi-tenant isolation, and backfill/reprocessing strategies

Deliver:

  • Domain model and storage choices
  • Ingestion and moderation flows
  • Indexing pipeline and cache strategy
  • Consistency, availability, and observability plans

Solution

Show

Comments (0)

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Apple•More Software Engineer•Apple Software Engineer•Apple System Design•Software Engineer System Design
PracHub

Master your tech interviews with 7,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.