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

Before Applying: A London Engineer Preparing for Meta Coding Rounds

He had not applied yet. Referrals to Meta were available, and he wanted LeetCode mocks in the real Meta format.

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 engineer with Meta referrals asked for coding mocks in Meta's two-mediums-in-45-minutes format, plus design and behavioral, before applying.

At a glance

RoleSoftware engineer (senior target; also considering quant)
RegionLondon (9.5 years)
Starting PointLots of LeetCode; top 100 Meta questions studied; not applied yet
TargetMeta (referrals), Amazon, Apple
OutcomeNo result yet - notes end before he applied

Timeline

Meta + Amazon + Apple

Focus

2 mediums / 45 minutes

Outcome

Senior SWE target

The Problem

He had lived in London for nine and a half years and had people who could refer him to Meta, but he had not applied yet. He had done a lot of LeetCode and had studied the top 100 questions asked at Meta by heart. The intake plan: mock LeetCode rounds in Meta's format - two mediums in 45 minutes - including a problem he had seen before, without the coach giving him the whole solution. System design and behavioral were on the list too, and quant trading roles were a parallel option.

What We Practised

Live coding practice session: a Python solution to the Add Two Numbers linked-list problem in a shared editor, with coach and student on a video call
Example of a live coding practice session - narrating a linked-list solution in English while the tests run.

The intake set the format: a problem he might have seen, no full solution from the coach, and English on the narration. System design and behavioral were on the same list.

  • Meta-style coding mocks: two mediums, forty-five minutes, thinking aloud.
  • System design, starting from Hello Interview.
  • Behavioral stories that focus on delivering value rather than people management.
  • Practice that withholds the complete answer, so recognising a problem does not replace explaining it.

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

Before and After

Before coaching

  • He had not applied yet, though people could refer him to Meta.
  • He had done a lot of LeetCode and memorised the top 100 Meta questions.
  • System design, behavioral and LeetCode were all on the list.
  • Targets: senior engineer roles at Amazon, Meta and Apple, plus quant trading.

After coaching

  • Plan: mock LeetCode rounds that stop short of the full solution.
  • Plan: Meta timing - two mediums in 45 minutes.
  • Plan: Hello Interview as the starting resource.
  • Plan: stories about delivering value, not people management.

Starting Point

He was aiming at FAANG - Amazon, Meta and Apple - at senior engineer level, with quant trading roles as another option. His notes say no people-management angle in his answers and that delivering value is very important. Hello Interview was the suggested place to start.

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 at the intake, before any application. They record the plan - Meta-format coding mocks, system design and behavioral - not how the mocks went or any interview result.

Advice for Engineers Preparing Meta Coding Rounds

  • 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 London-Based ML Engineer Joined Meta After English Coaching.

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

Time two mediums, narrate as you go, and do not look up the full solution. Feedback should target pauses and skipped complexity talk.

If referrals are waiting, get a few honest mocks first - then apply. Endless lists without a live round is stalling.

Yes if the full loop includes them. Coding-only prep leaves the later rounds untested in English.

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

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