On this page

Case studies

By Mockly English · Last updated:

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.

At a glance

RoleBackend Engineer
LocationLondon
English challengesystem design
Interview problemSystem Design
TargetRevolut
PreparationLive mocks with English feedback on the same answers
OutcomeImproved speaking confidence toward interview and IELTS goals
7-Day Free Trial

Land your dream tech job. In English.

Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches

Start freeNo card needed
MemberMemberMember

500+ tech pros preparing for global roles

Courses · Coaching · Mock Interviews

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
  • Stories ran long and lost the result
  • Knew the design; lost structure when explaining it live
  • Solved quietly, then tried to explain after the code

After coaching

  • Retrieved a small set of precise terms instead of long approximations
  • STAR stories with a clear action and a result said early
  • Walked requirements, components, and trade-offs in a fixed order
  • Thought aloud: constraints, approach, complexity, then code

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.

  • 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, QPS, storage) in full sentences.
  • Name one trade-off out loud even if you are sure about the design.
  • Record a 15-minute walk 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 Croatian PM Prepped for Revolut's Behavioral Interviews.

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

FocusSystem Design · Behavioral · Coding
TargetRevolut
Starting levelB2
IELTS speakingAlso in view

Practice this STAR story

Try a locked preview of a behavioral / STAR drill — with English prompts for situation, action, and result.

Sign up to unlock this exercise →

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 →

Frequently Asked Questions

What English should a backend 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.

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

How long does it take to feel ready as a backend engineer?

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