How a Software Engineer From Europe Interviewed at Revolut in English
Your résumé 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.
What this case shows
Explaining system-design answers while an interviewer watched was the hurdle. This Software Engineer trained that skill for Revolut - no offer claimed.
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 |
The Interview Problem
Your résumé 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.
- He 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 European Backend Engineer Interviewed at Revolut in English.
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, requests per second, and 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.
Learning paths
Practise in the course
Start with your introFAQ
Questions
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
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 European Backend Engineer Interviewed at Revolut in English
Explaining system-design answers while an interviewer watched was the hurdle. This Backend Engineer trained that skill for Revolut - no offer claimed.
How a Russian Backend Engineer Built English Fluency for Revolut
A Russian backend engineer was targeting Revolut. The gap was spoken interview English - clear terms under pressure - not the technical work. Here is what she practised.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.