hey everyone. i've been tracking Meta interview loop data to build a clearer picture of what the process actually looks like right now, specifically for 2025-2026 loops.
there are already a couple threads on the coding rounds and comp but i want this one focused on the FULL loop structure: how many rounds, which rounds happened, what order, how long you waited between stages, and the outcome if you're comfortable sharing. any role, any level.
i'll start with what i've seen aggregated from other threads and DMs:
common loop structure (SWE E4-E5 as of early 2026): recruiter screen: 30 min, mostly behavioral + process overview technical phone screen: 45-60 min, 1-2 LC-style coding problems onsite / virtual onsite: typically 4-5 rounds on the same day or spread across 2 days 2 coding rounds (medium-hard, sometimes one tree/graph, one DP or array) 1 system design (E5 and above especially) 1 behavioral (Jedi round): leadership principles, cross-functional situations 1 architecture or domain round depending on role
timelines people have reported: recruiter screen to phone screen: 1-3 weeks phone screen to onsite: 2-4 weeks onsite to decision: 1-2 weeks, sometimes up to 3
but these vary a lot. i've heard of people getting next-day offers and others waiting 5 weeks post-onsite.
what i'm specifically trying to collect: your role and target level which rounds you had and in what order how long the whole process took anything that felt different from what you expected going in
drop what you remember below. no pressure to share outcome if you don't want to.
5 replies
frontend_fran
went through this in February 2026 for E4 SWE, web/frontend track. loop was: recruiter call 30 min technical screen: 45 min, 1 medium string problem (went fine) onsite 5 rounds on one day: 2 coding (one array, one graph BFS), 1 system design (design a news feed), 1 behavioral jedi, 1 culture fit (this was lighter, almost a 'get to know you' round)
total process: about 6 weeks start to finish. got the offer 10 days after onsite. the system design was the part that felt highest stakes at E4 honestly.
jp_newgrad
did they ask about specific frameworks in the system design or was it more general distributed systems stuff? asking because i'm E3 targeting and wondering how deep they go at that level.
mobile_mara
ios engineer loop, March 2026. E4 target: recruiter screen phone screen: objC/Swift question, nothing too crazy, asked about memory management onsite 4 rounds: 1 mobile-specific (architecture of an iOS app, offline sync design), 1 general coding (LC medium, graphs), 1 system design lite, 1 behavioral
took 7 weeks total, which felt long. the wait after onsite was 14 days and i was losing my mind. got an offer but had to push for timeline clarification twice.
infra_ines
infra/platform loop E5, January 2026: recruiter 30 min no separate phone screen (they skipped it and went straight to onsite, recruiter said this happens sometimes for experienced hires) onsite: 2 coding (one was actually a bash/linux scripting adjacent problem which surprised me), 1 distributed systems design, 1 infra-specific round on observability and incident response, 1 jedi offer 8 days post-onsite
the infra-specific round felt more like a senior eng conversation than an interview. they wanted to know how i think about failure modes. less leetcode, more 'how would you design on-call rotation for a team that's paged 30 times a month'.
brand_ben
not an eng loop but posting for the designers: went through a product design onsite for a mid-level IC role in April 2026. portfolio review, two design exercises (one critique, one from-scratch prompt), and a cross-functional round with a PM. no coding. total loop about 5 weeks. decision took 12 days. the critique round was the hardest because they pushed hard on tradeoffs, not just what you'd change.