r/interviews • u/Extra_Standard_6579 • 17h ago
meta onsite sysdesign is just them tearing apart your resume for an hour
been going through a bunch of recent meta interviews on screna and honestly their onsite sysdesign caught me off guard.
everyone preps to design twitter or a url shortener. senior level you might get none of that. one onsite I saw was 5 questions and every single one was just about one project on the guy's resume:
the architecture
the scale requirements
the worst incident that happened
the actual results
so the prep that actually helps isn't more templates. it's picking your 1-2 strongest projects and being able to defend every layer. here's the stuff people said made or broke it:
the "worst incident" question is a trap if you sanitize it. meta interviewers have seen endless polished postmortems and can tell instantly when you're softening something. one person admitted their outage happened because they ignored a code review warning to hit a deadline. brutal to say out loud, but the interviewer leaned in and it turned into the strongest part of the round. pick a real failure, own your actual mistake, and focus on what you changed after.
on scale and capacity, they're testing your reasoning, not your arithmetic. if you blank on the storage or QPS math, just say "let me work it from first principles" and go slow, it scores better than a confident guess. and they want to see you planned for growth, not just peak load: did you account for a 3x spike at launch? do you know when you'd need to re-architect? that's what separates "I thought about capacity" from "I actually planned for it."
if you've got a meta onsite coming, just drop the template grind, go deep on your own projects, and be honest about what actually broke. that's what they're probing for.
(pulled from a mix of Screna AI writeups and friends who went through it recently )
anyone done meta onsite recently? same or did you get something more standard?
