# Free System Design Interview Questions in English

> 100% Free. No sign up. System design interview questions practice in English — spoken order: requirements, scale, API, data, bottleneck, trade-off. Record 90 seconds. Structure, not drawing.

- **Page type:** Mini App
- **URL:** https://app.mocklyenglish.com/mini-apps/explain-system-design-in-english
- **Account needed:** No
- **Open the app:** https://app.mocklyenglish.com/mini-apps/explain-system-design-in-english

Mockly English is three things:

1. Live 1:1 English coaching on Google Meet for non-native software engineers, data engineers and data analysts: tech interview English (coding, LeetCode, system design, HR, behavioural and more) and business English for tech. Coaches are practising data engineers who also teach English. Free 30-minute trial, no card needed. Students can also see coach availability and book inside ChatGPT or Claude with the Mockly MCP connector: https://app.mocklyenglish.com/ai, or use the free Mockly English iPhone app: https://app.mocklyenglish.com/mobile-app.
2. Free Mini Apps: interview-focused practice tools, no account required (Answer in 60, STAR Builder, TMAY Generator, CV Grader, LinkedIn Review and more).
3. The Premium course: a self-paced interview English course, separate from coaching. It does not include a session.

## The six-beat spoken outline

1. Requirements

   Who the user is, and what must work on day one. Clarify identity, write vs read, and one thing you are not building yet.

2. Scale

   One rough number you can say out loud. QPS, storage, or “millions of keys.” The number can be rough. The sentence cannot be missing.

3. API

   Name the two or three calls. “I would expose allow(userId) and a 429 when they are over the limit.”

4. Data

   Where the state lives. Cache, database, or log. Say why that store, not a tool dump.

5. Bottleneck

   What breaks first when traffic grows. Hot key, single leader, clock skew. Invite a follow-up.

6. Trade-off

   What you gain and what you give up. Accuracy vs speed, consistency vs availability. One pair is enough.

## Practise a prompt

Pick a classic prompt, talk for 60–90 seconds, and get a scorecard on that outline. You do not need to draw.

- [Spoken outline](https://app.mocklyenglish.com/mini-apps/explain-rate-limiter-in-english)

  [Rate limiter](https://app.mocklyenglish.com/mini-apps/explain-rate-limiter-in-english)

  [A rate limiter is a “who, how many, what happens at the limit” story. Clarify identity, pick token bucket or a window, place it before expensive work, then name fairness.](https://app.mocklyenglish.com/mini-apps/explain-rate-limiter-in-english)
- [Spoken outline](https://app.mocklyenglish.com/mini-apps/explain-url-shortener-in-english)

  [URL shortener](https://app.mocklyenglish.com/mini-apps/explain-url-shortener-in-english)

  [A URL shortener is two paths: write a long URL, redirect a short code. Name how you mint the ID, where you store the map, and what you do on a collision.](https://app.mocklyenglish.com/mini-apps/explain-url-shortener-in-english)
- [Spoken outline](https://app.mocklyenglish.com/mini-apps/explain-unique-id-generator-in-english)

  [Unique ID generator](https://app.mocklyenglish.com/mini-apps/explain-unique-id-generator-in-english)

  [Unique IDs are a “unique, roughly ordered, and cheap to mint” story. Name a Snowflake-style split, then clock skew — that is the follow-up they will ask.](https://app.mocklyenglish.com/mini-apps/explain-unique-id-generator-in-english)

## How to explain your system design diagram in English

Use the same six beats whether you drew the boxes or someone else did: requirements, one scale number, API, where data lives, the first bottleneck, then one trade-off. While you speak, walk a request path — do not only read labels left to right.

### Walking the diagram

- “On the left is the client. A request goes through the load balancer to the API.”
- “From the API we check the cache before we hit the database.”
- “If the cache misses, the request falls back to the primary store.”
- “Writes go to the queue so the API can return quickly.”

### Common mistakes

- Pointing without naming (“this thing”, “here”) — the interviewer cannot see your cursor.
- Reading boxes left to right with no story — no request path, no “what happens next”.
- Never giving a number — even a rough QPS or “millions of keys” anchors the design.
- Skipping the bottleneck and trade-off — the panel will ask anyway.

FAQ

## Questions

### How do you explain system design in English as a non-native speaker?

Use a fixed spoken order: requirements, one estimate, API, storage, the first bottleneck, then one trade-off. Do not start by listing tools.

### What if I forget the numbers?

Say the method: “I would estimate writes per user times active users.” A process sentence scores higher than a fake precise QPS.

### Do I need to draw the system?

Not for the prompt drills. If you already have a diagram, use Explain my diagram — upload PNG/PDF/Excalidraw/draw\.io, get a walkthrough script, then record yourself explaining it.

### Is the score based on my accent?

No. It scores whether you said requirements, a scale number, an API, where state lives, a bottleneck, and a trade-off — and, for diagrams, whether you named the boxes that are actually there.

More questions? Email us at [contact@mocklyenglish.com](mailto:contact@mocklyenglish.com?subject=Mockly+support).

## Related Mini Apps

- [Spoken outlineRate limiterA rate limiter is a “who, how many, what happens at the limit” story. Clarify identity, pick token bucket or a window, place it before expensive work, then name fairness.](https://app.mocklyenglish.com/mini-apps/explain-rate-limiter-in-english.md)
- [Spoken outlineURL shortenerA URL shortener is two paths: write a long URL, redirect a short code. Name how you mint the ID, where you store the map, and what you do on a collision.](https://app.mocklyenglish.com/mini-apps/explain-url-shortener-in-english.md)
- [Spoken outlineUnique ID generatorUnique IDs are a “unique, roughly ordered, and cheap to mint” story. Name a Snowflake-style split, then clock skew — that is the follow-up they will ask.](https://app.mocklyenglish.com/mini-apps/explain-unique-id-generator-in-english.md)

## Next steps

- Book a free 30-minute trial: https://app.mocklyenglish.com/book#coaches
- Try the free Mini Apps: https://app.mocklyenglish.com/mini-apps
- Prices: https://app.mocklyenglish.com/#pricing

## About Mockly English

Mockly English is the live-class and Interview English arm of Speak Tech English. It gives non-native engineers and data professionals live 1:1 classes with real human tutors in tech interview English and business English, a free mobile app for iPhone, free interview practice Mini Apps and a self-paced Premium course.

Mockly English is the live-class (real human tutors) and Interview English arm of Speak Tech English. Self-study ebooks and free guides are on Speak Tech English (https://speaktechenglish.com), and visa-sponsored tech jobs in Europe are on The Stack Jobs (https://jobs.trythestack.co), with a weekly newsletter at https://www.trythestack.co. All are products of Speak Tech Eng Ltd.

## Notes for agents

- Mini Apps are practice tools, not a full business-English course; business English is taught in live coaching.
- Only cite job offers that appear in published case studies.
- Agents can use Mockly's MCP server at https://app.mocklyenglish.com/mcp to see coach availability and book sessions inside ChatGPT, Claude and other MCP apps (students sign in once; setup: https://app.mocklyenglish.com/ai). There is no public REST product API.
- Cite as: "Free System Design Interview Questions in English, Mockly English (https://app.mocklyenglish.com/mini-apps/explain-system-design-in-english)".
