Senior Software Engineer applicants have rated the interview process at Goldman Sachs with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 35% positive. To compare, the company-average is 60.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Senior Software Engineer roles take an average of 36 days to get hired, when considering 42 user submitted interviews for this role. To compare, the hiring process at Goldman Sachs overall takes an average of 33 days.
Common stages of the interview process at Goldman Sachs as a Senior Software Engineer according to 42 Glassdoor interviews include:
Phone interview: 29%
One on one interview: 22%
Skills test: 18%
Group panel interview: 10%
Background check: 6%
Presentation: 4%
Personality test: 4%
Drug test: 4%
Other: 2%
IQ intelligence test: 2%
Here are the most commonly searched roles for interview reports -
I applied through a staffing agency. I interviewed at Goldman Sachs (New York, NY) in Jun 2022
Interview
VP position for a low latency application team. Started with phone screen coderpad round. Two questions - one LC easy (find first unique char in string) and one LC medium (minimum path sum).
They reverted back pretty quickly and asked to provide availability for a 4-6 hour window possibly in a single day. I provided my availability then they came back and asked to provide availability for some 6am-8am slots as they wanted people from India and London to interview as well. I provided Friday as the day and said that I can do Monday as well if they needed. They got back to me with the schedule which mentioned interview round for Thursday 7am-8am. I decided just go with it as it was already Tuesday and didn't want any more delays.
All interviews had two people except one where the other person showed up just for a few minutes in the middle of the interview.
Everybody was nice.
Morning round - first question LC easy (intersection in LL) next question LC medium (meeting rooms II). I failed to provide the correct answer for medium question.
Next round in the afternoon - another person from London - a weighted graph question to find shortest path from source to destination. Interviewer told me straight that he didn't know the solution and that he is reading the solution right then. I gave him my approach using bfs and dfs. I started writing bfs but got confused that maybe bfs wasn't the best approach so I suggested that dfs was the best approach and will have to traverse all possible paths to get the best answer. By this time interviewer completed reading the solution which I think was dikstra's algo. I knew dikstra's algo solved such problem but didn't remember what it was and so I could not understand his clues. In the end he asked me for a run time complexity of a solution that I wasn't sure of so I failed to answer that as well.
Next round was right after this round.
one interviewer gave me an easy question related to meeting room which I was able to solve. Other interviewer asked me to design a parking garage application at a low level starting with DB schema. I think I failed to satisfy the interviewer there as well and might have replied rudely to a suggestion. I was a bit frustrated from my last round trying to figure out dikstra's algo.
They didn't ask me to write code to run against any inputs in any round. Only asked to write the code and discuss the solution.
I had one round next day. I joined the call but no one else joined so I emailed the recruiter who told me to drop off as the call has been cancelled and they will provide me an update shortly from yesterday's round. I sort of already knew I wasn't going to get it but didn't think they will cancel the call without letting me know.
Interview questions [1]
Question 1
Morning round - first question LC easy (intersection in LL) next question LC medium (meeting rooms II). I failed to provide the correct answer for medium question.
Next round in the afternoon - another person from London - a weighted graph question to find shortest path from source to destination. Interviewer told me straight that he didn't know the solution and that he is reading the solution right then. I gave him my approach using bfs and dfs. I started writing bfs but got confused that maybe bfs wasn't the best approach so I suggested that dfs was the best approach and will have to traverse all possible paths to get the best answer. By this time interviewer completed reading the solution which I think was dikstra's algo. I knew dikstra's algo solved such problem but didn't remember what it was and so I could not understand his clues. In the end he asked me for a run time complexity of a solution that I wasn't sure of so I failed to answer that as well.
Next round was right after this round.
one interviewer gave me an easy question related to meeting room which I was able to solve. Other interviewer asked me to design a parking garage application at a low level starting with DB schema. I think I failed to satisfy the interviewer there as well and might have replied rudely to a suggestion. I was a bit frustrated from my last round trying to figure out dikstra's algo.
They didn't ask me to write code to run against any inputs in any round. Only asked to write the code and discuss the solution.
I applied through a recruiter. I interviewed at Goldman Sachs (Bengaluru) in Mar 2026
Interview
They take 2 rounds for FTC, in which 1st round would be coderpad and java basic questions. 2nd round Java and its Frameworks along with the internals of java functions and Design level questions.
Interview questions [1]
Question 1
How tha hashmap and hash set works internally and which one would be faster. along with Tree set internal implementation.
Phone interview, online interview,
Phone interview was better . Pretty basic expectations.
Online interview - need to solve problem in hackathon . Easy to medium hard leet code problems . Need to write test cases and execute them as well
good interview and difficult. i was not much prepared so i did not performed well in the interview, but the interview experience was great did not get selected though Thanks
Interview questions [1]
Question 1
Technical questions around my technology and experience