Goldman Sachs Asset & Wealth Management logo
Goldman Sachs Asset & Wealth ManagementSoftware Engineer
Updated Jul 7, 2026

Goldman Sachs Asset & Wealth Management Software Engineer Interview Experiences 2026

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

Get your personalized Goldman Sachs Asset & Wealth Management 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
3 months ago
Difficult Neutral Warsaw, Masovia

A recruiter reached out to me, and the process moved quickly from there. After an initial technical screening, I ended up in a super day loop that felt noticeably harder than the first screen. The bulk of the day was made up of LeetCode-style problems across medium and hard levels, and the interviewers kept pushing for solid reasoning rather than just a working answer.

What stood out most was the way the final parts of the super day blended evaluation styles. My last interview shifted into a background check and a deeper dive into a couple of projects I’d described, and then it turned more theoretical—talking through applied solutions, what trade-offs they come with, and how optimization decisions change depending on the constraints. Overall, I left feeling like the questions were fair but demanding, and I didn’t end up getting an offer.
4 months ago
Average Positive United States

I applied online and, about a week later, I got an email confirming they wanted to schedule. The early stages were fairly organized: first a 30-minute phone screening with a team lead, and then I was set up for a CoderPad round shortly after, running within the next several days. The overall feel at this point was straightforward and professional.

The CoderPad portion was where the pace picked up. It was timed and focused on problem solving rather than open-ended discussion, and I remember feeling like I had to stay precise while explaining what I was doing. I moved from there into interviews that mixed technical and non-technical elements—my hiring manager session included both, and then I had a follow-up that was specifically DSA pair programming. The day-to-day vibe through the recruiter and interviewer was supportive, and I got the sense they wanted clarity and steady communication more than frantic speed, but I still didn’t receive an offer.

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

Recruiter Interaction

The initial recruiter contact is generally positive and professional, setting a supportive tone for the process, although some candidates experienced abrupt cancellations or disorganization later on.

RecruiterCommunicationProfessionalism

Technical Screening

Candidates typically undergo a CoderPad technical screen focused on problem-solving, with a mix of easy to medium LeetCode-style questions, often under time constraints that emphasize precision and reasoning.

CoderPadLeetCodeTime Constraints

Super Day Structure

The super day consists of multiple rounds that blend technical and behavioral assessments, with a strong emphasis on data structures, algorithms, and system design, often testing candidates' ability to articulate their thought processes.

Super DayTechnical AssessmentBehavioral

Technical Difficulty

Candidates report a consistently high level of difficulty across technical rounds, with expectations for depth in both coding and design discussions, requiring candidates to maintain clarity under pressure.

DifficultyCodingDesign

Behavioral Evaluation

Behavioral interviews are integrated into the process, focusing on cultural fit and communication skills, with candidates reflecting that these aspects may weigh heavily in the final decision-making.

BehavioralCultural FitCommunication

Outcome Reflections

Many candidates noted that the final evaluation often hinged on subtle details, such as the depth of technical understanding and the ability to handle pressure, leading to unexpected outcomes despite strong performances in earlier rounds.

OutcomeReflectionEvaluation Criteria