How a European Backend Engineer Interviewed at Revolut in English
Interviewers are not grading your accent. They need to follow your reasoning in English. She was a backend engineer in London. 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 Backend Engineer trained that skill for Revolut - no offer claimed.
At a glance
| Role | Backend Engineer |
|---|---|
| Location | London |
| English challenge | system design |
| Interview problem | System Design |
| Target | Revolut |
| Preparation | Live mocks with English feedback on the same answers |
| Outcome | Improved speaking confidence toward interview and IELTS goals |
The Problem
Interviewers are not grading your accent. They need to follow your reasoning in English. She was a backend engineer in London. The next interviews were at Revolut, in English. In the room, system design was what broke down.
Then vs Now
Before coaching
- Reached for words mid-answer and translated from a first language.
- Knew the design; lost structure when explaining it live.
After coaching
- Used a small set of precise terms instead of long, vague descriptions.
- Walked requirements, components, and trade-offs in a fixed order.
What We Practised
Practice matched the round she actually had to speak: system design for Revolut. 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.
A Key Change
The shift showed up in a timed system-design mock. She knew the architecture but jumped between components. A fixed spoken sequence - requirements, then scale, then architecture, then bottlenecks - was repeated until follow-ups stayed inside that order.
What to Practise
- 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.
After the Coaching
Improved speaking confidence toward interview and IELTS goals. She could explain the work more clearly when questions got hard. That readiness was the goal - not a promised job offer.
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 Russian Backend Engineer Built English Fluency for Revolut.
Where She Started
She prepared for English-language interviews as a backend engineer. English started around B2. Written English was stronger than speaking under the clock.
Session snapshot
| Focus | System Design · Behavioral · Coding |
|---|---|
| Target | Revolut |
| Starting level | B2 |
| IELTS speaking | Also in view |
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 →Learning paths
Practise in the course
Start with your introPractise 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
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Other engineers practising interview English

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.

I’ve had the pleasure of practicing English with Mockly and I truly appreciate the progress I’ve made. I highly recommend their services to professionals in tech and beyond. I particularly enjoy the teaching style and the philosophy behind it: “If you enjoy the process, you’ll get it.” The personalized learning plans make every session practical and useful. Their hands-on knowledge and genuine interest in the world of technology will genuinely boost your English skills.
Similar case studies
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.
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.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.