Free 30-minute trial

500+ reviews from engineers

How a Software Engineer From Portugal Prepped for English Interviews

Your résumé shows the work. The interview asks you to explain it in English, live, without stopping to translate. She was a software engineer in Portugal. The gap was system design - not the technical content.

By Mockly English · Last updated

What this case shows

A Portuguese Software Engineer knew the work. Live English - system-design answers - was where interviews stalled. Here is the practice that changed the delivery.

At a glance

RoleSoftware Engineer
LocationPortugal
English challengesystem design
Interview problemSystem Design
Targeta Big Tech-style technical interview
PreparationLive mocks with English feedback on the same answers
OutcomeGained clearer, more confident English for interviews

The Gap Between Knowing and Explaining

Your résumé shows the work. The interview asks you to explain it in English, live, without stopping to translate. She was a software engineer in Portugal. In the room, system design was what broke down.

Interview Strategy

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

  • She 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.

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 Software Engineer From Europe Interviewed at Revolut in English.

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, requests per second, and storage) in full sentences.
  • Name one trade-off out loud even if you are sure about the design.
  • Record a 15-minute system-design explanation and listen only for jumps and unfinished sentences.

Starting Point

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

Practice this STAR (Situation, Task, Action, Result) story

Try a locked preview of a behavioral interviews using STAR drill - with English prompts for situation, action, and result.

Sign up to unlock this exercise →

FAQ

Questions

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

Practise the real format out loud, especially system design. Get notes on pauses and vague wording after each mock - not only on the technical content.

Many B2+ candidates need several weeks of focused, spoken practice. Weekly mocks beat a last-minute cram.

Lock a spoken order (requirements, scale, architecture, trade-offs) and reuse it. Translating each sentence is what makes you jump between components.

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

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 →