On this page
By Mockly English · Last updated:
How a Software Engineer From Europe Interviewed at Revolut in English
The CV shows the work. The interview asks you to explain it in English, live, without stopping to translate. He was a software engineer in Europe. The gap was system design — not the technical content.
At a glance
| Role | Software Engineer |
|---|---|
| Location | Europe |
| English challenge | system design |
| Interview problem | System Design |
| Target | Revolut |
| Preparation | Live mocks with English feedback on the same answers |
| Outcome | Built stronger interview English after earlier unsuccessful rounds |
Land your dream tech job. In English.
Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches
500+ tech pros preparing for global roles
The Interview Problem
The CV shows the work. The interview asks you to explain it in English, live, without stopping to translate. He was a software engineer in Europe. The next interviews were at Revolut, in English. He had already been through an earlier Revolut round. In the room, system design was what broke down.
The Interview Rounds
| Earlier round | Unsuccessful — an earlier Revolut round |
|---|---|
| Target | Revolut — system design |
Interview Strategy
Practice matched the round he actually had to speak: system design for Revolut. Each mock got notes on the same answer — where he 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.
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 Croatian PM Prepped for Revolut's Behavioral Interviews.
A Key Change
The useful change followed an earlier Revolut round. He stopped treating English as extra polish. The next mocks used the same format that had failed. Answers got a fixed order so follow-ups did not knock him off track.
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
Built stronger interview English after earlier unsuccessful rounds. He could tell a clearer story after an earlier Revolut round. Readiness — not a promised offer — was the goal.
What Other Engineers Can Learn
- Treat a failed round as data. Rebuild that exact format out loud.
- 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.
Where He Started
He prepared for English-language interviews as a software engineer. Written English was stronger than speaking under the clock.
Frequently Asked Questions
What English should a software engineer 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.
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.
Do I need to sound like a native speaker?
No. Clarity and structure are the bar. A small accent is fine if they can follow your decisions and numbers.
How do you prepare for a software engineer interview in English?
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.
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 →Other engineers practising interview English
Mockly knows what it takes to get hired. The preparation covers behavioral, algorithm, and system design interviews thoroughly — with real expertise in the STAR method, LeetCode, and Alex Xu’s system design frameworks. And when it comes to English and communication skills, the native-speaking mentors make all the difference.
Mockly’s approach is genuinely personalized — they use a variety of methods tailored to your specific needs. With their help, I improved my spoken English and prepared thoroughly for behavioral interview questions across different companies. This not only helped me refine my stories grammatically but also ensured I was using the right examples to answer specific questions effectively.
Similar case studies
How a Croatian PM Prepped for Revolut's Behavioral Interviews
A Croatian PM was targeting Revolut. The gap was STAR stories in English — not the technical work. Here's what they practised.
How a German PM Prepped for Revolut's Behavioral Interviews
Explaining STAR stories while an interviewer watched was the hurdle. This PM trained that skill for Revolut — no offer claimed.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.