On this page

Case studies

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

RoleSoftware engineer (senior target; also considering quant)
RegionLondon (9+ years)
Starting PointHeavy LeetCode; spoken delivery untested
TargetMeta (referrals), Amazon, Apple
OutcomeMocks for Meta’s 2-mediums-in-45-minutes format

Timeline

Meta + Amazon + Apple

Focus

2 mediums / 45 minutes

Outcome

Senior SWE target

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

I have seen the top Meta questions. I still need to solve a familiar problem out loud without freezing.

Software engineer · Meta interview prep

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 45 minutes with two mediums. System design and behavioral were on the list too. Quant roles were a parallel track. The risk was sending the referral cold, with silent LeetCode and no spoken reps.

What We Practised

The hour looked like Meta coding: a problem he might have seen, no full solution from the coach, English on the narration. System design and behavioral rotated in so the first onsite would not be the first time he spoke those formats.

  • Meta-style coding: two mediums, 45 minutes, think-aloud
  • System design with a value-first explanation
  • Behavioral without a people-manager story
  • Practice that withholds the complete answer

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

Before and After

Before coaching

  • Had not applied despite referrals
  • LeetCode volume high; live English untested
  • Risk of being given the whole solution in practice — useless for Meta
  • Behavioral and design still secondary to coding anxiety

After coaching

  • Mocks that stop short of the full solution
  • Two-medium timing with spoken reasoning
  • System-design and behavioral slots on the same calendar
  • Referral used when the format felt familiar

Starting Point

FAANG or similar: Amazon, Meta, Apple, senior engineer. No people-management pitch — 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 round, not a tutorial.

Session snapshot

Meta coding format2 mediums in 45 minutes
StatusReferrals available; applications not sent yet
TargetsMeta · 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.

Create your Mockly account →

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.

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 manager stories for a senior IC loop?

Not if you are not a manager. Prepare delivery and impact stories instead.

Is system design still required if I am a strong coder?

At Meta-style senior loops, yes. Practise it in English even if coding is the fear.