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.
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
| Role | ML engineer (10 years) |
|---|---|
| Region | From Russia; living in London since 2022 |
| Starting Point | Struggled to speak about ML topics in interviews |
| Target | Meta - ML system design and coding, then team matching |
| Outcome | Joined 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 + coding | Primary coaching focus while Meta was scheduling |
|---|---|
| Senior loop | Passed; waiting on team |
| Team matching | 30 minutes to collect signals; ads team chosen |
| Join | Left 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 window | Ready in 1–2 months (stated goal) |
|---|---|
| Loop result | Passed as senior; team match → ads |
| Focus | ML 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).
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
Other engineers practising interview English

Mockly knows what it takes to get hired. The preparation covers behavioral, algorithm, and system design interviews thoroughly - with real expertise in the STAR method, LeetCode, and Alex Xu’s system design frameworks. And when it comes to English and communication skills, the native-speaking mentors make all the difference.

Mockly has been the best investment I’ve made in the past year. The mentors don’t just have a deep knowledge of the language - they bring extensive experience in the IT industry. They understand the tech job market and are well-versed in modern engineering practices and the culture of top companies. Sessions aren’t just about improving your English; they’re an opportunity to sharpen your soft skills, gain valuable insights beyond engineering, and become a stronger communicator overall. Highly recommended.
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
Similar case studies
How an ML Engineer Passed Meta Interviews in English (IC5)
Case study: an ML engineer in Switzerland was held back by English fluency, not tech skills, at Meta, Google and Shopify. He got the Meta job (IC5).
How a Russian ML Engineer Landed an Offer at Meta With English Coaching
A Russian ML engineer could do the work. Spoken English under pressure - especially system design - was the gap. Coaching focused on clear spoken designs; then Meta moved forward.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.