did the Goldman Sachs senior engineering system design interview last month for a platform role. here's what I actually encountered vs what I expected.
expected: generic distributed systems question like design Twitter or design a URL shortener.
got: design a real-time trade confirmation notification system. needs to support millions of trades per day, sub-second delivery to client-facing apps, auditability for compliance, and graceful degradation if the downstream notification service is unavailable.
the finance context is real. they care that you understand concepts like at-least-once vs exactly-once delivery in a high-stakes financial context. idempotency keys matter here in a way they don't when you're designing a social feed.
what they evaluated: I could tell they were watching for: how you define SLOs before jumping into architecture whether you bring up failure modes proactively how you handle data consistency vs availability tradeoffs (and whether you even recognize there's a tradeoff) can you reason about operational concerns: monitoring, alerting, runbooks
i'd say 60% of the signal came from how I framed requirements and asked clarifying questions. the actual component choices mattered less.
level expectations for senior/vice president track: they want to see you lead the conversation. the interviewer went quieter once I established a solid direction, which I think was intentional. if you're waiting to be guided you're probably not performing at level.
duration was 45 minutes. I spent the first 8-10 minutes on requirements/scope, which felt like a lot but the interviewer seemed fine with it.
one heads-up: Goldman interviewers will often ask you about operational tradeoffs at a depth that startup interviewers don't. "how would you handle a kafka partition lag spike at market open" is a real thing someone might ask. worth having an answer.