Real, anonymous reports from people who interviewed for Software Engineer at Goldman Sachs, newest first and distilled into what to expect across the loop.
Get your personalized Goldman Sachs Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I went into a CoderPad session where the problems were surprisingly straightforward and focused on basic DSA patterns. I had two questions: one was about finding the first non-repeating character, and the other was essentially an optimal path problem described as “rock collection.” The round itself felt light compared to what I expected—more like testing clean thinking than pushing me into an extreme difficulty.
After that, the scheduling moved into a superday track. I got a call asking me to move forward for a superday interview, although the timeline details didn’t line up perfectly with the dates I had been given for the earlier stage, which added a little confusion.
4 months ago
I got pulled into a Goldman Sachs process through a coding-focused assessment on CoderPad. After the initial step, I had a problem-solving round that was basically two coding questions back to back. Both were framed in a very LeetCode way and, for the first prompt, it used the “High five” problem. The expectation felt strict: my solution had to run cleanly, and it wasn’t enough to just pass the sample—I needed additional test cases to work too. The second prompt was “High five” as well, so it felt like they really wanted correctness and robustness rather than creative interpretation.
The interview itself felt methodical. I worked through the logic, verified assumptions as I went, and kept checking edge cases because the setup made it clear they cared about whether the code actually held up under extra tests. Once I wrapped up, the process moved forward in the usual interview pipeline, but I didn’t end up getting an offer. What stayed with me most was how strongly the platform’s requirements were emphasized—getting the algorithm right wasn’t the only bar; the implementation had to be solid.
5 months ago
Difficult Neutral Bengaluru
My process started with an assessment that felt positioned as a tough gate. I first took a HackerRank screen with two coding questions. After clearing…
5 months ago
Average Neutral London, England
I went through Goldman Sachs in a way that felt like a compact but multi-part screen. One stage was described as a 1:15-minute interview, and I actual…
5 months ago
For a VP Software Engineer interview, I was hit with algorithmic questions that felt more like brain teasers than typical coding drills. The screening…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Coding Assessment
Candidates typically start with a CoderPad assessment focused on basic data structures and algorithms (DSA), often with straightforward problems that require clean implementation and edge case handling. Expect questions that test both correctness and robustness, with a strong emphasis on writing test cases.
CoderPadDSATest cases
Superday Structure
The interview process often culminates in a superday consisting of multiple back-to-back interviews that cover a range of topics including coding, system design, and behavioral fit. Candidates should prepare for a mix of technical discussions and cultural fit assessments, with a focus on clear communication throughout.
SuperdaySystem DesignBehavioral
Technical Depth and Pressure
Candidates report a significant increase in difficulty from initial assessments to later rounds, particularly in coding challenges that may include complex LeetCode-style problems. The pressure to perform under time constraints can be intense, and candidates should be ready to explain their thought processes and reasoning in detail.
LeetCodeTime PressureProblem Solving
Behavioral and Cultural Fit
Behavioral interviews are a key component of the process, often focusing on collaboration, problem-solving mindset, and communication skills. Candidates should prepare to discuss their experiences in depth, as these rounds are designed to assess alignment with the company's values and culture.
BehavioralCultural FitCommunication
Communication and Feedback
Candidates have noted varying experiences with communication throughout the process, including delays in feedback and a lack of clarity regarding next steps. It’s important for candidates to seek clarity and follow up if they feel uncertain about their status after interviews.
CommunicationFeedbackFollow-up
Overall Experience and Outcomes
The overall experience can vary widely, with some candidates feeling well-prepared and others facing unexpected challenges or a lack of closure post-interview. Reflecting on the process and identifying areas for improvement can be beneficial for future applications.