Meta interview questions for engineers

CANDIDATE-REPORTED · INDEPENDENT SYNTHESIS

What candidates report about the interview

4 reviewed signals

Use these reports to choose what to rehearse, not to predict a fixed loop. Formats vary by role, team, and date; confirm your current process with the recruiter. Frontier Rehearsal is independent and not company-endorsed.

Process signalsReported stages, formats, timing, and role-specific variations.3

Candidate reports describe the Meta E6 technical screen as roughly 20 minutes of behavioural questions, an easy warm-up coding problem, a medium coding problem with follow-ups, and a short window for candidate questions.
Open permanent link
Candidate reports describe Meta's product-manager onsite as testing core product sense plus an analytical interview with heavy emphasis on metrics and experimentation, even for candidates who applied to AI PM roles.
Open permanent link
Candidates describe the Meta software-engineer loop as consistently including coding, system design and behavioural rounds, with recent reports also mentioning an AI-focused round.
Open permanent link

Candidate briefingsCompact, independently written summaries of fuller candidate timelines.1

According to a candidate report, the Meta onsite loop comprises two coding rounds, two system-design rounds and one behavioural round, and a mixed signal in one round can trigger a follow-up round.
Open permanent link

Evidence reviewed Nov 12, 2026. Reports can become stale.

Question groups

Topics

Independent and not affiliated with the companies represented. Collected material does not predict future interview questions.

2 questions

Every question has a public brief with the task, constraints, and follow-ups. Labels describe interactive practice access.

Free practice

Topic tags
Python
Concurrency

MetaCoding

Python codingWebAssembly + public tests

Reported interview periodNot available

Per-function exclusive runtime from a call log

A single thread records start and end events for nested function calls. For each function id, work out how many time units it actually spent running, excluding the units spent inside calls it made.

Practice focusRequirements - Line one is the number of functions; ids run from 0 to count - 1 and every id appears at least once. Line two is the number of event lines. - Each remaining line is <id :<start|end :<timestamp with integer fields. Events are chronological and properly nested on one thread. - An end timestamp is inclusive: the unit at that timestamp belongs to the call that is ending, so it contributes timestamp - previous + 1 units. - When a call begins on top of a running call, credit the units since the previous boundary to the caller.…

New public brief

Topic tags
Python
Algorithms
Concurrency

MetaCoding

Python codingWebAssembly + public tests

Reported interview periodJan 2026–Sep 2026

Shortest maze route with collected keys

Guide a walker from the start cell to the exit of a character grid, where locked doors stay shut until the matching key has been picked up, and report the fewest single-cell moves needed.

Practice focusRequirements - Line 1 gives rows cols . The next rows lines each contain exactly cols characters. - . is open floor, blocks movement, S is the start, and E is the exit. - Lowercase letters a through f are keys. Uppercase A through F are doors that require the key with the same letter. - E marks the exit and is never read as the door for key e . - A collected key is kept permanently, so the walker may revisit a cell with a different set of keys. - Each move changes the row or column by one. Entering a door without its key is not allowed.…

Loading the question catalog…

CANDIDATE-REPORTED · INDEPENDENT SYNTHESIS

What candidates report about the interview

4 reviewed signals

Use these reports to choose what to rehearse, not to predict a fixed loop. Formats vary by role, team, and date; confirm your current process with the recruiter. Frontier Rehearsal is independent and not company-endorsed.

Process signalsReported stages, formats, timing, and role-specific variations.3

Candidate reports describe the Meta E6 technical screen as roughly 20 minutes of behavioural questions, an easy warm-up coding problem, a medium coding problem with follow-ups, and a short window for candidate questions.
Open permanent link
Candidate reports describe Meta's product-manager onsite as testing core product sense plus an analytical interview with heavy emphasis on metrics and experimentation, even for candidates who applied to AI PM roles.
Open permanent link
Candidates describe the Meta software-engineer loop as consistently including coding, system design and behavioural rounds, with recent reports also mentioning an AI-focused round.
Open permanent link

Candidate briefingsCompact, independently written summaries of fuller candidate timelines.1

According to a candidate report, the Meta onsite loop comprises two coding rounds, two system-design rounds and one behavioural round, and a mixed signal in one round can trigger a follow-up round.
Open permanent link

Evidence reviewed Nov 12, 2026. Reports can become stale.

Question groups

Topics

Independent and not affiliated with the companies represented. Collected material does not predict future interview questions.

2 questions

Every question has a public brief with the task, constraints, and follow-ups. Labels describe interactive practice access.

Free practice

Topic tags
Python
Concurrency

MetaCoding

Python codingWebAssembly + public tests

Reported interview periodNot available

Per-function exclusive runtime from a call log

A single thread records start and end events for nested function calls. For each function id, work out how many time units it actually spent running, excluding the units spent inside calls it made.

Practice focusRequirements - Line one is the number of functions; ids run from 0 to count - 1 and every id appears at least once. Line two is the number of event lines. - Each remaining line is <id :<start|end :<timestamp with integer fields. Events are chronological and properly nested on one thread. - An end timestamp is inclusive: the unit at that timestamp belongs to the call that is ending, so it contributes timestamp - previous + 1 units. - When a call begins on top of a running call, credit the units since the previous boundary to the caller.…

New public brief

Topic tags
Python
Algorithms
Concurrency

MetaCoding

Python codingWebAssembly + public tests

Reported interview periodJan 2026–Sep 2026

Shortest maze route with collected keys

Guide a walker from the start cell to the exit of a character grid, where locked doors stay shut until the matching key has been picked up, and report the fewest single-cell moves needed.

Practice focusRequirements - Line 1 gives rows cols . The next rows lines each contain exactly cols characters. - . is open floor, blocks movement, S is the start, and E is the exit. - Lowercase letters a through f are keys. Uppercase A through F are doors that require the key with the same letter. - E marks the exit and is never read as the door for key e . - A collected key is kept permanently, so the walker may revisit a cell with a different set of keys. - Each move changes the row or column by one. Entering a door without its key is not allowed.…

Meta interview questions for engineering roles

Meta interview questions for engineering roles

What candidates report about the interview

Per-function exclusive runtime from a call log

Shortest maze route with collected keys

What candidates report about the interview

Per-function exclusive runtime from a call log

Shortest maze route with collected keys