Updated by Meta candidates
Software Engineer Interview Experience
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 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.
Questions asked
Specific questions asked
Given nums + window size k, return the max for each sliding window. Need O(n), so deque
I initially thought heap, then switched to monotonic deque. Edge cases were duplicate values + window expiry.
implement serialize(root) + deserialize(data) so the same tree comes back
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 + scale
regular behavioral questions
Get full access with a membership, or share your experience to try it free.
