# Twitter/X Interview Guide 2026: Timeline Algorithms, Real-Time Search, and Content at Scale

Source: https://www.techinterview.org/post/3233460305/twitter-x-interview-guide-2026-timeline-algorithms-real-time-search-and-content-at-scale/
Updated: 2026-06-30 · techinterview.org

## Twitter/X Interview Guide 2026: Timeline Algorithms, Real-Time Systems, and Content Moderation at Scale

Twitter/X has undergone massive changes since Elon Musk's acquisition in 2022, including significant headcount reduction (~80%) and a complete rebuild of many systems. The engineering team is now smaller and more focused on performance and monetization. This guide covers what to expect in SWE interviews at X (formerly Twitter) in 2026.

## The X/Twitter Interview Process (2026)

Post-acquisition, X's interview process is less formalized than traditional FAANG:

- **Recruiter/sourcing call** — often direct outreach from engineering managers

- **Technical screen** (1 hour) — coding + architecture discussion

- **Onsite** (3–4 rounds, compressed schedule):

 2× coding (medium-hard, emphasis on performance and scale)

 - 1× system design (timeline, search, or real-time messaging)

 - 1× engineering manager / culture fit

**Culture note**: X values "hardcore" engineers who can work long hours on hard problems. Interview culture expects demonstrated productivity and shipping mentality over process.

## Core Algorithms: Timeline and Feed

### Twitter's Open-Source Timeline Algorithm

Twitter open-sourced their recommendation algorithm in 2023. Key components:


```
from dataclasses import dataclass, field
from typing import List, Dict, Optional
import math

@dataclass
class Tweet:
 id: int
 author_id: int
 text: str
 timestamp: float
 like_count: int = 0
 retweet_count: int = 0
 reply_count: int = 0
 view_count: int = 0
 has_media: bool = False
 language: str = 'en'

@dataclass
class UserContext:
 user_id: int
 following_ids: List[int]
 interests: List[str]
 engagement_history: Dict[int, str] # tweet_id -> action

class TimelineRanker:
 """
 Simplified model of Twitter's timeline ranking.

 Real Twitter uses a two-stage system:
 1. Candidate generation: fetch 1500 candidates from:
 - In-network (following, followers-of-followers)
 - Out-of-network (trending, similar users, topics)
 2. Heavy ranker: ML model scoring each candidate
 3. Heuristic filters: dedupe, balance in/out-network, author diversity

 The ranking model uses ~48M parameter neural network with
 features covering user engagement history, tweet quality signals,
 author trust scores, and topic relevance.
 """

 def __init__(self):
 self.engagement_weights = {
 'like': 1.0,
 'retweet': 2.0,
 'reply': 3.0,
 'quote': 2.5,
 'profile_click': 0.5,
 'link_click': 1.5,
 }

 def score_tweet(
 self,
 tweet: Tweet,
 viewer: UserContext,
 current_time: float
 ) -> float:
 """
 Multi-factor tweet relevance score.
 """
 # 1. Social graph signal (is this from someone you follow?)
 social_score = 1.0 if tweet.author_id in viewer.following_ids else 0.3

 # 2. Engagement rate (quality signal)
 impressions = max(tweet.view_count, 1)
 engagement_rate = (
 tweet.like_count * 1.0 +
 tweet.retweet_count * 2.0 +
 tweet.reply_count * 3.0
 ) / impressions
 engagement_score = min(1.0, engagement_rate * 100)

 # 3. Recency decay (half-life = 2 hours for breaking news feel)
 age_hours = (current_time - tweet.timestamp) / 3600
 half_life = 2.0
 recency_score = math.exp(-age_hours * math.log(2) / half_life)

 # 4. Media boost (tweets with images/video get higher engagement)
 media_boost = 1.3 if tweet.has_media else 1.0

 # 5. User engagement history with author
 author_affinity = 1.5 if any(
 tweet_id for tweet_id in viewer.engagement_history
 # simplified: check if user has engaged with content from this author
 ) else 1.0

 return (
 social_score * 0.30 +
 engagement_score * 0.25 +
 recency_score * 0.25 +
 (media_boost - 1) * 0.10 +
 (author_affinity - 1) * 0.10
 )

 def generate_timeline(
 self,
 viewer: UserContext,
 candidate_tweets: List[Tweet],
 current_time: float,
 limit: int = 200
 ) -> List[Tweet]:
 """
 Score and rank all candidate tweets for viewer's timeline.

 Time: O(C * F) where C=candidates, F=features per tweet
 """
 scored = [
 (self.score_tweet(t, viewer, current_time), t)
 for t in candidate_tweets
 ]
 scored.sort(reverse=True)

 # Author diversity constraint: max 2 consecutive tweets per author
 result = []
 consecutive_by_author: Dict[int, int] = {}

 for score, tweet in scored:
 if len(result) >= limit:
 break
 count = consecutive_by_author.get(tweet.author_id, 0)
 if count < 2:
 result.append(tweet)
 consecutive_by_author[tweet.author_id] = count + 1
 else:
 consecutive_by_author[tweet.author_id] = 0 # reset after gap

 return result
```


