← Disney Interview Insights

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

SeniorPrefer not to say
Apr 2026

Summary

Disney system design round for a software engineer role, basically one big question about building a Twitter-scale platform from scratch. Dense topic, lots of ground to cover, and I definitely didn't get to all of it.

Questions Asked (1)

Q1

Design a Twitter-like social platform covering data modeling, core user interactions, feed generation, storage architecture, search and trending, and how you'd scale it to hundreds of millions of users.

System DesignData ModelingTechnical Trade-offs
Author's notes

This is basically a full system design gauntlet in one question.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale (e.g., 500M users, read-heavy, eventual consistency acceptable). Then walk through a high-level design covering data modeling, core interactions, feed generation, storage, search/trending, and scaling, making trade-offs explicit at each step. Conclude by summarizing how components work together and potential bottlenecks.

Pro tip: Emphasize the read-heavy nature and propose a hybrid feed approach: push (fan-out on write) for active users and pull (fan-out on read) for celebrities, showing you understand the trade-off between latency and cost. Also, mention how Disney's need for real-time engagement (e.g., live events) might influence design choices like trending algorithms.

1. Clarify Requirements and Scale

Ask questions to understand functional and non-functional requirements: user base size, read/write ratio, latency, consistency, and features like tweets, follows, timeline, search, and trending. Establish scale targets (e.g., 500M users, 500M tweets/day).

2. Data Modeling and Storage

Design schemas for users, tweets, follows, and likes. Choose appropriate storage: SQL for user data (ACID), NoSQL (e.g., Cassandra) for tweets and timelines (high write throughput), and graph DB for social graph. Discuss sharding and replication.

3. Core Interactions and Feed Generation

Detail posting tweets, following, and timeline retrieval. Explain feed generation: fan-out on write for most users, fan-out on read for celebrities, using a hybrid approach. Discuss caching (Redis) for timelines and tweet objects.

4. Search and Trending

Describe indexing tweets for search (e.g., Elasticsearch) and computing trends using streaming analytics (e.g., Apache Storm, Flink) with sliding windows. Discuss ranking and personalization.

5. Scaling and Trade-offs

Explain horizontal scaling, partitioning, CDN for media, and load balancing. Discuss consistency vs. availability (CAP theorem) and latency vs. cost. Address bottlenecks like hotkeys and celebrity problem.

Key Points to Mention

  • Hybrid feed generation (push vs. pull) to handle celebrities and reduce latency.
  • Sharding strategies for tweets and timelines (e.g., by user ID or tweet ID).
  • Use of caching (Redis/Memcached) for hot data like timelines and tweet objects.
  • Search indexing with Elasticsearch and real-time trending with stream processing.
  • Trade-offs: consistency vs. availability, latency vs. cost, and storage choices (SQL vs. NoSQL).
  • Scalability techniques: horizontal scaling, partitioning, replication, and CDN for media.

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