Correctness, auditability and latency - plus a coding bar that rewards precision over cleverness.
Goldman Sachs technology loops are precision loops. The coding rounds favour correctness, edge-case handling and clear reasoning over clever one-liners, and interviewers will probe what happens with an empty input, an overflow, or a concurrent modification. Sloppy but working code scores considerably worse here than at consumer product companies.
Design questions are shaped by finance constraints rather than consumer scale: auditability and immutable records, correctness under reconciliation, low-latency paths for trading-adjacent systems, and strict access control. Expect at least one round to be a domain and fundamentals conversation covering data structures, concurrency and sometimes language internals.
60-90 min
Timed automated assessment early in the process.
45-60 min
Two to three rounds on data structures, concurrency and language depth.
60 min
Auditability, correctness, latency and access control as first-class constraints.
Half day
Several back-to-back interviews mixing technical and behavioral.
A half-day block of back-to-back interviews mixing technical rounds with behavioral and team-fit conversations. Stamina and consistency across rounds matter - a strong first interview does not carry a weak fourth.
Less exotic, more exacting. Problems are often more approachable, but edge cases, overflow behaviour, thread safety and precision are probed harder, and an answer that works on the happy path only will not clear it.
Not for most engineering roles. Understanding why auditability, immutability and correctness dominate the design conversation is enough - you are not expected to price derivatives.
Practise the rounds Goldman Sachs actually runs, and get scored on where you stand.