### Distributed Rate Limiting at Twitter Scale


```
import time
from collections import defaultdict
from threading import Lock

class TokenBucketRateLimiter:
 """
 Token bucket algorithm for API rate limiting.
 Twitter API: 1500 requests per 15 minutes per app.

 Token bucket:
 - Bucket capacity = max_requests
 - Tokens refill at rate = max_requests / window_seconds
 - Each request consumes 1 token
 - If bucket empty: reject request

 Advantage over fixed window: allows short bursts up to capacity
 while maintaining average rate constraint.

 Twitter uses Redis for distributed token bucket across API servers.
 """

 def __init__(self, capacity: int, refill_rate: float):
 """
 capacity: max tokens (burst limit)
 refill_rate: tokens per second
 """
 self.capacity = capacity
 self.refill_rate = refill_rate
 self.buckets: Dict[str, Dict] = defaultdict(
 lambda: {'tokens': capacity, 'last_refill': time.time()}
 )
 self.lock = Lock()

 def allow_request(self, key: str, tokens_needed: int = 1) -> bool:
 """
 Check if request is allowed; consume tokens if so.
 Thread-safe via lock (use Redis EVAL script in distributed setting).

 Time: O(1)
 """
 with self.lock:
 bucket = self.buckets[key]
 now = time.time()

 # Refill tokens based on elapsed time
 elapsed = now - bucket['last_refill']
 new_tokens = elapsed * self.refill_rate
 bucket['tokens'] = min(self.capacity, bucket['tokens'] + new_tokens)
 bucket['last_refill'] = now

 if bucket['tokens'] >= tokens_needed:
 bucket['tokens'] -= tokens_needed
 return True
 return False

 def get_reset_time(self, key: str) -> float:
 """Seconds until bucket is full again."""
 with self.lock:
 bucket = self.buckets[key]
 deficit = self.capacity - bucket['tokens']
 return deficit / self.refill_rate if deficit > 0 else 0
```


## System Design: Twitter Search

Common X/Twitter question: *"Design Twitter's real-time search — results must appear within seconds of a tweet being posted."*


```
"""
Twitter Real-Time Search Architecture:

Tweet Posted
 |
[Ingestion Kafka Topic]
 |
[Real-Time Indexing Service]
 - Tokenizes tweet text
 - Extracts hashtags, mentions, entities
 - Writes to real-time index (Earlybird — Twitter's custom Lucene)
 - Earlybird: in-memory inverted index, TTL-based eviction (7 days)
 |
[Search Query Service]
 - Parse query (boolean operators, hashtag/mention filters)
 - Fan out to all Earlybird shards (by time range)
 - Merge and rank results
 - Apply safety filters (spam, NSFW)

Key design decisions:
1. In-memory index: tweets are ephemeral; no need for persistent indexing
2. Time-partitioned shards: each shard covers a time window
3. Top-K aggregation: each shard returns top-K; merge globally
4. Relevance signals: engagement counts updated asynchronously
5. Personalization: rerank based on user's following graph

Scaling challenge: 6000 tweets/second peak
Solution: Earlybird replicas, consistent hashing, parallel fan-out
"""
```


## X/Twitter Engineering Culture (2026)

Post-Musk X is radically different from pre-2022 Twitter:

- **High velocity**: Features shipped in days, not months; less process

- **Small teams**: Most teams are 3–8 engineers owning large surface areas

- **Performance obsession**: Engineering blog frequently posts about latency, memory, and cost wins

- **"Hardcore"**: Expect long hours during major product launches

## Compensation (2025 data)

| Level | Base | Total Comp (est.) |
| --- | --- | --- |
| SWE | $150–190K | $200–280K |
| Senior SWE | $190–230K | $280–380K |
| Staff SWE | $230–270K | $350–500K |

