Skip to main content
HireStepX is now in Beta! Be among the first to practise smarter and get hired on proof.
System Design · Goldman Sachs

Goldman Sachs System Design Interview Questions 2026

Goldman Sachs's system-design rounds are finance-native and correctness-obsessed.

By the HireStepX editorial team · How we source and label this

Questions12
Rounds4
Intense9 of 12
FrameworkConsistent and ordered
Try it · Goldman Sachs question 1 of 10
Intense

Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

Think of your answer first, then reveal how to structure it.
Practise this out loud

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.

Practice questions

  1. 01

    Design a system to predict same-day delivery feasibility for a new pincode in tier-3 India.

    IntenseFlipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.
    Practise
  2. 02

    We're seeing UPI failure rates spike at 9pm on weekends. How would you debug, and what's your hypothesis?

    IntenseRazorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.
    Practise
  3. 03

    Walk me through how you'd build idempotency into a payment retry system. What happens if the network drops mid-callback?

    Intense
    Practise
  4. 04

    Design Swiggy Genie's matching algorithm. How does it differ from food-order matching?

    Intense
    Practise
  5. 05

    Walk me through how you'd architect transaction-level fraud detection for 100M daily UPI transactions.

    IntensePhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.
    Practise
  6. 06

    How would you build a recommendation engine that suggests bills the user is about to forget?

    Standard
    Practise
  7. 07

    Design a cashback-allocation system that prevents abuse without alienating genuine users.

    Standard
    Practise
  8. 08

    Design a system to detect duplicate documents at web scale. What's your approximation strategy?

    IntenseGoogle SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.
    Practise
  9. 09

    Design Amazon Prime's recommendation engine. How would you handle the cold-start for a new Prime member?

    Intense
    Practise
  10. 10

    Design a URL shortener like bit.ly. Walk me through database choice and scaling.

    Standard
    Practise
2 more questionsCreate a free account to see the full set and practise any of them with scoring.Unlock all questions
Prep notes

How to walk in ready.

The 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.

Flipkart engineering loves India-specific constraints: pincode coverage, monsoon patterns, kirana partnerships.

Razorpay loves real production scenarios: payments failures, NPCI rate limits, settlement reconciliation. Be specific.

PhonePe engineering rounds are scale-obsessed: every answer should explicitly address throughput, latency, and cost at India scale.

Google SWE rounds prize first-principles thinking and explicit trade-off articulation. Always discuss what you're approximating.

Real-time position and risk aggregation, an order-management system handling partial fills and cancellations, and tick-level market-data storage optimised for time-range reads.

More to read

Practice

Rehearse the room before you enter it.

Run a mock Goldman Sachs interview and get scored feedback on every answer.