PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Asana

Design a Twitter-like microblogging service

Last updated: Mar 29, 2026

Quick Overview

This question evaluates system design competencies including scalable architecture, data and API modeling, feed generation trade-offs, storage and caching strategies, consistency expectations, and operational concerns such as rate limiting, abuse mitigation, and observability.

  • medium
  • Asana
  • System Design
  • Software Engineer

Design a Twitter-like microblogging service

Company: Asana

Role: Software Engineer

Category: System Design

Difficulty: medium

Interview Round: Technical Screen

Design a Twitter-like microblogging system. You can describe it verbally and with structured notes. Requirements: - Users can post short messages. - Users can follow/unfollow others. - Users can view a home timeline/feed with recent posts from accounts they follow. - Support high read volume and write volume. Clarify and address: - Core APIs and data models. - Feed generation approach (fan-out on write vs fan-out on read, or hybrid). - Storage choices, caching, pagination, and ranking. - Consistency expectations (e.g., how quickly a new post should appear). - Operational concerns: rate limiting, abuse/spam, and observability.

Quick Answer: This question evaluates system design competencies including scalable architecture, data and API modeling, feed generation trade-offs, storage and caching strategies, consistency expectations, and operational concerns such as rate limiting, abuse mitigation, and observability.

Related Interview Questions

  • Design a Collaborative Todo List - Asana (medium)
  • Design a Twitter-like service - Asana (medium)
Asana logo
Asana
Feb 8, 2026, 12:00 AM
Software Engineer
Technical Screen
System Design
5
0

Design a Twitter-like microblogging system. You can describe it verbally and with structured notes.

Requirements:

  • Users can post short messages.
  • Users can follow/unfollow others.
  • Users can view a home timeline/feed with recent posts from accounts they follow.
  • Support high read volume and write volume.

Clarify and address:

  • Core APIs and data models.
  • Feed generation approach (fan-out on write vs fan-out on read, or hybrid).
  • Storage choices, caching, pagination, and ranking.
  • Consistency expectations (e.g., how quickly a new post should appear).
  • Operational concerns: rate limiting, abuse/spam, and observability.

Solution

Show

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Asana•More Software Engineer•Asana Software Engineer•Asana System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,000+ 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.