Quick Answer
How to design Instagram in English interviews: separate upload from feed generation, estimate photo storage, then walk sharding, redundancy, and ranking tradeoffs out loud.
Diagrams and what to say while drawing
Draw as you speak: requirements → APIs → estimates → boxes → deep dive → bottlenecks. Western panels score the narration as much as the diagram.
Key vocabulary
| Term | Plain meaning | Say it in an interview |
|---|---|---|
| Upload path | How photos enter the system | “Uploads go to blob storage, then we write metadata.” |
| News feed | Ranked posts for a user | “I’ll separate feed generation from photo storage.” |
| Shard | Split data across machines | “I’d shard photos by user_id.” |
| Hot user | Celebrity with huge fanout | “Hot users need a different fan-out strategy.” |
ESL English phrases and transitions
Open and clarify
- “I’ll clarify photo vs video scope and feed requirements.”
- “Reads will dominate - I’ll design for that.”
- “Upload path and feed path are different bottlenecks.”
UK/US system design moves
- “The tradeoff is X versus Y.”
- “I’ll deep-dive this component next.”
- “A single point of failure here would be …”
Pair this chapter with Mockly’s System Design interview English hub.
Key English language pitfalls
| Pitfall | Sounds like | Say instead |
|---|---|---|
| Designing only the UI | Misses backend | Lead with storage and feed. |
| One DB for everything | Won’t scale | Separate blobs and metadata. |
| Ignoring CDN | Slow images | Say CDN for static photo bytes. |
| Summary | Clear tradeoffs are how Western panels hear senior engineers. | |
Common English mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| No redundancy talk | Fragile design | Name replicas and failover. |
| Feed = SQL join forever | Too slow | Precompute or cache timelines. |
| Skipping hot users | Classic trap | Call out celebrity fan-out. |
What the interviewer is testing
For Instagram-scale photo sharing, UK/US interviewers test structured thinking, scale intuition, and calm spoken English - not accent perfection.
They listen for clarify → estimate → design → tradeoffs → bottlenecks. If those moves are audible, you sound hireable.
How to open in English
First 20 seconds
- “I’ll clarify photo vs video scope and feed requirements.”
- “Reads will dominate - I’ll design for that.”
- “Upload path and feed path are different bottlenecks.”
instagram system design interview
Use this sequence for instagram system design interview. Say the step name before you do it.
| Step | What to say |
|---|---|
| Clarify | Follow graph, photo size, feed freshness, search or not. |
| Estimate | Uploads/day, storage, read QPS for feeds. |
| High-level | Clients, app servers, photo store, metadata DB, feed service, cache. |
| Feed | Push vs pull; ranking; sharded graph implications. |
| Reliability | Replicas, CDN for photos, failure handling. |
Weak vs strong answers
Weak
Users upload photos and friends see them somehow.
Strong
Upload writes to object storage and metadata DB; feed service builds timelines asynchronously; CDN serves photo bytes; I’d deep-dive sharding and hot-user fan-out next.
How to say the key terms
| Term | Say it |
|---|---|
| CDN | “content delivery network” |
| fan-out | “fan-out on write versus read” |
Follow-up questions you will get
Expect these
- “How do you rank the feed?”
- “What changes if we add Stories or Reels?”
Practice drill
Set a timer for twelve minutes. Design Instagram-scale photo sharing out loud in English. Record yourself. Check: clarify, estimate, tradeoffs, bottlenecks.
Repeat tomorrow focusing only on the deep-dive section.
Answer frameworks you can reuse
Clarify → APIs → Estimates → Data model → High-level → Deep dive → Bottlenecks.
For every deep dive: options → tradeoffs → recommendation.
Technical Software Interview English knowledge base
← Technical Software Interview English knowledge base - start at How to Walk System Design Interviews in English for the full chapter index and reading order.
Explore every Mockly article on the blog hub.
All chapters in this series
Jump between Technical Software Interview English posts below. Each chapter builds spoken English for the same book - use the KB overview when you want the big picture.
| # | Chapter | Slug |
|---|---|---|
| 1 | How to Walk System Design Interviews in English | system-design-interview-seven-steps-in-english |
| 2 | How to Design Pastebin in English Interviews | pastebin-system-design-in-english |
| 3 | How to Design Instagram in English Interviews (you are here) | instagram-system-design-in-english |
| 4 | How to Design Twitter Timeline in English | twitter-system-design-in-english |
| 5 | How to Design Yelp Nearby Search in English | yelp-nearby-system-design-in-english |
| 6 | How to Design Uber Dispatch in English | uber-system-design-in-english |
| 7 | How to Design Ticketmaster in English | ticketmaster-system-design-in-english |
| 8 | Long Polling vs WebSockets vs SSE in English | long-polling-websockets-sse-in-english |
- How to Walk System Design Interviews in English
- How to Design Pastebin in English Interviews
- How to Design Instagram in English Interviews - you are here
- How to Design Twitter Timeline in English
- How to Design Yelp Nearby Search in English
- How to Design Uber Dispatch in English
- How to Design Ticketmaster in English
- Long Polling vs WebSockets vs SSE in English
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.