Java Position - Dallas Payment Team
Two rounds of phone tech interviews + 5 rounds of back-to-back virtual onsite interviews.
Unprofessional Team.
1st round: Questions about data structures. It seemed the interviewer didn't use Java. When I mentioned I would like to use an ArrayList, she didn't know it. She asked me if it was an Array or a List. It's fine, we can talk about general data structures.
2nd round: Questions about software tools and lifecycle.
3rd round: Two interviewers asked me about String, StringBuilder, HashMap, and ArrayList. They asked how to implement HashMap and how to implement ArrayList. One of them asked me to describe how to implement a HashMap. I answered with using an array with buckets, a hash to get the index, and a linked list for conflicts. Then, another interviewer asked again how to deal with the conflict. OK, FINE. I know the other way: set the element to the next unused position. OBVIOUSLY, he didn't listen to my previous answer carefully. He asked me again how I could retrieve the conflicted element. Compare the key value. "How???"
4th round: Questions about REST APIs. Implement TinyURL with REST API. Good experience.
5th round: BST. How to insert a tree node. Another question: code review. They gave me a couple of lines of code and asked me to provide advice to make it better.
I can say Goldman Sachs, but my experience sucks. They move very, very, very, very slow. Some of the interviewers are not professional. They are not qualified to be interviewers.
Phone rounds are questions on LeetCode.
The following metrics were computed from 23 interview experiences for the Goldman Sachs Software Engineer role in Dallas, Texas.
Goldman Sachs's interview process for their Software Engineer roles in Dallas, Texas is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Goldman Sachs's Software Engineer interview process in Dallas, Texas.