The interview process started positively. There were five telephonic discussions before I was requested to fly to Bangalore for further F2F rounds. All telephonic rounds were mostly technical in nature, with questions ranging from design aspects to problem-solving skills.
The F2F rounds also went well and took five hours for the on-campus interviews. After the F2F, there were a few more telephonic discussions with the VP of Tech.
I was told in the 16th round that it was the final deciding round, and after that interview, I felt positive about receiving an offer. However, the HR personnel called again and asked for one more telephonic interview with another VP.
Overall, the whole process was very time-consuming. The main issue is that I was asked to bear all travel expenses to Bangalore, which would be reimbursed later. However, the HR personnel have been completely unmoved, even after four weeks have passed since my travel to Bangalore and with repeated requests for reimbursement via email. I was told things were positive, but now there has been no reply to follow-up emails for the last two weeks.
It was a huge loss of my money and time. For other good techies, I would advise you to think twice before interviewing with Goldman Sachs for work in a proprietary language, which the outside world has no regard for.
Design chessboard templates.
STL related questions.
The following metrics were computed from 10 interview experiences for the Goldman Sachs Senior Software Engineer role in Bengaluru, Karnataka.
Goldman Sachs's interview process for their Senior Software Engineer roles in Bengaluru, Karnataka is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Goldman Sachs's Senior Software Engineer interview process in Bengaluru, Karnataka.