On this page
By Mockly English · Last updated:
How a London Software Engineer Prepped for Meta Coding Rounds
He had not applied yet. He was already training as if the Meta referral were this week.
At a glance
| Role | Software engineer (senior target; also considering quant) |
|---|---|
| Region | London (9+ years) |
| Starting Point | Heavy LeetCode; spoken delivery untested |
| Target | Meta (referrals), Amazon, Apple |
| Outcome | Mocks for Meta’s 2-mediums-in-45-minutes format |
Timeline
Meta + Amazon + Apple
Focus
2 mediums / 45 minutes
Outcome
Senior SWE target
Land your dream tech job. In English.
Practice technical, behavioral & system design interviews with interactive lessons and native-speaking coaches
Join 500+ preparing for global roles
“I have seen the top Meta questions. I still need to solve a familiar problem out loud without freezing.”
The Problem
He had lived in London for nine and a half years and had people who could refer him to Meta. He had not applied. He had memorised a large set of Meta-tagged problems and still needed the English to solve a problem he had seen before — out loud — in forty-five minutes with two mediums. System design and behavioral were on the list too. Quant roles were a parallel option.
What We Practised
The hour looked like Meta coding: a problem he might have seen, no full solution from the coach, and English on the narration. System design and behavioral rotated in so the first onsite would not be the first time.
- He practised Meta-style coding: two mediums, forty-five minutes, thinking aloud.
- He practised system design with a value-first explanation.
- He practised behavioral stories without a people-manager narrative.
- He used practice that withholds the complete answer so recognition does not replace narration.
Useful references along the way: What to expect in English interviews, STAR interview framework.
Before and After
Before coaching
- He had not applied despite referrals.
- LeetCode volume was high, but live English was untested.
- There was a risk of being given the whole solution in practice — useless for Meta.
- Behavioral and design were still secondary to coding anxiety.
After coaching
- Mocks stopped short of the full solution.
- He practised two-medium timing with spoken reasoning.
- System-design and behavioral slots sat on the same calendar.
- He could use the referral when the format felt familiar.
Starting Point
He was aiming at FAANG or similar: Amazon, Meta, Apple, at senior engineer level. He did not want a people-management pitch — he wanted to deliver value. He wanted mocks that did not hand him the full solution. Hello Interview and similar resources were already in the mix. Coaching had to feel like the real Meta round.
Session snapshot
| Meta coding format | 2 mediums in 45 minutes |
|---|---|
| Status | Referrals available; applications not sent yet |
| Targets | Meta · Amazon · Apple · senior / quant |
The Result
The notes stop before an offer — he had not applied yet. The work was to make the Meta coding round, and the design and behavioral rounds around it, something he had already done in English. That is the honest outcome: readiness before the referral is used.
What He Would Do Differently
- Do not wait to apply until every list is finished.
- Practise seen problems out loud — recognition is not narration.
- Refuse practice that spoils the solution.
- Book design and behavioral mocks before the onsite, not after the coding screen.
Why This Matters for London Engineers Targeting Meta
Meta coding rounds grade communication as much as patterns. Living in London does not automatically produce that skill. Referrals expire in quality if the first live round is also the first spoken round.
Preparing for a similar path? Read How a UAE-Based Backend Engineer Prepped for Meta in English.
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
Frequently Asked Questions
How do you train for Meta’s two-medium coding interview in English?
Time two mediums, narrate as you go, and do not look up the full solution. Feedback should target pauses and skipped complexity talk.
Should I apply to Meta before I feel ready?
If referrals are waiting, get a few honest mocks first — then apply. Endless lists without a live round is stalling.
Do I need system design and behavioral before the coding screen?
Yes if the full loop includes them. Coding-only prep leaves the later rounds untested in English.
Do I need to sound like a native speaker?
No. Clarity and structure matter most. A light accent is fine if they can follow your reasoning.
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.
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 UAE-Based Backend Engineer Prepped for Meta in English
A backend engineer in the UAE was interviewing at Meta, Amazon, and Adobe. Coaching focused on behavioral English — then he joined Revolut.
How a Switzerland-Based ML Engineer Passed Meta's Interview in English
A Zurich MLOps engineer had already passed Meta’s coding screen. Fluency under pressure was the gap. Coaching focused on ML system design and behavioral rounds — then he got the offer.
More case studies
Related resources
Case studies are illustrative, based on patterns from real coaching sessions.