Black Friday sale: 25% off all coaching sessions and packs. See prices

A Brazilian SWE in the US Preparing System Design Interviews in English

About six years of engineering and a monolith-to-microservices migration to explain - in behavioral and system design rounds, in English.

By Mockly English · Last updated Based on real coaching sessions. Names and some identifying details are changed to protect student privacy.

What this case shows

A software engineer who moved from Brazil to the US prepared behavioral and system design interviews in English around a monolith-to-microservices story.

At a glance

RoleSoftware engineer (~6 years)
RegionUnited States
BackgroundMoved from Brazil to the US
FocusBehavioral + system design
Story bankMonolith → microservices at a large bank
OutcomeNo interview result recorded in the notes

Timeline

Brazil → US

Focus

Monolith → microservices

Outcome

Behavioral + system design

Profile

A software engineer with about six years of experience who moved from Brazil to the US, preparing for interviews that cover behavioral and system design rounds in English. Her core technical story was a monolith-to-microservices migration at a large bank.

Goals

  • Prepare behavioral interview answers in English
  • Prepare system design interviews in English
  • Explain a monolith-to-microservices migration clearly

Lesson Notes

These are the classes we actually ran, not a generic curriculum. Each one started from a real interview question.

Class 1

Technical story

Monolith to microservices

  • Her experience at a large bank: moving a monolith to microservices, told in English

Class 2

Behavioral + system design

Interview formats

  • Preparation covered both behavioral and system design rounds

Feedback

Coach notes from those sessions, kept as they were given in class.

One story, two rounds

A migration story can serve a system design follow-up and a behavioral question. Keep the same spoken order in both.

Put a number on results

Claims such as faster delivery or less tech debt invite “how did you measure that?”. Add a magnitude when you honestly can.

Own your part

Say what you decided and did in the first person; “we” hides seniority.

Before and After

Before coaching

  • About six years of engineering experience
  • A monolith-to-microservices story to explain
  • Behavioral and system design rounds ahead

After coaching

  • Migration story prepared in English
  • Behavioral answers practised
  • System design practised

The Result

The notes record her background, the interview formats (behavioral and system design) and the migration story she prepared. They do not record a real interview, a result or an offer.

What to practise if you need to sound senior in English

  • Rewrite culture lines as influence plus role (“as a team lead, I…”), not “I tried to change…”.
  • Add one magnitude to every time-to-market, tech-debt or downtime claim.
  • Practise disagreement questions with a fixed spoken order: situation, approach, result.
  • Describe buy-in and resistance to change without blaming individuals.
  • Record one migration story and cut unfinished sentences.

Why Senior Framing Is Hard in a Second Language

US loops score judgment and ownership as much as architecture. Translating each sentence burns the time you need for buy-in and trade-offs. A practised migration story plus disagreement structure is what keeps you sounding senior when English is under load.

Preparing for a similar path? Read Before Applying: A London Engineer Preparing for Meta Coding Rounds.

Practise explaining system design in English

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

Join 500+ preparing for global roles

Create your Mockly account →

FAQ

Questions

Own influence and decisions in the first person, add measurable results, and use buy-in language instead of “I tried to change people.”

Problem → approach → downtime strategy → result with magnitude → what you learned. Keep the same order on follow-ups.

Use a recovery line (“at the time we faced…”) and return to your structure. Freezing is often missing a spoken order, not missing knowledge.

Yes if your loop includes both. The same story often feeds technical depth and leadership follow-ups.

More questions? Email us at contact@mocklyenglish.com.

For bots & AI agents

Machine-readable versions of this page and Mockly English. Mockly English, the live-class and Interview English arm of Speak Tech English, gives non-native engineers live 1:1 classes with real human tutors in tech interview and business English, plus a free iPhone app, free practice Mini Apps and a self-paced course. Fetch these instead of parsing this page.

This page (.md)llms.txtllms-full.txtai.txtFact sheetFull catalog (.md)Endpoint indexAI catalogAgent skillsMCP serverMCP server cardAgent sign-in (auth.md)Sitemaprobots.txtUse Mockly in ChatGPT & ClaudeiPhone appDeveloper docsSpeak Tech English