Sweaty Imposter

Meta E6 Loop

Company GuideStaffStaff Software Engineer · Last checked Nov 2026

Two design rounds drive the E6 decision, and staff candidates are generally expected to pass both. Down-leveling to E5 is common, and it usually traces to design depth or to behavioral stories without enough cross-team scope.

The Rounds

Screens

  • Recruiter CallCovers your background, the scope of your recent work, and your product or infrastructure track.Practice Recruiter Call
  • Structured ScreenUsually pairs coding problems with behavioral questions, and helps set whether the loop runs at E5 or E6.Practice Structured Screen

Onsite

  • CodingTwo medium problems with a higher bar for code quality and edge cases. · 45 minPractice Coding
  • AI-Enabled CodingUsually replaces the second coding round: work through a multi-file codebase in CoderPad with an AI assistant. · 60 minPractice AI-Enabled Coding
  • System Design or Product ArchitectureTwo rounds on your track, each a separate problem, and the rounds that weigh most on level. · 45 minPractice System Design or Product Architecture
  • BehavioralLeadership, influence across teams, conflict, and ownership, with pushback on the alternatives you weighed. · 45 minPractice Behavioral
  • Project RetrospectiveSome teams only: walk through a major project you led, sketch its architecture, and defend the decisions.Practice Project Retrospective

What the E6 Loop Weighs

  • Both design rounds at staff depth: you set scope, name the hard parts, and go deep where it matters.
  • Long-term thinking in design, including how the system and its owners change over time.
  • Behavioral stories measured by reach: how many teams the work touched and what changed because of you.
  • Coding at a higher bar for quality and edge cases, at medium difficulty.
Sources

Sources

Last checked Nov 2026. Loops vary by team and change over time, so confirm the details with your recruiter.