# System Design in English: A Frontend Engineer Case Study

> Written English was fine. Spoken answers stalled. See how one Frontend Engineer from Brazil practised system-design answers out loud.

- **Page type:** Case study
- **URL:** https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-brazil
- **Last updated:** 2026-09-01

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.

What this case shows

Written English was fine. Spoken answers stalled. See how one Frontend Engineer from Brazil practised system-design answers out loud.

At a glance

| Role              | Frontend / Mobile Engineer                            |
| ----------------- | ----------------------------------------------------- |
| Location          | Brazil                                                |
| English challenge | system design                                         |
| Interview problem | System Design                                         |
| Target            | a frontend interview in English                       |
| Preparation       | Live mocks with English feedback on the same answers  |
| Outcome           | Gained clearer, more confident English for interviews |

## The Gap Between Knowing and Explaining

The CV shows the work. The interview asks you to explain it in English, live, without stopping to translate. She was a frontend / mobile engineer in Brazil. Day-to-day work used React. In the room, system design was what broke down.

## What We Practised

Practice matched the round she actually had to speak: system design. Each mock interview included notes on the same answer - where she paused, which words were vague, and where the structure broke.

- Practised stating the requirements in English before naming any services or components.
- Used the same spoken order every time: scope, then main components, then bottlenecks, then trade-offs.
- Practised explaining design trade-offs out loud, not only drawing boxes on a board.
- Worked on saying metrics in full English sentences - for example latency, load, and cost.
- Described the architecture in English without stopping to translate each sentence in her head.

Useful references along the way: [STAR interview framework](https://app.mocklyenglish.com/guides/star-interview-framework), [What to expect in English interviews](https://app.mocklyenglish.com/guides/what-to-expect-in-english-interviews).

## Why System Design Is Difficult in English

System design is a thirty-to-forty-five-minute spoken explanation. You must order the components, defend trade-offs, handle follow-up questions, and keep the vocabulary accurate while the clock runs. Translating each sentence in your head uses the time the interviewer needed for depth. A fixed spoken order is what keeps the round clear in a second language.

Preparing for a similar path? Read [How a Frontend Engineer From China Prepped for English Interviews](https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-china).

## The Turning Point

The shift showed up in a timed system-design mock interview. She knew the architecture but jumped between components. A fixed spoken sequence - requirements, then scale, then architecture, then bottlenecks - was repeated until follow-up questions stayed inside that order.

Proof of work - one mock session

| Problem       | Timed walkthrough of a service end to end                                |
| ------------- | ------------------------------------------------------------------------ |
| Old approach  | Jumped between components; the interviewer had to reconstruct the design |
| New framework | Requirements → scale → architecture → bottlenecks → trade-offs           |
| Result        | Follow-ups stayed inside a known spoken order                            |

How answers sounded before

“We need a database and maybe cache and also queues, and the model, and then monitoring…”

How answers sounded after

“I'd start with the write path and the read path, then the bottleneck at peak load, then one trade-off I would actually defend.”

## What Changed

Gained clearer, more confident English for interviews. She could explain system-design answers more clearly when questions got hard. That readiness was the goal - not a promised job offer.

## What to Practise

- State the scope in English before you name any services.
- Use one spoken order every time: requirements, then scale, then architecture, then bottlenecks, then trade-offs.
- Practise saying metrics such as latency, queries per second, and storage in full sentences.
- Name at least one trade-off out loud, even when you are sure about the design.
- Record a fifteen-minute design walkthrough and listen only for jumps and unfinished sentences.

## Starting Point

She prepared for English-language interviews as a frontend and mobile engineer. The stack was React. Written English was stronger than speaking under time pressure.

FAQ

## Questions

### What English should a frontend / mobile engineer learn for interviews?

The English of the round you will face - here, system design. Learn full sentences for that format, not a general business-English course. That is what this frontend / mobile engineer practised.

### How do I explain system design if I translate in my head?

Lock a spoken order - requirements, scale, architecture, trade-offs - and reuse it. Translating each sentence is what makes you jump between components. That fixed order is what helped this frontend / mobile engineer.

### Can I pass a tech interview if my English isn't fluent?

Yes. Interviewers need to follow your reasoning. A clear structure and the right words matter more than sounding native. This case study about this frontend / mobile engineer is about that gap - not about erasing an accent.

### What if I understand English but struggle to speak in interviews?

That was the pattern here: written English was stronger than live answers. Practise system design out loud, with follow-up questions, until the words come without long pauses.

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

## Similar case studies

[Frontend / Mobile Engineer·China](https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-china)

### [How a Frontend Engineer From China Prepped for English Interviews](https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-china)

[Written English was fine. Spoken answers stalled. See how one frontend engineer from China practised system-design answers out loud.](https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-china)

[Gained clearer, more confident English for interviews](https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-china)

[Backend Engineer·Brazil](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-brazil)

### [System Design in English: A Backend Engineer Case Study](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-brazil)

[A Brazilian backend engineer knew the work. Live English for system-design answers was where interviews stalled. Here is the practice that changed the delivery.](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-brazil)

[Gained clearer, more confident English for interviews](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-brazil)

## More case studies

- [How a Non-Native Speaker Handled Wise's System Design Round](https://app.mocklyenglish.com/case-studies/engineering-manager-wise-interview-english-brazil)
- [Interview-Ready English for a Frontend Engineer From Europe](https://app.mocklyenglish.com/case-studies/frontend-engineer-technical-interview-english-europe)
- [From Nervous to Fluent: English Interview Prep for Backend Engineers](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-georgia)
- [Preparing for a System Design Interview in English](https://app.mocklyenglish.com/case-studies/backend-engineer-system-interview-english-russia)

## Related resources

- [Interview English Course (free curriculum)](https://app.mocklyenglish.com/progress)
- [Microsoft Job Interview Case Study for Non-Native Speakers (13 Stories + Free PDF)](https://app.mocklyenglish.com/blog/competency-based-behavioral-interview)
- [Conflict and disagreement questions (with model answers)](https://app.mocklyenglish.com/blog/top-30-behavioural-interview-questions#conflict-and-disagreement)
- [How to Prepare for Tech Behavioural Interviews](https://app.mocklyenglish.com/blog/prepare-tech-behavioural-interview)
- [STAR Method in English](https://app.mocklyenglish.com/guides/star-interview-framework)

Case studies are illustrative, based on patterns from real coaching sessions.

## 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: "System Design in English: A Frontend Engineer Case Study, Mockly English (https://app.mocklyenglish.com/case-studies/frontend-engineer-system-interview-english-brazil)".
