Jobra
🐞Step 1 of Jobra:AI Debugging Rounds
DSA+AIPreparing you for both.
JOBRA · AI DEBUG ROUND (PREVIEW)sum.cpp
// buggy snippet
int total(vector<int>& a, int n) {
    int sum = 0;
    for (int i = 0; i <= n; i++) { // 🐞        sum += a[i];
    }
    return sum;
}
A real codebase. A real bug. You + AI.

Jobra drops you into a broken repo. Find it, fix it, ship it. AI helps you debug like on the job.

Prompt:Correct the loop condition
Tap 'Let Jobra fix it' below to simulate AI debugging...

Meta Senior (E5+) Software Engineer Interview Guide: Coding Speed, Product Architecture and Scope

5 min read

Prepare for Meta software engineer senior interviews with reported assessment patterns, interview questions, and preparation advice.

In this article
On this page

Last reviewed November 15, 2026.

For E5 and E6 candidates.

Built by the Codinzhub team from Meta senior interview experiences that candidates shared. Each experience is one person's interview, and Meta changes its process by year and team, so use this as a map, not a promise.

The 30-second version. A recruiter call, a phone screen with two coding problems, then an onsite of four or five rounds: two coding rounds (or one coding and one AI-enabled coding), one or two system design or product architecture rounds, and behavioral. At E5 and above, design and the scope of your work decide the level. Mixed results often lead to a follow-up interview rather than a rejection. Then the hiring committee and team matching.

Round-by-round breakdown

Stage 1: Application, where candidates applied

How it works. Most senior candidates were contacted by a recruiter, some about roles in London or Bangalore. Others had a referral from a former colleague. One candidate asked for E6 and agreed with the recruiter it sat closer to E5; another was moved up to E6 after a very strong screen.

Stage 2: Shortlisting, how candidates moved forward

How it works. A recruiter call on background, level and team preference. Candidates were given months if needed: one prepared for six weeks, another for three months. One recruiter waived the phone screen after an old OA.

Stage 3: Phone screen

At a glance

  • Length: 40 to 45 minutes
  • Questions per round: 2 coding problems, sometimes after behavioral questions
  • What was asked: intervals, trees, strings, number parsing
  • Most common: Meta-tagged mediums, sometimes a hard

How it works. Two timed coding-problem problems, slight variants of the originals. One senior candidate got one hard and one medium; another got two hards. Embedded roles asked embedded C questions such as bit manipulation.

Questions candidates reported:

Question (our summary)Follow-up reported
Valid NumberNone
A BST range questionThe tree is huge and the range changes
An interval variant and a tree or graph problemClear reasoning and edge cases
Bit manipulation and page-aligned flash writes (embedded)C or C++ only

More questions: Browse Meta questions.

Stage 4: The onsite

How it works. Four or five rounds, often split over two or three days. Coding and design rounds have no introduction. Several candidates scheduled coding first and design a week later.

Coding rounds

At a glance

  • Length: 45 minutes
  • Questions per round: 2 problems, sometimes a hard follow-up
  • What was asked: heaps, trees, intervals, calculators, production-style caches and graphs
  • Most common: Kth largest; Basic Calculator; interval variants

Questions candidates reported:

Question (our summary)Follow-up reported
Kth largest element; Unique Paths II; Best Time to Buy and Sell StockNone
Basic Calculator IIBasic Calculator III
Group Shifted StringsRange Sum of BST and a Merge Intervals twist in the follow-up interview
A cache or rate-limit problem from productionMore data, more machines, failures
A dependency graph problemScale and concurrent execution

More questions: Browse Meta questions.

AI-enabled coding round

At a glance

  • Length: about an hour
  • Questions per round: 1 multi-part problem
  • What was asked: debugging, then building on an existing codebase
  • Most common: the maze with keys and doors; the card deck; word containment

How it works. Use the AI tools, but prove you understand the code. One candidate passed after the first two of four test suites, which counted as a pass for that problem.

System design and product architecture

At a glance

  • Length: 45 minutes; one or two rounds
  • Questions per round: 1 design
  • What was asked: messaging, news feed, notifications, search, queues, auctions
  • Most common: a chat app or Messenger; News Feed

Questions candidates reported:

Question (our summary)What the interviewer focused on
Facebook News Feed frontend and APIs from a mock-upCursor pagination, response shape, UX edge cases
Messenger or a chat appPlain web APIs over WebSockets in one case
Notification systemStorage, fan-out, reliability, long-term maintenance
Ads impression aggregator, updated within 30 secondsHigh write throughput
Online auction; location search within a radiusPub/sub, server-sent events, top K
Catalog system; online chessRequirements first, then real-time moves

More questions: Browse Meta questions.

Behavioral round

At a glance

  • Length: 45 to 60 minutes
  • Questions per round: 4 to 8 questions
  • What was asked: scope, conflict with a manager, vague requirements, mentoring, moving fast
  • Most common: a disagreement with a manager

Questions candidates reported: balancing competing priorities; a disagreement with your manager where you were wrong; a project with very vague requirements; mentoring someone and giving feedback; your favourite project's scope; volunteering for an important project; your experience using AI.

More questions: Browse Meta questions.

Stage 5: Hiring committee, team match and offer

How it works. Mixed signals led to follow-up rounds: one candidate redid coding, another redid behavioral to show E5 scope. One candidate was down-levelled from L5 to L4 after a weak design round; one E6 candidate passed every round and was cut at the hiring committee. Team matching took five weeks for one candidate. Equity was the main thing candidates could negotiate.

Topics to prioritise

Across these experiences, the most common topics are system design and product architecture, heaps, trees, intervals, strings and parsing, and behavioral scope. At E5, design weighs more than coding.

The Codinzhub Next-Round Playbook

What senior candidates who moved on did. Put together by the Codinzhub team from the senior experiences in this guide.

To get past the screen

  • Practise Meta-tagged mediums and hards in order of frequency.
  • Confirm inputs, give brute force and optimised approaches, agree, then code and dry-run with an edge case.

To get past the onsite

  • For every design you prepare, be able to go deep in at least three areas.
  • Rebuild designs from memory: entities, APIs, databases, then deep dives.
  • Spread the rounds over two days so you can recover.
  • If one round goes badly, reset before the next. Candidates still passed.

To get the level

  • Tell stories about what you owned, why, and the impact, not what you took part in.
  • Use paid or peer mock interviews for design and behavioral.

About this guide

This guide is researched and written by the Codinzhub team. We read every Meta senior interview experience we could find, kept only what candidates actually described, and rewrote it in our own words. Questions are our own short summaries; the practice links point to similar problems, not the exact interview questions. Found something out of date? Share your own experience on Codinzhub and we will update the guide.

Ready for the next topic?

Keep track of what you’ve learned.