E5 Software Engineer Interview Prep
Curated practice for Meta's E5 loop - heavy on system design and senior-level behavioral signal.
About this loop
Meta's E5 loop is one of the more demanding in the industry. Two coding rounds at Hard difficulty (or Medium with deep follow-ups), two system design rounds (one product-flavored, one infra-flavored), and a behavioral round with senior-level expectations. At E5, you're expected to drive system design conversations, not just respond. The behavioral round screens for impact, strategic thinking, mentoring, and conflict navigation - 'I shipped a feature' is not enough; you need stories about steering teams, navigating ambiguity at scale, and recovering from failure. Meta runs a tight 2-day onsite (or virtual equivalent), so stamina and pacing matter.
The interview loop
- 1Recruiter screen30 minutes. Level calibration (E4 vs E5 vs E6), team interest, logistics.
- 2Phone screen (technical)45 minutes, two coding problems back-to-back. Pace matters - if you don't finish both, that's a signal.
- 3Onsite: Coding round 145 minutes, two algorithmic problems. Hard or Medium-with-twist. Trees, graphs, dynamic programming, intervals.
- 4Onsite: Coding round 245 minutes, two more algorithmic problems. Different topics from round 1. Heavy on follow-up questions probing depth.
- 5Onsite: Product system design45 minutes. Design a user-facing system: news feed, messaging, photo sharing, live streaming. Drive the conversation.
- 6Onsite: Infra system design45 minutes. Design backend infrastructure: rate limiter, distributed cache, log aggregation, queue. Lower-level than product design.
- 7Onsite: Behavioral45 minutes. E5-level signal: impact, ambiguity, mentoring, cross-team navigation. Bring metrics and named projects.
What Meta actually evaluates
- →Speed and code volume - you should clear two problems per coding round
- →Driving system design conversations without prompting
- →E5-level impact stories: 'shipped feature' is below bar - you need 'steered roadmap, mentored juniors, navigated cross-team conflict'
- →Identifying trade-offs explicitly and defending choices
- →Comfort going deep on follow-ups (sharding strategy, hot partitions, consistency models)
- →Honest assessment of your own work - what you'd do differently
Topics tested
System Design
Two design rounds at E5. Practice both product-flavored (news feed, messaging, photo sharing) and infra-flavored (rate limiter, distributed cache, queue). Drive the conversation - silence is a negative signal.
Algorithms
Two coding rounds, each with two problems. Pace is the real test - you should finish both problems with time for follow-ups. Hard difficulty or Medium with deep follow-ups is the norm.
Data Structures
Trees, graphs, heaps, hash maps, intervals. Meta loves graph problems and tree DP - know these cold.
Behavioral
E5-level signal. Stories about driving impact across teams, mentoring, navigating conflict, recovering from failure. 'I shipped a feature' is below the bar - stretch to stories about influence.
Databases
Comes up in system design - sharding, replication, hot partitions, consistency models. Rare as a standalone topic.
Operating Systems
Light coverage in infra system design rounds. Process vs thread, memory layout, file system basics. Useful to have but not deeply tested.
System design topics tested in this loop
Curated walkthroughs for the bounded designs that show up in Meta's system design rounds. Capacity estimation, architecture, deep-dives, and trade-offs.
News Feed
HardThe classic write-vs-read amplification trade-off. Push, pull, or hybrid fanout - and how to handle the celebrity user with 100M followers.
Chat
HardLong-lived connections, ordering guarantees, presence, and the difference between 1:1 chat and a 50K-member group.
Video Streaming
HardEncoding ladders, adaptive bitrate, CDN economics, and the difference between live and VOD. Petabyte-scale storage meets millisecond-scale playback.
Distributed Cache
HardConsistent hashing, eviction, replication, and what really happens when a single hot key takes down the cluster.
Rate Limiter
MediumFive algorithms, three sharding strategies, one fail-open vs fail-closed decision. The bounded design that surfaces in every backend interview loop.
Ride-Share Dispatch
HardGeo-indexing, real-time matching, ETA prediction, and surge. The canonical geo-spatial design problem with hard real-time constraints.
Behavioral themes tested in this loop
Sample STAR answers, common prompts, pitfalls, and follow-up strategies for the behavioral themes that decide Meta's loop.
Ownership
Amazon LPTested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?
Conflict
GeneralThe most universal behavioral question. Tested everywhere. The signal is in how you investigate the disagreement, not in how you 'won.'
Learning from Failure
MicrosoftMicrosoft's Growth Mindset core. Also tested at Google, Anthropic, and any company that screens for self-awareness. The signal is whether you actually changed.
Ambiguity
GeneralTested at Google, Anthropic, OpenAI, and any senior+ loop. Strong candidates show how they get curious; weak candidates show how they get anxious.
Compensation at Meta BETA
Total comp ranges, base, equity, and bonus across the levels tested in this loop. Aggregated from public sources.
Meta compensation by level
5 SWE levels covered. Updated 2026-05.
Curated practice questions
346 MCQs and 231 coding challenges, grouped by topic. Free preview shows question titles - premium unlocks full content.
System Design · 68 MCQs
Browse all in System Design →Algorithms · 77 MCQs
Browse all in Algorithms →Data Structures · 44 MCQs
Browse all in Data Structures →Behavioral · 63 MCQs
Browse all in Behavioral →Databases · 49 MCQs
Browse all in Databases →Operating Systems · 45 MCQs
Browse all in Operating Systems →System Design - Coding challenges · 2 challenges
Browse all coding challenges →Algorithms - Coding challenges · 149 challenges
Browse all coding challenges →Data Structures - Coding challenges · 50 challenges
Browse all coding challenges →Databases - Coding challenges · 25 challenges
Browse all coding challenges →Operating Systems - Coding challenges · 5 challenges
Browse all coding challenges →Practice in mock interview format
Behavioral and system design rounds reward practice with a live AI interviewer that probes follow-ups, not silent reading.
Start an AI mock interview →Frequently asked questions
What's the difference between E4 and E5 at Meta?
E4 is mid-level (3-5 YOE). E5 is senior (5-8 YOE) and the level at which Meta expects you to operate independently and drive technical decisions. The interview bar at E5 is significantly higher: harder coding problems, deeper system design follow-ups, and behavioral stories about influence and impact, not just execution.
How do I clear both problems in a 45-minute coding round?
Pace ruthlessly. Spend 2-3 minutes clarifying, code in 12-15 minutes, walk through with one example, move to the next problem. The interviewer will help with hints if you're stuck - take them quickly. Practice with a timer and force yourself to move on. Most candidates over-explain and run out of time.
What makes a Meta system design round different?
Meta expects you to drive. Many candidates wait to be asked questions - that's a negative signal. You should clarify scale, sketch a high-level architecture, then walk through components proactively, calling out trade-offs as you go. The interviewer is evaluating whether you would be able to lead a real design discussion at the company.
How important are metrics in behavioral stories?
Critical at E5. 'I improved performance' scores poorly. 'I reduced p99 latency from 800ms to 200ms across our 5M-user product surface, which lifted retention by 2%' scores well. Senior-level signal requires you to know your numbers and tie work to business outcomes.
What product designs come up most often at Meta?
News feed, messaging (DMs, group chats), photo/video sharing, live streaming, notification systems, and recently, ads ranking and recommendation systems. All of these have real Meta products behind them - reading public engineering blog posts about how Meta builds these gives you legitimate study material.
How long is the Meta interview loop end-to-end?
Recruiter screen to offer typically 6-10 weeks. Onsite is usually compressed to one or two days. Hiring committee review is fast (1 week). Team matching can add 2-4 weeks. Plan for 8-12 weeks total. Many candidates run multiple loops simultaneously - Meta is OK with this.