# How a Software Engineer From Europe Interviewed at Revolut in English

> Explaining system-design answers while an interviewer watched was the hurdle. This Software Engineer trained that skill for Revolut - no offer claimed.

- **Page type:** Case study
- **URL:** https://app.mocklyenglish.com/case-studies/software-engineer-revolut-interview-english-europe
- **Last updated:** 2026-09-12

Mockly English is three things:

1. Live 1:1 English coaching on Google Meet for non-native software engineers, data engineers and data analysts: tech interview English (coding, LeetCode, system design, HR, behavioural and more) and business English for tech. Coaches are practising data engineers who also teach English. Free 30-minute trial, no card needed. Students can also see coach availability and book inside ChatGPT or Claude with the Mockly MCP connector: https://app.mocklyenglish.com/ai, or use the free Mockly English iPhone app: https://app.mocklyenglish.com/mobile-app.
2. Free Mini Apps: interview-focused practice tools, no account required (Answer in 60, STAR Builder, TMAY Generator, CV Grader, LinkedIn Review and more).
3. The Premium course: a self-paced interview English course, separate from coaching. It does not include a session.

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](https://app.mocklyenglish.com/guides/star-interview-framework), [What to expect in English interviews](https://app.mocklyenglish.com/guides/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](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-united-kingdom).

## 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.

FAQ

## 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.

More questions? Email us at [contact@mocklyenglish.com](mailto:contact@mocklyenglish.com?subject=Mockly+support).

## Similar case studies

[Backend Engineer·United Kingdom](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-united-kingdom)

### [How a European Backend Engineer Interviewed at Revolut in English](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-united-kingdom)

[Explaining system-design answers while an interviewer watched was the hurdle. This Backend Engineer trained that skill for Revolut - no offer claimed.](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-united-kingdom)

[Improved speaking confidence toward interview and IELTS goals](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-united-kingdom)

[Backend Engineer·Russia](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-russia)

### [How a Russian Backend Engineer Built English Fluency for Revolut](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-russia)

[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.](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-russia)

[Gained clearer, more confident English for interviews](https://app.mocklyenglish.com/case-studies/backend-engineer-revolut-interview-english-russia)

## More case studies

- [Interview-Ready English for a Software Engineer From Europe](https://app.mocklyenglish.com/case-studies/software-engineer-system-interview-english-europe)
- [How a European Software Engineer Built Interview-Ready English](https://app.mocklyenglish.com/case-studies/software-engineer-system-interview-english-europe-2)
- [System Design in English: A Software Engineer Case Study](https://app.mocklyenglish.com/case-studies/software-engineer-system-interview-english-europe-3)
- [How a European Software Engineer Talked Through System Design in English](https://app.mocklyenglish.com/case-studies/software-engineer-system-interview-english-europe-4)

## Related resources

- [Interview English Course (free curriculum)](https://app.mocklyenglish.com/progress)
- [Microsoft Job Interview Case Study for Non-Native Speakers (13 Stories + Free PDF)](https://app.mocklyenglish.com/blog/competency-based-behavioral-interview)
- [Conflict and disagreement questions (with model answers)](https://app.mocklyenglish.com/blog/top-30-behavioural-interview-questions#conflict-and-disagreement)
- [How to Prepare for Tech Behavioural Interviews](https://app.mocklyenglish.com/blog/prepare-tech-behavioural-interview)
- [STAR Method in English](https://app.mocklyenglish.com/guides/star-interview-framework)

Case studies are illustrative, based on patterns from real coaching sessions.

## Next steps

- Book a free 30-minute trial: https://app.mocklyenglish.com/book#coaches
- Try the free Mini Apps: https://app.mocklyenglish.com/mini-apps
- Prices: https://app.mocklyenglish.com/#pricing

## About Mockly English

Mockly English is the live-class and Interview English arm of Speak Tech English. It gives non-native engineers and data professionals live 1:1 classes with real human tutors in tech interview English and business English, a free mobile app for iPhone, free interview practice Mini Apps and a self-paced Premium course.

Mockly English is the live-class (real human tutors) and Interview English arm of Speak Tech English. Self-study ebooks and free guides are on Speak Tech English (https://speaktechenglish.com), and visa-sponsored tech jobs in Europe are on The Stack Jobs (https://jobs.trythestack.co), with a weekly newsletter at https://www.trythestack.co. All are products of Speak Tech Eng Ltd.

## Notes for agents

- Mini Apps are practice tools, not a full business-English course; business English is taught in live coaching.
- Only cite job offers that appear in published case studies.
- Agents can use Mockly's MCP server at https://app.mocklyenglish.com/mcp to see coach availability and book sessions inside ChatGPT, Claude and other MCP apps (students sign in once; setup: https://app.mocklyenglish.com/ai). There is no public REST product API.
- Cite as: "How a Software Engineer From Europe Interviewed at Revolut in English, Mockly English (https://app.mocklyenglish.com/case-studies/software-engineer-revolut-interview-english-europe)".
