Meta E3 Interview Guide

You receive a CoderPad link from the recruiter and have a few days to complete it. Both problems are graded by automated test cases and human review of code quality.

• Problem 1 is usually an easy/medium array, string, or hashmap problem.
• Problem 2 is a medium with a non-trivial twist, typically a graph, tree traversal, or two-pointer problem.

You are expected to finish both, with code that compiles, passes the visible cases, and handles obvious edge cases. Comments are not required but a short explanation in plain English at the top of each solution helps the human reviewer.

The recruiter walks through your background, target team, timeline, and salary band. This is also where they explain the loop and answer your questions.

There is no technical evaluation here, but two things can knock you out:

• Misalignment on level, if your resume reads E4+ but you applied for E3, recruiters may steer you to a different opening.
• Red-flag answers about why you're leaving your current role (anything that reads as conflict-averse or blame-shifting).

Identical format to onsite coding rounds, just one. A Meta engineer joins on video, shares a CoderPad link, and walks you through 1–2 problems.

The interviewer is looking for the same signals as the onsite coding rounds, so prep them as one unit. The bar is slightly lower (some companies use a "convert" model where TPS is purely a screen) but a clear miss here ends the loop.

Two problems, typically one warm-up easy/medium and one harder medium. Common categories: arrays, strings, hashmaps, two pointers, sliding window, BFS/DFS on trees and graphs.

The interviewer expects you to:

1. Spend the first 3–5 min restating the problem and asking clarifying questions.
2. Propose a brute-force approach, then optimize before coding.
3. Code the optimized solution, narrating as you go.
4. Dry-run your code on the example input.
5. Discuss complexity (time and space).

Same structure as Coding 1, but with a different interviewer and (usually) different problem categories, often DP, recursion, intervals, or harder graph problems. The two coding rounds are calibrated to give independent signal: a strong-strong is a clear hire, a strong-weak goes to debrief discussion.

Meta calls this the "Jedi" round. The interviewer probes:

• Conflict, how you handled disagreements with peers or managers.
• Failure, a project that went wrong and what you learned.
• Motivation, why Meta, why this role, what kind of work energizes you.
• Collaboration, how you give and receive feedback.

Have 3 polished stories prepared, each in STAR format, each demonstrating a different value (impact, ownership, growth). Use real numbers where possible.