# Design Twitter's API — system design interview question

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/questions/1300/design-twitter-api
Source observed: 2026-11-05T00:13:39.421Z
Last checked: 2026-11-05T00:13:39.421+00:00
Indexed: 2026-11-06T21:36:13.069+00:00

---

# Design Twitter's API.

We provide this as a system design interview question in Aced (formerly Exponent), our interview-preparation platform. The question concerns designing Twitter's API and is categorized as **System Design** and **Technical**.

## Question details

- **Interview type:** System Design
- **Reported last asked:** 4 months ago
- **Roles:** [Software Engineer](https://www.aced.io/questions?role=swe) — 3
- **Companies associated with this question:** [MongoDB](https://www.aced.io/questions?company=mongodb), [Amazon](https://www.aced.io/questions?company=amazon), [Lumos](https://www.aced.io/questions?company=lumos), and [Twitter](https://www.aced.io/questions?company=twitter)
- **Categories:** [System Design](https://www.aced.io/questions?type=system-design), [Technical](https://www.aced.io/questions?type=technical)
- **Community answers:** No answers have been contributed by the community yet.

Members can use our interview-preparation resources, including:

- 100+ expert answer videos
- Access to all courses
- Peer-to-peer practice
- Private Discord community
- Full question database

[Upgrade](https://www.aced.io/upgrade?src=questions) or [upgrade now](https://www.aced.io/upgrade?src=questions).

## Interview experiences

Three shared interview experiences are associated with this question:

1. **MongoDB · 4 months ago** — Software Engineer, Mid Level / L4
   > Good coding round; good overall experience; interviewer was supportive. Cons: it went for 2 months.

   [Read the MongoDB interview experience](https://www.aced.io/experiences/mongodb-software-engineer-interview-bcaba8).

2. **Amazon · 10 months ago** — Software Engineer, Entry Level / L3
   > The overall process was quite slow and took longer than expected. The timeline seemed to depend largely on the interviewer, as scheduling and progress varied based on availability. There were delays between stages, making the process feel less streamlined. More consistent communication and scheduling could have made it more efficient.

3. **Lumos · 2 years ago** — Software Engineer
   > Nice. People genuinely wanted to help. Strong focus on WLB. Hired as new grad. People are genuinely friendly and want to help.

   WLB means work-life balance.

## Related questions

- [Design Twitter.](https://www.aced.io/questions/1374/design-twitter)
- [Design the SMS API for Twilio.](https://www.aced.io/questions/4497/design-twilio-sms-api)
- [Design Twilio.](https://www.aced.io/questions/7160/design-twilio-communication-platform)

## Related courses

### [Software Engineering Interview Prep](https://www.aced.io/courses/software-engineering)

We help candidates prepare for software engineering roles at Google, Amazon, Microsoft, Meta, Apple, and other companies through mock interviews, frameworks, and advice from senior candidates. The course covers data structures, algorithms, system design, people management, behavioral interviews, and more.

![Software Engineering Interview Prep](https://images.ctfassets.net/x78yjrjc11pq/4VkuYewBHUFIVUS5oJDW5h/02e833439b1289f25f38f13f81cbdca3/adobe_stock_optimized.jpeg?w=800&h=800&fm=webp&q=75)

### [System Design Interviews](https://www.aced.io/courses/system-design-interviews)

We teach candidates how to answer current system design questions across product, infrastructure, and AI domains. The course includes in-depth video examples, written breakdowns, reference patterns, and mock interview videos in which senior engineers and managers answer these questions.

![System Design Interviews](https://images.ctfassets.net/x78yjrjc11pq/78x7miFZFjBCrM5GqftrMJ/2f6d26e632c4e7265c49f6a180227edb/system_design_track_compressed_26ac98a46e__281_29_5be2280f31.jpeg?w=800&h=800&fm=webp&q=75)

## Submit an answer

After signing in or creating an account, candidates can submit an answer and mark the question complete. [Sign up](https://www.aced.io/signup?src=nav&returnPath=/questions/1300/design-twitter-api) or [log in](https://www.aced.io/login?src=nav).

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F1300%2Fdesign-twitter-api&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fquestions%2F1300%2Fdesign-twitter-api). Opening a form does not execute a tool.