It consisted of 3 coding questions to be done in 1 hour, along with 10 MCQ's with no negative marking.
2 coding questions were moderate and 1 was advanced (based on modifications on a 2-D array).
The MCQ's were pretty easy and based on general topics like recursion, OOP's concepts, Pointers, Determine the Output and some puzzles.
The interviewer made me feel comfortable and asked me about my internship and various projects that I had undertaken. Then he asked me questions on linked lists, arrays and DP. The main focus was on building upon the solutions I was giving him and coming up with the most efficient way to solve them.
Overall, the interview went smoothly and the interviewer gave adequate hints.
This round the questions were more advanced. One question was on finding the various permutations of a character array of given length, in the best way possible. Here also the focus was on how you approach the problem and your thought process behind a particular solution.
Then I was asked a puzzle which took time but eventually I solved it and the interviewer was pleased with the answer.
The interviewer again gave hints and the round ended with me asking him questions about Goldman Sachs.
The interviewer asked about my internship in detail and then went on to ask 2 more questions.
First was a backtracking question and it took almost 50 min to come up with the right solution. The interviewer gave some hints that helped me solve it properly.
There was a question on trees that was also tough and I could not solve it completely.
Then she asked me some HR questions like 'Why Goldman Sachs', etc. Overall, the interviewer was friendly but the questions were very tough.
After giving a brief introduction of myself, I was asked 1 datastructure question and 1 puzzle.
Both required thinking a lot and the were continuosly asking what I was thinking about the problem and why.
They were satisfied with the answers that I gave and the round ended with me asking them questions about the culture at Goldman Sachs.
Always engage the interviewer and let them know how you are thinking about the solution. That will tell them about your mindset and you might get some hints in the right direction if you are going astray.