Goldman Sachs Software Engineer interview experience

RemoteCandidate report, summarized by Dataford

Right after I cleared the first video coding screen, the hiring side told me the next stage would be more conceptual rather than another pure coding round.

That stuck with me because I realized I couldn’t just rely on writing code quickly—I’d need to be ready to explain thinking, tradeoffs, and how I approach problems beyond syntax.

In the coderpad portion that I did before hearing about the conceptual shift, the interviewer kept drilling into follow-ups around optimization and edge cases. They also mentioned up front that there would be several rounds total, roughly in the 4–5 range, so it didn’t feel like a single one-off conversation.

Once I got to the point where the process was describing what came next, the preparation pressure changed:

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Goldman Sachs Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Goldman Sachs interview guidesEvery role we cover at this company