First telephonic: Given student names and scores in respective subjects, print the average for each subject for each student. Second telephonic: Given two arrays of intervals, merge intervals. Third telephonic: (Blank entry)
45 minutes: Emulate a snack jar where each person gets to vote for their preferred snack. The people's votes should represent the probability with which the candy will be picked from the jar. 45 minutes: Interview with product managers about projects, processes, and the roles of people in the team I worked with.
I breezed through all the telephonic interviews, which were pretty simple. All the interviewers were happy with what I spoke and solved. Then I was called onsite. My flight got delayed, so the onsite was shortened to three interviews only.
First hour: Design a Hotel Management system. This was a pretty interesting discussion with the interviewers; we discussed several pros and cons for several approaches. Second hour: Two interviewers, who were recently hired, interviewed me. It was evident from their faces that they had absolutely no interviewing experience whatsoever. They came in and asked me to design a restaurant management system. I told them it was pretty similar to what I was asked in the previous round of the interview. They were taken by surprise by this. Then, one of them asked me to design a Car manufacturing system. I said okay, and then, as I was thinking about it, they (the two interviewers) were talking among themselves about why the previous interviewers asked design questions. Then they asked me to switch to problem-solving. When one of the interviewers was googling for questions to ask, right in front of me, the other interviewer decided to ask me a naive question just to stall until the other one searched for a question. I quickly solved that naive question (finding the kth last node in a linked list). The other interviewer then came up with the first Google result for Goldman Sachs' interview questions. I solved it, but all this hassle gave me no time to code the solution. Third round: Hiring manager. Asks behavioral questions and about my previous projects. I answered them pretty effectively, I thought, looking at the reaction of the interviewer. Then the interviewer got extra involved, trying to get as much information as possible about the existing processes we follow in my current company, how it works well to match the pace of the competition, and the stringent deliverables.
In all, I felt this interview process was a waste of my valuable time. It was more intended for them to learn more from experienced candidates rather than seriously interviewing them. It's a shame there is no way to segregate or identify such interviews.
Design Hotel Management System
Find the k-th last node from the end.
The following metrics were computed from 2 interview experiences for the Goldman Sachs Software Engineer role in San Francisco, California.
Goldman Sachs's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Goldman Sachs's Software Engineer interview process in San Francisco, California.