Black Friday sale: 25% off all coaching sessions and packs. See prices

How a Belgrade Tech Lead Practised System Design Interviews in English

HR interviews were not the problem. Solving algorithm and system design problems out loud in English was.

By Mockly English · Last updated Based on real coaching sessions. Names and some identifying details are changed to protect student privacy.

What this case shows

A Belgrade senior engineer and tech lead was fine in HR rounds but struggled to solve problems out loud in English. Coaching targeted LeetCode and design.

At a glance

RoleSenior SWE / architect / tech lead (pivoting toward management)
RegionBelgrade, Serbia
Starting PointHR fine; struggled to solve problems out loud in English, worse under stress
TargetEnglish-speaking role (London / Spain / Cyprus / Dubai)
InterviewsSeveral live processes, including Revolut and Perplexity

Timeline

Senior / tech lead

Focus

Belgrade

Outcome

Design + LeetCode in English

The Problem

He had eight or nine years as a software engineer and worked as a senior engineer, architect and tech lead. He was reading books like The Manager's Path and The Staff Engineer's Path and wanted to pivot into management. HR interviews were not the problem. Algorithm and system design problems were: he struggled to solve problems out loud and could not focus on delivering his solution in English, and his English got worse under stress. He wanted to focus on everything that influences the result of the interview.

What We Practised

System design practice session on video: a distributed ID generator with timestamp, datacenter ID, machine ID and sequence fields
Explaining a distributed ID generator design out loud - a typical system design practice question.

He wanted to focus on whatever would change the result of the interview. That meant technical rounds first - algorithms and system design out loud in English - with behavioral questions as a smaller part.

  • LeetCode problems, explained out loud in English.
  • System design practice using chapters such as "Design YouTube" and "Design Google Drive".
  • Some behavioral interview questions, relevant to his move toward management.
  • Preparation alongside live interview processes with several companies.

Useful references along the way: What to expect in English interviews, STAR interview framework.

Starting Point

He was based in Belgrade. His main goal was an English-speaking job, ideally in London, Spain, Cyprus or Dubai. He was focused on LeetCode problems and wanted to add system design and some behavioral questions. Suggested system design study material included chapters on designing YouTube and Google Drive. He had already started interview processes with several companies, so coaching ran alongside live interviews.

Before and After

Before coaching

  • HR interviews were not a problem for him.
  • He struggled to solve problems out loud in English.
  • He said his English was bad when stressed.
  • He was already in several interview processes.

After coaching

  • He practised LeetCode problems out loud in English.
  • He used system design chapters as spoken practice material.
  • He added some behavioral interview questions.
  • He kept interviewing, including with Revolut and Perplexity.

Session snapshot

Experience8–9 years; senior / tech lead
Weak areaAlgorithms + system design out loud in English
Live processesRevolut, Perplexity, others in notes

The Result

The notes do not record a Google interview or an offer. They record a senior engineer and tech lead in Belgrade who was comfortable in HR rounds but struggled to solve problems out loud in English, with several interview processes running at once. He had an interview with Revolut and was waiting for feedback, and a Perplexity interview was scheduled for 30 May.

What to Practise

  • Practise solving out loud before the first technical round, not after HR.
  • Turn design chapters into timed spoken runs.
  • Use the same spoken structure at every company - do not reinvent your English for each process.
  • Practise under some time pressure so stress is not a surprise on the day.

Why This Matters for Tech Leads in Belgrade Interviewing in English

Technical interview loops usually include a spoken design round and coding with narration. A tech lead who is calm in HR rounds can still lose a senior role if stress makes the English fall apart mid-solution. The fix is practising the hard round in English until the structure holds.

Preparing for a similar path? Read How a Lead Backend Engineer Prepped for FAANG Interviews in English.

FAQ

Questions

Timed spoken designs and LeetCode narration. HR success does not transfer.

Say a chapter as a mock. Reading is not the skill the round grades.

Reuse one spoken structure across companies. Change the problem, not the English habits.

No. Clarity and structure matter most. A light accent is fine if they can follow your solution.

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

Create your Mockly account →

For bots & AI agents

Machine-readable versions of this page and Mockly English. Mockly English, the live-class and Interview English arm of Speak Tech English, gives non-native engineers live 1:1 classes with real human tutors in tech interview and business English, plus a free iPhone app, free practice Mini Apps and a self-paced course. Fetch these instead of parsing this page.

This page (.md)llms.txtllms-full.txtai.txtFact sheetFull catalog (.md)Endpoint indexAI catalogAgent skillsMCP serverMCP server cardAgent sign-in (auth.md)Sitemaprobots.txtUse Mockly in ChatGPT & ClaudeiPhone appDeveloper docsSpeak Tech English