Initial phone call with a recruiter about the position.
The second interview involved behavioral questions in the format of “What would you do if your coworker/manager…?” This was followed by coding questions through CoderPad, including one LeetCode easy and one LeetCode hard.
Unit tests were pre-written, and the expectation was to add to them. For the easy question, I spent more time thinking of additional unit tests, despite having working code, as the interviewer focused on that aspect.
Because the questions were nearly exact copies from LeetCode, pasted directly into CoderPad, there was limited opportunity for dialogue to ask questions. The instruction was to simply read the prompt and verbalize your thought process.
This stage could easily be an auto-timed step in the interview process rather than a live conversation. However, it did allow for clarifying questions about the role to be addressed by the interviewer.
I did not advance to the next step because I spent too much time on unit tests. The next and final step would have been a 5-hour interview with several people.
What would you do if your coworker came up to you in the elevator, saying they're getting a larger mortgage with hopes of getting a promotion soon?
What would you do if your teammate took full credit for something you worked on?
Power of 10 - LeetCode easy question.
Trapping Rainwater - LeetCode hard question.
The following metrics were computed from 23 interview experiences for the Goldman Sachs Software Engineer role in Salt Lake City, Utah.
Goldman Sachs's interview process for their Software Engineer roles in Salt Lake City, Utah is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Goldman Sachs's Software Engineer interview process in Salt Lake City, Utah.