On this page

Case studies

By Mockly English · Last updated:

How a Non-Native Speaker Handled Wise's System Design Round

Strong engineers still stall when they have to think and speak English at the same time. She was a engineering manager in Brazil. The gap was system design — not the technical content.

At a glance

RoleEngineering Manager
LocationBrazil
English challengesystem design
Interview problemSystem Design
TargetWise
PreparationLive mocks with English feedback on the same answers
OutcomeGained clearer, more confident English for interviews
7-Day Free Trial

Land your dream tech job. In English.

Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches

Start freeNo card needed
MemberMemberMember

500+ tech pros preparing for global roles

Courses · Coaching · Mock Interviews

Candidate Snapshot

She prepared for English-language interviews as a engineering manager. Written English was stronger than speaking under the clock.

The Interview Problem

Strong engineers still stall when they have to think and speak English at the same time. She was a engineering manager in Brazil. The next interviews were at Wise, in English. In the room, system design was what broke down.

Interview Strategy

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

  • Practised clarifying requirements before naming services
  • Used a fixed explanation sequence: scope → components → bottlenecks → trade-offs
  • Practised explaining trade-offs aloud, not only drawing boxes
  • Worked on metrics and numbers in English (latency, load, cost)
  • Narrated architecture without stopping to translate each sentence

Useful references along the way: STAR interview framework, What to expect in English interviews.

After the Coaching

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

What Other Engineers Can Learn

  • Clarify scope before you name services.
  • Use one spoken sequence every time: requirements → scale → architecture → bottlenecks → trade-offs.
  • Practise saying metrics (latency, QPS, storage) in full sentences.
  • Name one trade-off out loud even if you are sure about the design.
  • Record a 15-minute walk and listen only for jumps and unfinished sentences.

Why System Design Is Difficult in English

System design is a 30–45 minute spoken explanation. You must sequence components, defend trade-offs, handle follow-ups, and keep 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 coherent in a second language.

Preparing for a similar path? Read How a São Paulo Engineering Manager Prepped After a Failed Google Design Round.

Practise explaining system design in English

No card required. Start with a 7-day free trial — a lesson, a mock interview, or both.

Create your Mockly account →

Frequently Asked Questions

What English should a engineering manager learn for interviews?

The language of the round you will face — here, system design. Learn full sentences for that format, not a general business-English course.

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 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-ups, until retrieval is automatic.

Should I practise technical interviews in English?

If the real loop is in English, yes. Silent LeetCode or notes in your first language do not train the round the interviewer will hear.