Junior Developer Interview Experience - United States
Process
The interview included one CodePad question, followed by a couple of scripted behavioral questions.
It felt as though the interviewer was “forced” to interview me.
He also spent a lot of time questioning my conflict resolution skills, presenting various hypothetical situations and scenarios where someone might take credit for my work.
Judging by his focus on this, it seems to be a common issue within his department or the company.
Questions
CodePad: Compress strings like "aaabbbcc" to "a3b3c2", and "aabb" to "a2b2".
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the Goldman Sachs Junior Developer role in United States.
Success Rate
Goldman Sachs's interview process for their Junior Developer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Goldman Sachs's Junior Developer interview process in United States.
Goldman Sachs Work Experiences
- 4.0Jr. Oracle DeveloperJunior Developer • Current EmployeeJanuary 24, 2018Pros: I have learned some good knowledge from my team.Cons: It is nice to work at this place.
- 4.0Smart people, high salarySoftware Engineer • Former EmployeeDecember 1, 2025Pros: All teammates were really smart, and the company offered a high salary.Cons: The working hours could be long for night calls.
- 5.0Good place to work, nice peopleData Engineer • Current EmployeeBengaluru, Karnataka, IndiaNovember 27, 2025Pros: Good place to work, nice people.Cons: Can get stagnant sometimes, when you work with legacy code.
Goldman Sachs Interview Questions
