Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Goldman Sachs Engineering interview research

Candidate accounts · 1 scoped account · 5 reported questions/topics

Snapshot: 1 October 2026 · Software/backend focus · No live fetching

Self-reported accounts, not employer-confirmed. Preserve the stated role, team and location; this sample does not establish company-wide patterns or question frequency.

Questions people reported

Named problems, reported variants and broad topics are different kinds of evidence. Related practice links are not proof that the exact problem was asked. Some prompts were withheld; we do not invent their details.

Topics in these accounts: Coding · System design · Backend

SWE; Core Engineering; level/location not established

Interview date unknown; indexed publication date not confirmed

Read the original candidate account

Scope and source limitations

Search-indexed report date: September 11, 2026. New York was asked about, not confirmed. Another commenter's Dallas/messaging account is separate and is not merged.

  • Remove a minimum number of parentheses to balance input

    Coding · Reported topic

  • Minimum denomination count to reach a target

    Coding · Reported topic

  • Multi-garage parking allocation with concurrency

    System design · Reported topic

  • Global music streaming with CDN failover

    System design · Reported topic

  • Retry safety and transactional outbox in project discussion

    Backend · Reported topic

Additional independent, matching role/level/region reports are needed before claiming recurring patterns.

A suggested 14-day preparation plan

Authored practice, not the company’s syllabus. This general track is an editorial starting point, not a pattern inferred from all these reports. Confirm the format with your recruiter and adapt it to your actual level.

Backend correctness and Java/SQL depth

Balance DSA with transactions, indexes, API contracts, Java fundamentals, concurrency and failure recovery.

  • Days 1–2: hashing, prefix sums and interval/window exercises.
  • Days 3–4: Java collections, object contracts and concurrency tests.
  • Days 5–6: SQL joins/indexes; transaction isolation and locking examples.
  • Days 7–8: implement a reservation, ledger or workflow service.
  • Days 9–10: design retries, idempotency and asynchronous failure recovery.
  • Days 11–14: design mock, project debugging story and mixed final mock.
Practise an original design exercise

Design a trade-event audit service with replay.

This exercise is written for practice, not reported by a candidate. Define requirements, implement the smallest useful version, then test concurrency, retries and failure recovery where relevant.

Customize a timed role/level prep brief

The timed brief uses a narrower, date/level-filtered dataset. Broader accounts on this page are deliberately not substituted into those filters.

How this research was collected

Public candidate accounts, official guides and original editorial practice are kept separate. We did not copy paid question banks or scrape all of the internet. Cross-posts are not independent evidence; one source can describe more than one company. Unknown or index-only dates are not used to claim recency. Future expansion needs permitted fetching, deduplication and metadata review; this version remains a static snapshot.