Meta · Primly Community

Completed the Meta loop last month. Here's what actually happened.

corp_refugee · 4 replies

Just finished an E5 SWE loop at Meta. Got the offer, sharing notes while they're fresh.

The coding rounds: two of them, back to back with the same 5-minute break in between. First one was a graph traversal problem that looked easy and wasn't. The key thing nobody tells you: if you get a brute force working, they'll ask you to optimize, and they want to hear you reason about complexity before you rewrite. I made the mistake of silently rewriting. The interviewer stopped me and said "talk to me." That's a signal.

Second coding round was DP. Didn't finish perfectly clean. Still got the offer. I think they'd rather see you reason correctly under time pressure than produce flawless but silent code.

System design: was asked to design a notification system at Meta scale. I spent the first 5 minutes on requirements and capacity estimates. Interviewer visibly relaxed when I started doing the math. They pushed hard on the fan-out problem and whether I'd shard by sender or receiver. Know your trade-offs.

Jedi round: 45 minutes, 3 behavioral questions. Mine were all about navigating disagreement, influencing cross-functionally, and a time I'd shipped something that wasn't ready. Have real stories. They probe the 'what did YOU specifically do' angle relentlessly.

Total timeline: recruiter reached out, loop was 6 weeks later, offer came 10 days after that.

4 replies

newgrad_neil

the part about 'talk to me' is so useful. i always go quiet when i'm thinking. going to consciously practice narrating during mock interviews. did the Jedi round feel like a trap or was the interviewer actually warm about it?

corp_refugee

the interviewer was fine. it's more that the questions are very specific, not 'tell me about a time you collaborated' but 'tell me about a time you disagreed with your manager and what you did about it.' if you have a vague answer they'll keep probing until you give them a real one. so have a real one ready.

staff_steph

the 'sharding by sender vs receiver' question is a classic and it has no right answer. the right move is to explain the actual failure modes of each. sender sharding means hot users blow up a shard. receiver sharding means broadcast to large audiences is expensive. both are true. state them both and say which you'd pick for which access pattern. that's the answer.

ml_mike

six weeks recruiter to loop is pretty normal for Meta in my experience. though the 10 days for offer came back fast, I've seen up to 3 weeks post-loop. congrats on the offer.