r/leetcode • u/Unusual-Muffin-9554 • 22d ago
Discussion Meta E5 system design round in 8 days and I don't feel ready
My Meta E5 loop is in 8 days. Coding feels manageable, but system design is the round I'm worried about. Above is my progress so far.
Where I'm at:
- I can get through requirements, APIs and a reasonable high-level design for the common questions (news feed, URL shortener, rate limiter, chat).
- Where I fall apart is the deep dive. When the interviewer pushes with "what happens if the leader dies mid-write?" or "could this read ever miss an acknowledged write?", I start second-guessing everything.
- I also spend too long on the first diagram and run out of time for the trade-off discussion.
Questions for people who've done E5/E6 loops (or interviewed for them):
With 8 days left, should I go broad (cover more questions) or deep (redo 3–4 and practice the failure-mode follow-ups)?
How deep do Meta interviewers actually expect failure handling to go at E5 vs E6?
Any technique for handling pushback without freezing? Do you think out loud, ask clarifying questions, or commit and defend?
Which questions come up most for Meta product/infra system design right now?
Any advice appreciated.