Goldman Sachs's system-design rounds are finance-native and correctness-obsessed.
In 2026 expect prompts on real-time position and risk aggregation across trading desks, an order-management system that routes trades and handles partial fills and cancellations, and tick-level market-data storage optimised for backtesting reads. Interviewers probe consistency of aggregated state under high message rates, event ordering, and time-series read optimisation. Generic web-scale answers miss the mark; the bar is precise reasoning about correctness, latency, and the write-versus-read trade-off in a trading context. Grounding your design in real financial workflows is what separates strong candidates.
About Goldman Sachs
Top-tier global investment bank; large engineering org; Bengaluru is one of the largest engineering centers globally.
Online coding assessment (HackerRank)
Technical coding round on DSA
System-design round on a trading or risk service
Hiring-manager and Superday rounds, then offer
Round 1 (60-90 min)
online coding assessment.
Round 2 (45-60 min)
coding round on data structures and algorithms.
Round 3 (45-60 min)
system-design round on trading, risk, or market data.
Round 4 (45 min)
behavioral and hiring-manager round.
Sourced from 2+ candidate post-mortems. Hit Practice to answer any one with AI voice feedback.
2 more questions. Sign up to unlock all
Sign up free: unlock all questionsThe typical Goldman Sachs recruitment process has 4 stages: Online coding assessment (HackerRank) → Technical coding round on DSA → System-design round on a trading or risk service → Hiring-manager and Superday rounds, then offer.
Goldman Sachs typically conducts 4 interview rounds: Round 1 (60-90 min): online coding assessment.; Round 2 (45-60 min): coding round on data structures and algorithms.; Round 3 (45-60 min): system-design round on trading, risk, or market data.; Round 4 (45 min): behavioral and hiring-manager round..
HireStepX recommends the Consistent-and-Ordered framework for this type of interview: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path
To answer this question well, HireStepX recommends the Consistent-and-Ordered approach: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Consistent-and-Ordered approach: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Consistent-and-Ordered approach: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Consistent-and-Ordered approach: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path Ground your answer in a specific real example from your own experience.
To answer this question well, HireStepX recommends the Consistent-and-Ordered approach: Design for correctness first: consistent aggregated state, strict event ordering, and read-optimised time-series storage, with clear latency budgets for the trading path Ground your answer in a specific real example from your own experience.