Meta coding interview: reading the Reddit reports

You are reading threads to find out what the Meta coding round is really like, and the volume makes it hard to tell a pattern from one bad week. This section names the complaints that recur across accounts and explains what causes each, so you can tell which apply to you.

• Two problems, not one. Candidates who budgeted a single puzzle run out of room when the second prompt lands.
• No run button. People used to LeetCode submit messages freeze when they have to be the interpreter.
• Silence is visible. The pad shows pauses and deletions, and interviewers write notes while you think.
• Stale lists. A prompt copied from a thread months ago rarely reappears verbatim.

None of those are secrets. They follow from a 45-minute shared pad, not from anything adversarial. The structural walkthrough of Meta's stages sits on the company interviews topic hub.

Meta hires into specific teams, and a team's interviewer, level, and problem set are not a single shared exam. Two people interviewing for adjacent E4 roles can sit in honest, opposite threads in the same month. One got two array problems and time left. The other got a graph follow-up at minute 30 and felt ambushed.

The sampling makes that worse. People post after a rejection or a strange round far more often than after a pad that went normally, so the aggregate reads harsher than the base rate. Phone-screen reports and loop reports also get mixed in the same thread, which produces advice that is true for one stage and useless for the other.

The practical move is to treat a reported prompt as a family, not a script, and to ask your recruiter what the coding round looks like for your level.

Two things, and both cost preparation time. Question lists first: interviewers choose their own problems, so a list posted last quarter tells you the categories and not the questions. Preparing the underlying patterns transfers. Memorising posted items does not survive the first follow-up.

Second, the tooling folklore. Threads argue about overlays, extra monitors, and whether anyone can tell. A shared pad is already a shared surface. If you are asked to share your screen, anything on that screen is in the share. Company-managed or proctored devices are out of scope for any assist tool, whatever a comment claims.

An E5 candidate spent a week memorising prompts copied from Reddit. In the phone screen the interviewer opened a different graph problem in the same family. She recovered only because she had practised narrating BFS trade-offs, not because she had seen that prompt. The threads had not been lying. They had been unrepresentative.

The useful signal is format, not content. Candidates describe the shape of the hour accurately: two problems, a plain pad, cameras on, narration graded. That tells you what to rehearse. Rehearse it as speech, on a 45-minute timer, because the failure mode people describe is freezing rather than not knowing.

Running that against an AI interviewer works on the mock interview page.

For live spoken rounds around the pad, SubcueAI ships two surfaces. The native macOS and Windows app captures system audio plus your microphone into a floating local overlay. A browser extension Side Panel does live assist for a meeting tab on Chromium browsers, capturing only that tab's audio. No meeting bot joins the call, and nothing is injected into the meeting page. The limit is the pad itself and any screen share. What is captured and stored elsewhere is documented on the security page.