Interview process
The process was pretty rigorous, mainly because the bar at E6 felt more about scope and judgement than just solving the questions. Recruiter was clear and helpful. The coding rounds went ok, but I spent too long explaining some edge cases. Design was probably the strongest part, good back-and-forth and tradeoffs. Behavioral was fine, though I could’ve been more specific with impact numbers. Overall, a solid process but definitely tiring.
- Technical interview
Interview rounds
4 questions across 1 roundTechnical interview
4 questionsOverview
Besides the technical questions listed below, I was asked some regular behavioral questions too.
Specific questions asked
I initially thought heap, then switched to monotonic deque. Edge cases were duplicate values + window expiry.
Talk through fanout, ranking, caching, pagination, celebrity users, consistency + failures
Users can play chess in real time, reconnect if needed, and see a ranked leaderboard. Cover matchmaking, game state, WebSockets, persistence, cheating, and scale
Interview tips
I'd revise the common Meta-tagged LC problems, but don’t just memorise solutions. Practice explaining your thinking while coding. For E6, spend proper time on system design- requirements, scale, failure cases, tradeoffs, and how you’d get other teams aligned. Also prep 5–6 real leadership stories. The interviews move quickly, so keep answers fairly structured
Company culture
The interviewers seemed direct but fair, and mostly interested in how I think rather than looking for one “correct” answer. There was a lot of focus on ownership, moving fast, and influencing outside your immediate team. The vibe felt pretty pragmatic. I didn’t see any obvious red flags, although the pace and scope expectations seem high.
Get full access with a membership, or share your experience to try it free.
More Meta interview experiences

“There’s a new AI coding section I haven’t seen before. They still want to test my coding skill, so I first implement by myself, then use AI as a code reviewer for readability and missing test cases.”

“In the age of AI, I could feel the interviewer adding little follow-up questions just to make sure I actually understood the problem, because if you were using AI tools, there’d be a lag. Even clearing the onsite doesn’t mean you’ll find a team quickly.”