Goldman Sachs Bank logo
Goldman Sachs BankSoftware Engineer
Updated May 19, 2026

Goldman Sachs Bank Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Goldman Sachs Bank, newest first and distilled into what to expect across the loop.

Get your personalized Goldman Sachs Bank 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.
Build my free plan
Hot & recentNewest first
5 months ago
Difficult Neutral Bengaluru

After applying, I ended up doing an OA-style coding assessment first, and once I cleared that stage, the next step immediately felt much more intense. In my case, I got hit with a very hard LeetCode-style question right away—something like trapping rain water—and I just couldn’t finish it in the time. Even though the interviewer was kind, the gap between the question difficulty and what I could produce under pressure was obvious, and I didn’t move forward.

For another attempt in the same overall flow, I started with a coding round where the core LeetCode problem was simply beyond me at first. I couldn’t solve it, even though the interviewer was from outside Japan and the process still stayed fairly human. I also remember an OA that felt comparatively easier, and then the real test came right after, with the live coding/platform portion escalating fast.
5 months ago
Average Neutral London, England

My process looked like a classic two-part path: a first round with standard LeetCode questions, then a Superday packed into one day with multiple conversations focused on different SWE topics. After the initial technical screen, I showed up to a full-day format where the interviews covered a mix of system thinking and hands-on problem solving—roughly spanning system architecture/design, data structures, and LeetCode-style questions—plus a general fit discussion to close things out.

In the Superday-style round, the interviews felt structured and fairly tight on time. One technical session was presented as a short interview, but I still worked through it faster than the allocated window, starting from my previous work and projects. I got asked a set of cultural questions alongside a set of coding questions, and I also had time to ask about the role. The overall tone was not unfriendly; it just felt like they were scanning for both technical clarity and how I framed my thinking.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your 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 an online assessment (OA) focused on LeetCode-style coding problems, which serves as a preliminary filter before moving to live interviews. The difficulty can vary, but many report that the initial assessment is crucial for progressing in the interview process.

Online AssessmentLeetCodeCoding Problems

Technical Interview Rounds

The technical interviews often consist of multiple rounds, including coding challenges, system design discussions, and data structures and algorithms (DSA) questions. Candidates should expect a mix of hands-on problem-solving and theoretical discussions, with a strong emphasis on efficiency and clarity of thought.

Technical InterviewsSystem DesignDSA

Behavioral and Cultural Fit

Behavioral interviews are a significant part of the process, focusing on cultural fit and how candidates handle challenges and communicate their thought processes. Candidates should prepare to discuss their past experiences and how they align with the company's values.

BehavioralCultural FitExperience Discussion

Superday Format

Many candidates experience a Superday format, which includes multiple back-to-back interviews in a single day. This typically combines technical and behavioral assessments, requiring candidates to maintain focus and performance across different interviewers and topics.

SuperdayMultiple InterviewsBack-to-Back

Communication and Collaboration

Interviewers often assess not just technical skills but also how well candidates communicate their thought processes and collaborate during problem-solving. Candidates should be prepared to explain their reasoning and engage in discussions about their approaches.

CommunicationCollaborationProblem-Solving

Process Length and Feedback

Candidates report varying lengths of the interview process, with some experiencing delays and a lack of feedback after interviews. It's important to manage expectations regarding timelines and to follow up if communication stalls.

Process LengthFeedbackCommunication