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

How a London-Based ML Engineer Joined Meta After English Coaching

Ten years in ML was not the problem. Speaking about ML in English without spending all his energy on the words was - first in the interviews, then in team matching.

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 London ML engineer from Russia passed Meta's senior loop, used coaching for ML design, coding talk and team-matching English, and joined Meta.

At a glance

RoleML engineer (10 years)
RegionFrom Russia; living in London since 2022
Starting PointStruggled to speak about ML topics in interviews
TargetMeta - ML system design and coding, then team matching
OutcomeJoined Meta; onboarding English still in progress

Timeline

ML system design

Focus

Passed senior loop, then team matching

Outcome

Joined Meta

The Problem

He had ten years as an ML engineer and wanted to move to a big tech company. In interviews he struggled to speak about ML topics: he spent a lot of mental power processing the question and thinking about how to respond. Coding and ML system design were his primary focus; behavioral interviews were a secondary problem. Meta was already contacting him. His goal was to feel comfortable in the interview and stop thinking about what he was saying.

Before and After

Before coaching

  • He spent a lot of mental energy thinking about how to respond.
  • He struggled to speak about ML topics in interviews.
  • Behavioral interviews were a secondary concern.
  • After joining, Meta's internal jargon and structuring his speech were still hard.

After coaching

  • He had a written ML system-design structure for a 32-minute answer.
  • He had a LeetCode communication checklist.
  • He refined his team-matching questions and chose an ads team.
  • He kept working on English for onboarding: jargon, structure and recalling words.

Starting Point

He was from Russia and had lived in London since January 2022. He wanted to be ready in one to two months. He asked to solve a LeetCode problem before each class and to repeat words and phrases during the lesson, so vocabulary and phrases would come without effort.

The interview process

ML system design + codingPrimary coaching focus while Meta was scheduling
Senior loopPassed; waiting on team
Team matching30 minutes to collect signals; ads team chosen
JoinLeft his previous company; started at Meta on an ads team

What We Practised

Early sessions were technical mock interviews: ML system design and coding communication. After he passed, the work shifted to team matching - follow-up questions, fit and open headcount - and then to English for onboarding at Meta.

  • A 32-minute ML system design structure: clarification and scope, reframing as an ML problem, technical details (features, dataset, models, trade-offs, metrics, inference, productionising, A/B testing), practical challenges, then follow-up questions.
  • A LeetCode communication checklist: clarify, explain the solution, code live, walk a standard example and edge cases, state time and space complexity, then discuss.
  • Repeating words and phrases in class so they were ready under pressure.
  • Team-matching questions to find out which teams were a good fit and had open headcount.
  • After joining, Meta jargon, structuring speech and putting thoughts into words on unfamiliar topics.

Useful references along the way: STAR interview framework, Pronouncing numbers and metrics.

Session snapshot

Prep windowReady in 1–2 months (stated goal)
Loop resultPassed as senior; team match → ads
FocusML system design · coding talk · matching

Practice this scenario

Locked preview of the ML system-design scaffold he used - English prompts for each stage.

Sign up to unlock this exercise →

The Result

He passed Meta's interviews as a senior engineer, went through team matching, chose an ads team, and joined Meta. The notes then record the next English challenge: internal jargon, structuring his speech, and sometimes recalling words on topics he did not yet know well.

What to Practise

  • Learn one ML system design structure before your first mock and use it every time.
  • Practise team-matching questions as seriously as system design.
  • Repeat target phrases in the session, not only in your notes.
  • Expect onboarding to bring new vocabulary - keep practising after the offer.

Why This Matters for ML Engineers Targeting Meta

Meta ML loops reward a long spoken design: scope, model, metrics, production and follow-ups. Passing is not the last English test. Team matching and onboarding use the same skill on new vocabulary, so preparation that covers both sides of the offer is closer to the real job.

Preparing for a similar path? Read How an ML Engineer Passed Meta Interviews in English (IC5).

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 →

FAQ

Questions

Run the real clock with a fixed order: clarify, reframe as ML, then features, metrics, and production. Feedback should catch pauses and unfinished sentences, not only missing components.

You have a short window to ask questions and show fit. Prepare what you need to learn about headcount, the problem space, and how the team works day to day.

Often yes. Onboarding jargon and new topics reuse the same skill: saying a clear next sentence without long mid-answer translation.

No. Clarity and structure matter most. A light accent is fine if they can follow your metrics and trade-offs.

More questions? Email us at contact@mocklyenglish.com.

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