I went through an interview flow that had both data structures/technical assessments and longer time blocks. The coding assessments were two separate segments tied to data structures and a technical track, and each one ran about 90 minutes.
The recruiter was alongside during the process to help manage things and also to ask about implementation. Because the time was so long and focused on coding and execution, it didn’t feel like the kind of interview where you can coast.
8 months ago
Difficult Neutral United States
My Meta interview experience felt pretty standard compared to other tech companies. It totaled about five interviews end to end: a screening, one coding assessment, and then three separate one-hour interviews all packed into the same day. The schedule itself was straightforward, and the time commitment felt intense because everything technical ran close together.
I walked into the interviews expecting the usual mix—coding plus deeper follow-ups—and that’s pretty much what happened. While it was rigorous, it didn’t feel random or poorly organized, just concentrated. When it was over, I didn’t move forward, but I had the sense that the structure was consistent and the interviews were designed to evaluate the core skills the role needed.
11 months ago
Average Positive Henrico, VA
My process felt unusually smooth. The recruiters were helpful throughout, and there was a clear structure: I started with a technical round, and then …
12 months ago
Difficult Positive Menlo Park, CA
My interview path leaned heavily technical and a bit unusual compared to a pure coding-only loop. I went through multiple rounds where the first porti…
Unlock every Network Engineer interview experience
