Taro Logo

Software Engineer Interview Experience

March 12, 2018
Negative ExperienceNo Offer

Process

I think they need to ramp up their interviewing process drastically.

I was hunted by a recruiter on LinkedIn and scheduled a call, but I didn't receive one. I had to reach out to them to ask if they had missed the schedule, which apparently they had. After rescheduling, we finally had the screening call, which was only about 5 minutes long.

Anyway, I made it past the first round. One of the questions was quite challenging; it was something called the "Partition Problem." I solved the first question in about 5 minutes, and then the recruiter threw another question at me.

Here's the catch: these recruiters seem to be pretty clueless. As soon as they presented the second question, I recognized it as the "Partition Problem," which is NP-Hard and was famously solved by the mathematician Ramanujan. I told them, but the individual hadn't heard of the "Partition Problem" or "Ramanujan." I was stunned.

Regardless, the only way to solve that problem is if you knew the question beforehand and used a DP approach, which of course, I couldn't, and I was out.

The shameful part is that I had to follow up with the recruiter for about a month to get feedback.

Was this helpful?

Interview Statistics

The following metrics were computed from 284 interview experiences for the Goldman Sachs Software Engineer role in United States.

Success Rate

13%
Pass Rate

Goldman Sachs's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive42%
Neutral37%
Negative21%

Candidates reported having good feelings for Goldman Sachs's Software Engineer interview process in United States.

Goldman Sachs Work Experiences