Facebook E5 Interview Experience: Referral to Offer
Updated July 17, 2026
A candidate entered Facebook's interview process for an E5 engineering role after being referred by a friend who already worked at the company. The loop moved through a recruiter phone screen, a single technical phone screen, and a four-part virtual onsite covering coding, system design, and behavioral topics.
The coding questions spanned trees, arrays, graphs, and string parsing rather than concentrating on one topic, and the system design round asked the candidate to design a search feature and sketch the architecture live. The process ended with an accepted offer at total compensation above what had been discussed before interviews began.
How the process went
Referral
The candidate was referred by a friend already working at Facebook, which led to the initial recruiter outreach.
Recruiter phone screen
A call covering the candidate's current role, motivation for leaving, status of other interview processes, general logistics such as visa status, and which level the candidate would interview at.
Technical phone screen
A single 45-minute session with two coding questions and only brief introductions before moving into the problems.
Virtual onsite
Four back-to-back 45-minute rounds: two coding rounds, one system design round, and one behavioral round that also included a coding question.
Offer
The candidate accepted an E5 offer with total compensation above the figure discussed before the interviews started.
Recruiter Phone Screen
Background, motivation, and interview logistics
- Details about the candidate's current job
- Why they were considering leaving their current company
- Status of other interview processes and any existing offers
- General logistics questions such as visa status
- Discussion of what level the candidate would be interviewed at
Scheduled after a referral from a friend at Facebook.
Technical Phone Screen
Two coding problems with no separate behavioral portion · 45 minutes
- Lowest Common Ancestor of a Binary Tree III
- Integer to English Words
The candidate spent roughly 15 minutes on the first problem and about 25 minutes on the second.
Virtual Onsite – Coding Round 1
Array and graph problems · 45 minutes
- Product of Array Except Self
- Clone Graph
Virtual Onsite – Coding Round 2
Subarray/prefix-sum and string-parsing problems · 45 minutes
- Subarray Sum Equals K
- Minimum Remove to Make Valid Parentheses
Virtual Onsite – System Design
Designing a search-oriented feature · 45 minutes
- Design Facebook Status Search
The candidate used an iPad to sketch and explain the architecture diagram during this round.
Virtual Onsite – Behavioral Round
Behavioral questions plus one coding question · 45 minutes
- Recent projects at the candidate's current company
- Why they were leaving their current company
- A conflict resolution example
- How they handled working with a difficult colleague
- One coding question similar to First Bad Version
Key takeaways
- A referral can help get a recruiter call scheduled quickly, but the technical bar in the rounds that followed was unchanged.
- The coding questions across the phone screen and onsite covered a wide span of classic patterns — trees, arrays/prefix sums, graphs, and string parsing — so breadth of practice mattered more than depth on any single topic.
- For the system design round, being ready to sketch and narrate an architecture diagram (the candidate used an iPad) helped communicate the design clearly.
- The behavioral round wasn't purely conversational; it also included a live coding question, so it helps to stay warmed up on coding even in that slot.
- Total compensation was finalized after the offer stage and ended up higher than the figure discussed earlier, so it's worth treating a pre-interview compensation number as a starting point rather than the final one.
Practice a Facebook interview
Rehearse out loud against the kinds of questions in this story — with an AI interviewer that asks follow-ups.
Practice this interviewSource
The questions and process facts come from the candidate's public write-up, linked below. The retelling above is our own summary.
Candidate's public write-up on LeetCode Discuss