*X Corp. is now privately held. Equity is illiquid and uncertain. Compensation should be evaluated primarily on cash. Verify current comp data with levels.fyi.*

## Interview Tips

- **Real-time systems**: Twitter is fundamentally a real-time platform; know Kafka, stream processing, pub/sub

- **Performance focus**: Expect questions about latency, memory efficiency, and throughput optimization

- **Open source**: Twitter open-sourced their timeline algorithm; reading it shows genuine interest

- **Culture awareness**: Research recent changes honestly; show you can thrive in a fast-changing environment

- **LeetCode**: Medium-hard; graph algorithms and sliding window patterns common

*Practice problems: LeetCode 355 (Design Twitter), 295 (Median Data Stream), 362 (Design Hit Counter), 981 (Time Based Key-Value Store).*

## Related System Design Interview Questions

Practice these system design problems that appear in Twitter/X interviews:

- [Design a News Feed (Facebook-style)](https://www.techinterview.org/post/3233460016/design-a-news-feed-facebook-style/)

- [System Design: Search Autocomplete (Google Typeahead)](https://www.techinterview.org/post/3233460549/system-design-search-autocomplete/)

- [System Design: Notification System (Push, Email, SMS)](https://www.techinterview.org/post/3233460452/system-design-notification-system/)

- [System Design: URL Shortener (TinyURL / bit.ly)](https://www.techinterview.org/post/3233460451/system-design-url-shortener/)

## Related Company Interview Guides

- [Anthropic Interview Guide 2026: Process, Questions, and AI Safety](https://www.techinterview.org/post/3233460267/anthropic-interview-guide-2026-process-questions-and-ai-safety/)

- [Lyft Interview Guide 2026: Rideshare Engineering, Real-Time Dispatch, and Safety Systems](https://www.techinterview.org/post/3233460306/lyft-interview-guide-2026-rideshare-engineering-real-time-dispatch-and-safety-systems/)

- [Uber Interview Guide 2026: Dispatch Systems, Geospatial Algorithms, and Marketplace Engineering](https://www.techinterview.org/post/3233460273/uber-interview-guide-2026-dispatch-systems-geospatial-algorithms-and-marketplace-engineering/)

- [Meta Interview Guide 2026: Facebook, Instagram, WhatsApp Engineering](https://www.techinterview.org/post/3233460272/meta-interview-guide-2026-facebook-instagram-whatsapp-engineering/)

- [Cloudflare Interview Guide 2026: Networking, Edge Computing, and CDN Design](https://www.techinterview.org/post/3233460270/cloudflare-interview-guide-2026-networking-edge-computing-and-cdn-design/)

- [Shopify Interview Guide](https://www.techinterview.org/post/3233459924/shopify-interview/)

- [System Design: Apache Kafka Architecture](/post/3233460433/system-design-apache-kafka/)

- [System Design: Social Network at Scale](/post/3233460495/system-design-social-network/)

- [System Design: Music Streaming Service (Spotify)](/post/3233460805/system-design-music-streaming/)

- [System Design: Code Repository and CI/CD (GitHub / GitLab)](/post/3233460817/system-design-code-repository/)

- [System Design: Real-Time Bidding Platform](/post/3233460859/system-design-real-time-bidding/)

- [System Design: GraphQL API at Scale](/post/3233460898/system-design-graphql-api/)

- [System Design: Global Content Delivery and Edge Computing](/post/3233460954/system-design-edge-computing/)

- [System Design: API Rate Limiting and Throttling](/post/3233460984/system-design-rate-limiting/)

- [System Design: Distributed Cache (Redis Deep Dive)](/post/3233460434/system-design-distributed-cache/)

- [System Design: Notification System at Scale](/post/3233461021/system-design-notification-system-scale/)

- [System Design: Social Graph and Friend Recommendations](/post/3233461036/system-design-social-graph/)

- [System Design: WebRTC and Real-Time Video Architecture](/post/3233461050/system-design-webrtc-video/)

- [System Design: Content Moderation at Scale](/post/3233460623/system-design-content-moderation/)

*Explore all our [company interview guides](https://www.techinterview.org/category/company-guides/) covering FAANG, startups, and high-growth tech companies.*

Related system design: [System Design Interview: API Rate Limiter Deep Dive (All Algorithms)](https://techinterview.org/api-rate-limiter-system-design-deep-dive/)

Related system design: [System Design Interview: Design a Distributed File System (HDFS/GFS)](https://techinterview.org/system-design-distributed-file-system-hdfs/)

Related system design: [System Design Interview: Design a Distributed Messaging System (Kafka)](https://techinterview.org/system-design-distributed-messaging-kafka/)

See also: [System Design Interview: Design a Pastebin / Code Snippet Service](https://techinterview.org/system-design-pastebin/)

See also: [System Design Interview: Design a Feature Flag System](https://techinterview.org/system-design-feature-flag-system/)

- [System Design Interview: Design a Distributed File System (HDFS / GFS)](https://techinterview.org/system-design-distributed-file-system-hdfs-gfs/)

- [System Design Interview: Design a Social Graph (Friend Connections)](https://techinterview.org/system-design-social-graph-friend-connections/)

- [System Design Interview: Design a Content Delivery Network (CDN)](https://techinterview.org/system-design-content-delivery-network-cdn/)

- [Heap and Priority Queue Interview Patterns: Top-K, K-Way Merge, Median Stream](https://techinterview.org/heap-priority-queue-interview-patterns/)

- [System Design Interview: Design a Real-Time Bidding (RTB) System](https://techinterview.org/system-design-real-time-bidding-system/)

- [System Design Interview: Design a Real-Time Chat Application (WhatsApp/Slack)](https://techinterview.org/system-design-real-time-chat-whatsapp-slack/)

- [System Design Interview: Design a Search Engine (Query Processing and Ranking)](https://techinterview.org/system-design-search-engine-query-ranking/)

- [System Design Interview: Design a Video Streaming Platform (YouTube/Netflix)](https://techinterview.org/system-design-video-streaming-platform-youtube/)

- [System Design Interview: Design a Real-Time Analytics Dashboard](https://techinterview.org/system-design-real-time-analytics-dashboard/)

- [System Design Interview: Design a Social Media Feed System](https://techinterview.org/system-design-social-media-feed-system/)

- [System Design Interview: Design a Content Moderation System](https://techinterview.org/system-design-content-moderation-system/)

- [System Design Interview: Design a Notification System](https://techinterview.org/system-design-notification-system/)

- [System Design Interview: Design a Real-Time Gaming Leaderboard](https://techinterview.org/system-design-gaming-leaderboard/)

- [System Design Interview: Design a Typeahead / Search Suggestion System](https://techinterview.org/system-design-typeahead-search-suggestions/)

- [System Design Interview: Design an Ad Click Aggregation System (Google/Meta Ads)](https://techinterview.org/system-design-ad-click-aggregation/)

- [System Design Interview: Design a Live Sports Score System](https://techinterview.org/system-design-live-sports-scores/)

- [System Design Interview: Design a Rate Limiter (Token Bucket, Sliding Window)](https://techinterview.org/system-design-rate-limiter/)

- [System Design Interview: Design a Web Crawler and Search Indexer](https://techinterview.org/system-design-web-crawler-search-indexer/)

- [System Design Interview: Design an Online Auction System (eBay)](https://techinterview.org/system-design-auction-system/)

- [System Design Interview: Design a Streaming Data Pipeline (Kafka + Flink)](https://techinterview.org/system-design-streaming-data-pipeline/)

- [System Design Interview: Design a Geospatial Service (Nearby Drivers/Places)](https://techinterview.org/system-design-geospatial-service/)

- [System Design Interview: Design a Cryptocurrency Exchange](https://techinterview.org/system-design-cryptocurrency-exchange/)

- [System Design Interview: Design a Ticketing System (Ticketmaster)](https://techinterview.org/system-design-ticketing-system/)

- [System Design Interview: Design a Live Video Streaming Platform (Twitch)](https://techinterview.org/system-design-live-video-streaming/)

- [System Design Interview: Design a Recommendation System (Netflix/Spotify/Amazon)](https://techinterview.org/system-design-recommendation-system/)

- [System Design Interview: Design a Web Search Engine (Google)](https://techinterview.org/system-design-web-search-engine/)

- [System Design Interview: Design a Social Media Feed (Twitter/Instagram)](https://techinterview.org/system-design-social-media-feed/)

- [System Design Interview: Design a Notification Service (Push, SMS, Email)](https://techinterview.org/system-design-notification-service/)

- [System Design Interview: Design a Search Autocomplete System](https://techinterview.org/system-design-search-autocomplete/)

- [System Design Interview: Design a Real-Time Collaboration Tool (Figma/Miro)](https://techinterview.org/system-design-real-time-collaboration/)

- [System Design Interview: Design a CI/CD Deployment Pipeline](https://techinterview.org/system-design-cicd-pipeline/)

- [System Design Interview: Design a Real-Time Leaderboard](https://techinterview.org/system-design-leaderboard/)

- [System Design Interview: Design a Web Crawler](https://techinterview.org/system-design-web-crawler/)

- [System Design Interview: Design a Key-Value Store (Redis/DynamoDB)](https://techinterview.org/system-design-key-value-store/)

- [System Design Interview: Design a Video Streaming Platform (YouTube/Netflix)](https://techinterview.org/system-design-video-streaming/)

- [Trie Data Structure Interview Patterns: Autocomplete, Word Search & XOR](https://techinterview.org/trie-data-structure-interview-patterns/)

- [System Design Interview: Design a Load Balancer](https://techinterview.org/system-design-load-balancer/)

- [System Design Interview: API Design (REST vs GraphQL vs gRPC)](https://techinterview.org/system-design-api-design/)

- [System Design: Content Delivery Network (CDN)](https://techinterview.org/system-design-cdn/)

- [System Design: Real-Time Analytics Dashboard (ClickHouse / Druid)](https://techinterview.org/system-design-real-time-analytics/)

- [System Design: Search Engine (Google / Elasticsearch)](https://techinterview.org/system-design-search-engine/)

- [System Design: Real-Time Chat System (WhatsApp / Slack)](https://techinterview.org/system-design-chat-system/)

- [System Design: Twitter / Social Media Feed Architecture](https://techinterview.org/system-design-twitter-social-media-feed/)

- [System Design: Video Streaming Platform (Netflix/YouTube)](https://techinterview.org/system-design-video-streaming-platform/)

- [System Design: URL Shortener (bit.ly/TinyURL)](https://techinterview.org/system-design-url-shortener/)

- [System Design: Autocomplete and Typeahead Service](https://techinterview.org/system-design-autocomplete-typeahead/)

- [System Design: Machine Learning Platform and MLOps](https://techinterview.org/system-design-ml-platform-mlops/)

- [System Design: Recommendation Engine at Scale](https://techinterview.org/system-design-recommendation-engine/)

- [System Design: Distributed File System (GFS/HDFS/S3)](https://techinterview.org/system-design-distributed-file-system/)

## Related System Design Topics

- [System Design: Data Pipeline and Stream Processing](https://techinterview.org/system-design-data-pipeline/)

📌 Related: [System Design Interview: Design Instagram / Photo Sharing Platform](https://techinterview.org/system-design-instagram-photo-sharing/)

📌 Related: [System Design Interview: Design YouTube / Video Streaming Platform](https://techinterview.org/system-design-youtube-video-streaming/)

📌 Related: [System Design Interview: Design WhatsApp / Real-Time Messaging](https://techinterview.org/system-design-whatsapp-messaging/)

📌 Related: [System Design Interview: Design Twitter / X Timeline](https://techinterview.org/system-design-twitter-timeline/)

📌 Related: [Low-Level Design: Chat Application (OOP Interview)](https://techinterview.org/lld-chat-application/)

📌 Related: [System Design Interview: Design a Social Media News Feed](https://techinterview.org/system-design-news-feed/)

📌 Related: [System Design Interview: Design a Leaderboard / Top-K System](https://techinterview.org/system-design-leaderboard-top-k/)

📌 Related: [System Design Interview: Design a Search Autocomplete (Typeahead)](https://techinterview.org/system-design-autocomplete/)

📌 Related: [Trie Interview Patterns (2025)](https://techinterview.org/trie-interview-patterns/)

📌 Related: [Low-Level Design: Social Network Friend Graph (OOP Interview)](https://techinterview.org/lld-social-network/)

Related system design: [System Design: Consistent Hashing Explained with Virtual Nodes](https://techinterview.org/system-design-consistent-hashing/)

Related system design: [System Design Interview: Design a Distributed Message Queue (Kafka)](https://techinterview.org/system-design-message-queue/)

 Related: [Low-Level Design: Pub/Sub Message Broker (Observer Pattern)](https://techinterview.org/lld-pubsub-message-broker/)

Related system design: [System Design: Sharding and Data Partitioning Explained](https://techinterview.org/system-design-sharding-data-partitioning/)

Related system design: [System Design: Content Delivery Network (CDN) — Cache, Routing, Edge](https://techinterview.org/system-design-cdn-content-delivery-network/)

Related system design: [System Design: Database Replication, Read Scaling, and Failover](https://techinterview.org/system-design-database-replication/)

Related system design: [Low-Level Design: Social Media Feed (Follow, Post, Fan-out, Likes)](https://techinterview.org/lld-social-media-feed/)

Related system design: [System Design: Collaborative Document Editing (Google Docs) — OT, CRDT, and WebSockets](https://techinterview.org/system-design-collaborative-document-editing/)

Related system design: [System Design: Distributed Counters, Leaderboards, and Real-Time Analytics](https://techinterview.org/system-design-distributed-counters-analytics/)

Related system design: [System Design: Real-time Chat and Messaging System (WhatsApp/Slack) — WebSockets, Pub/Sub, Scale](https://techinterview.org/system-design-real-time-chat/)

Related system design: [System Design: Video Processing Pipeline (YouTube/Netflix) -- Transcoding, HLS, and Scaling](https://techinterview.org/system-design-video-processing-pipeline/)

Related system design: [System Design: Event-Driven Architecture -- Kafka, Event Sourcing, CQRS, and Saga Pattern](https://techinterview.org/system-design-event-driven-architecture/)

Related system design: [Low-Level Design: Content Moderation System -- Automated Filtering, Human Review, and Appeals](https://techinterview.org/lld-content-moderation-system/)

Related system design: [Low-Level Design: Social Media Post Scheduler -- Scheduling, Multi-Platform Publishing, and Analytics](https://techinterview.org/lld-social-media-post-scheduler/)

Related system design: [System Design: Log Aggregation and Observability Platform — ELK Stack, Metrics, Tracing, and Alerting](https://techinterview.org/system-design-log-aggregation-observability/)

Related system design: [Low-Level Design: Task Management System — Boards, Workflows, Assignments, Due Dates, and Notifications](https://techinterview.org/lld-task-management-system/)

Related system design: [System Design: Social Network News Feed — Fan-out on Write vs Read, Ranking, and Feed Generation](https://techinterview.org/system-design-social-network-feed/)

Related system design: [System Design: Typeahead and Search Autocomplete — Trie, Prefix Indexing, and Real-time Suggestions](https://techinterview.org/system-design-typeahead-search-autocomplete/)

Related system design: [System Design: Multiplayer Game Backend — Game Sessions, Real-time State, Matchmaking, and Leaderboards](https://techinterview.org/system-design-multiplayer-game-backend/)

Related system design: [System Design: WebRTC and Video Calling -- Signaling, ICE, STUN/TURN, and SFU Architecture](https://techinterview.org/system-design-webrtc-video-calling/)

Related system design: [Monotonic Stack and Queue Interview Patterns: Next Greater Element, Largest Rectangle, Sliding Window Maximum (2025)](https://techinterview.org/monotonic-stack-queue-interview-patterns/)

Related system design: [System Design: Distributed Message Queue -- Kafka Architecture, Partitions, Consumer Groups, and Delivery Guarantees](https://techinterview.org/system-design-distributed-message-queue/)

Related system design: [Low-Level Design: Social Media Platform -- Posts, Feeds, Follows, and Notifications](https://techinterview.org/lld-social-media-platform/)

Related system design: [System Design: Collaborative Editing — Operational Transformation, CRDTs, and Conflict Resolution](https://techinterview.org/system-design-collaborative-editing/)

Related system design: [System Design: Chat Application — Real-Time Messaging, Message Storage, and Presence (WhatsApp/Slack)](https://techinterview.org/system-design-chat-application/)

Related system design: [System Design: Ad Serving — Real-Time Bidding, Targeting, and Impression Tracking](https://techinterview.org/system-design-ad-serving/)

Related system design: [System Design: Typeahead and Autocomplete — Trie, Ranking, and Real-Time Suggestion Updates](https://techinterview.org/system-design-typeahead-autocomplete/)

Related system design: [System Design: Ad Server — Targeting, Real-Time Bidding, Impression Tracking, and Click Attribution](https://techinterview.org/system-design-ad-server/)

Related system design: [Low-Level Design: Task Management System (Trello/Jira) — Boards, Workflows, and Notifications](https://techinterview.org/lld-task-management/)

Related system design: [System Design: Flash Sale — High-Concurrency Inventory, Queue-Based Purchase, and Oversell Prevention](https://techinterview.org/system-design-flash-sale/)

Related system design: [System Design: Analytics Pipeline — Ingestion, Stream Processing, and OLAP Query Layer](https://techinterview.org/system-design-analytics-pipeline/)

Related system design: [System Design: Search Ranking — Query Processing, Inverted Index, and Relevance Scoring](https://techinterview.org/system-design-search-ranking/)

Related system design: [System Design: Live Comments — Real-Time Delivery, Moderation, and Spam Prevention at Scale](https://techinterview.org/system-design-live-comments/)

Related system design: [Low-Level Design: Blog Platform — Content Management, Comments, and SEO-Friendly URLs](https://techinterview.org/lld-blog-platform/)

Related system design: [System Design: Typeahead / Search Autocomplete — Trie Service, Ranking, and Low-Latency Delivery](https://techinterview.org/system-design-typeahead/)

See also: [System Design: Gaming Backend](https://techinterview.org/system-design-gaming-backend/)

See also: [Low-Level Design: Online Judge System](https://techinterview.org/lld-online-judge/)

See also: [System Design: Analytics Dashboard](https://techinterview.org/system-design-analytics-dashboard/)

See also: [System Design: Real-Time Bidding Platform](https://techinterview.org/system-design-realtime-bidding/)

See also: [System Design: Feed Ranking and Personalization](https://techinterview.org/system-design-feed-ranking/)

See also: [Low-Level Design: Poll and Voting System](https://techinterview.org/lld-poll-voting/)

Twitter's t.co URL shortener is a classic system design topic. Review the full design in [URL Shortener and Click Analytics Platform System Design](https://www.techinterview.org/post/3233466527/system-design-url-analytics/).

Twitter/X powers real-time sports conversations. Review the full live sports platform design in [Live Sports Score Platform System Design](https://www.techinterview.org/post/3233462676/system-design-live-sports-scores/).

See also: [Low-Level Design: Content Moderation System - Rules Engine, ML Scoring, and Appeals](https://www.techinterview.org/post/3233466649/lld-content-moderation/)

Twitter/X system design covers feed fan-out. Review the full social feed LLD in [Social Feed System Low-Level Design](https://www.techinterview.org/post/3233464486/lld-social-media-feed/).

See also: [Low-Level Design: API Rate Limiter - Token Bucket, Sliding Window, and Distributed Throttling](https://www.techinterview.org/post/3233466721/lld-api-rate-limiter/)

Twitter engineering tests interval scheduling. Review meeting rooms and non-overlapping interval patterns in [Interval Interview Patterns](https://www.techinterview.org/post/3233464624/interval-interview-patterns/).

Twitter search uses autocomplete. Review trie, Redis sorted sets, and trending query detection in [Search Autocomplete System Low-Level Design](https://www.techinterview.org/post/3233466851/lld-search-autocomplete/).

Twitter uses URL shortening at scale. Review base62, redirect strategy, and analytics in [URL Shortener System Low-Level Design](https://www.techinterview.org/post/3233466875/lld-url-shortener/).

Twitter search indexes billions of tweets. Review web crawler, inverted index, and query processing in [Search Engine System Low-Level Design](https://www.techinterview.org/post/3233467019/lld-search-engine/).

Twitter handles high-traffic events. Review virtual waiting room and booking system scaling in [Ticket Booking System Low-Level Design](https://www.techinterview.org/post/3233467045/lld-ticket-booking/).

Twitter system design covers follow graph and social networks. Review the social graph LLD in [Social Graph System Low-Level Design](https://www.techinterview.org/post/3233467093/lld-social-graph/).

Twitter system design covers trending and ranking. Review Redis sorted set leaderboard design in [Game Leaderboard System Low-Level Design](https://www.techinterview.org/post/3233467162/lld-game-leaderboard/).

Twitter system design covers ad click tracking at scale. Review the full LLD in [Ad Click Tracker System Low-Level Design](https://www.techinterview.org/post/3233467186/lld-ad-click-tracker/).

Twitter system design covers real-time event analytics. Review Kafka, Druid, and HyperLogLog design in [Real-Time Analytics Platform Low-Level Design](https://www.techinterview.org/post/3233467211/lld-realtime-analytics/).

Twitter system design covers A/B testing at scale. Review the full experimentation LLD in [A/B Testing Platform Low-Level Design](https://www.techinterview.org/post/3233467235/lld-ab-testing/).

Twitter system design covers timeline and feed delivery. Review the full feed LLD in [Content Feed System Low-Level Design](https://www.techinterview.org/post/3233467330/lld-content-feed/).

Twitter system design covers comment and reply threading. Review the nested comment and voting LLD in [Comment System Low-Level Design](https://www.techinterview.org/post/3233467450/lld-comment-system/).

Cursor-based pagination and feed design is covered in our [Pagination System Low-Level Design](https://www.techinterview.org/post/3233473300/lld-pagination-design/).

Activity feed and timeline fan-out design is covered in our [Activity Feed System Low-Level Design](https://www.techinterview.org/post/3233468622/lld-activity-feed-aggregator/).

Follow system architecture design is covered in our [Follow System Low-Level Design](https://www.techinterview.org/post/3233467782/lld-follow-system/).

Comments and reply threading system design is covered in our [Comments System Low-Level Design](https://www.techinterview.org/post/3233467859/lld-comments-system/).

Like system design is covered in our [Like System Low-Level Design](https://www.techinterview.org/post/3233467860/lld-like-system/).

Tagging system and hashtag design is covered in our [Tagging System Low-Level Design](https://www.techinterview.org/post/3233467861/lld-tagging-system/).

Live comments and real-time feed design is covered in our [Live Comments System Low-Level Design](https://www.techinterview.org/post/3233467931/lld-live-comments/).

Mentions and notification system design is covered in our [Mentions and Notifications System Low-Level Design](https://www.techinterview.org/post/3233467932/lld-mentions-notifications/).

User blocking and harassment prevention design is covered in our [User Blocking System Low-Level Design](https://www.techinterview.org/post/3233467935/lld-user-blocking/).

Cursor-based pagination and infinite scroll feed design is covered in our [Cursor Pagination Low-Level Design](https://www.techinterview.org/post/3233468056/lld-cursor-pagination/).

API pagination and infinite scroll feed design is covered in our [API Pagination Low-Level Design](https://www.techinterview.org/post/3233468067/lld-api-pagination/).

Link preview and URL unfurling system design is covered in our [Link Preview Service Low-Level Design](https://www.techinterview.org/post/3233468296/lld-link-preview/).

Follower graph and social feed design is covered in our [Follower Graph Low-Level Design](https://www.techinterview.org/post/3233468385/lld-follower-graph/).

Trending topics and hashtag system design is covered in our [Trending Topics Low-Level Design](https://www.techinterview.org/post/3233468386/lld-trending-topics/).

Content moderation and abuse reporting design is covered in our [Report and Abuse System Low-Level Design](https://www.techinterview.org/post/3233468391/lld-report-abuse/).

Poll and voting system design is covered in our [Poll System Low-Level Design](https://www.techinterview.org/post/3233468394/lld-poll-system/).

A/B experiment and product experimentation design is covered in our [A/B Experiment System Low-Level Design](https://www.techinterview.org/post/3233469934/lld-experiment-platform/).

Distributed counter and high-throughput counting design is covered in our [Distributed Counter Low-Level Design](https://www.techinterview.org/post/3233468546/lld-distributed-counter/).

Activity feed and social media feed design is covered in our [Activity Feed Aggregator Low-Level Design](https://www.techinterview.org/post/3233468622/lld-activity-feed-aggregator/).

See also: [Content Scheduler Low-Level Design: Scheduled Publishing, Timezone Handling, and Recurring Content](https://www.techinterview.org/post/3233468714/lld-content-scheduler/)

See also: [Image Moderation Pipeline Low-Level Design: ML Classification, Human Review Queue, and Appeals](https://www.techinterview.org/post/3233468723/lld-image-moderation/)

See also: [Threaded Comment System Low-Level Design: Nested Replies, Voting, and Moderation](https://www.techinterview.org/post/3233468725/lld-comment-threading/)

See also: [Follower Feed Low-Level Design: Fanout Strategies, Feed Pagination, and Hybrid Approach for Celebrities](https://www.techinterview.org/post/3233469497/lld-follower-feed/)

See also: [Spam Detection System Low-Level Design: Velocity Checks, Graph-Based Detection, and Classifier Ensemble](https://www.techinterview.org/post/3233469710/lld-spam-detection/)

See also: [Abuse Detection System Low-Level Design: Multi-Signal Risk Scoring, Account Takeover Detection, and Automated Response](https://www.techinterview.org/post/3233469711/lld-abuse-detection/)