goldman sachs logo
Goldman Sachs· Frontend Developer

Goldman Sachs | Reject | Rookie Mistake

Posted
13 Jul 2025
288 reads

Summary

I interviewed for a Frontend Developer role at Goldman Sachs, which resulted in a rejection after I struggled with one coding problem and made a rookie mistake in my preparation, particularly around managing pressure and articulating my approach.

How it went

Round 1 - Technical (1 Hour) Interviewer: Friendly and supportive

Question 1:

Variation of Second Smallest.

Before coding, I was asked to clearly explain my understanding of the problem and approach.

I completely blanked out — couldn’t think clearly under pressure, even though it was a relatively simple problem.

I was expected to generate my own edge case test cases. Spent ~30 minutes on this and couldn’t make progress.

Question 2:

Twisted version of [LeetCode 1086. High Five].

Solved it in 5 minutes with a clean approach. Interviewer appreciated the solution and allowed me to retry the first question.

Back to Question 1:

Came up with a working solution in O(n log n), but the expected solution was O(n).

Questions asked (2)

  1. 01

    Find Second Smallest Element in an Array

    Data Structures & Algorithms

    I was presented with a variation of the problem to find the second smallest element in an array. Before coding, I was asked to clearly explain my understanding of the problem and approach. I was also expected to generate my own edge case test cases. An O(n) solution was expected.

  2. 02

    Twisted Version of High Five

    Data Structures & Algorithms · Medium

    I was given a twisted version of LeetCode 1086. High Five. The original problem typically asks to calculate the average of the top five scores for each student. I needed to adapt this to the specific twisted requirements provided during the interview.

    Open the problem

How they prepared

I had 4 days to prepare for the interview, during which I focused primarily on Goldman Sachs-specific questions, though none of them were asked. My key learnings for future preparation include: being able to articulate the problem and my approach before jumping into code, practicing solving problems under pressure, simulating actual interview environments during prep, being prepared to generate edge cases independently, and learning to reset my mindset quickly if I get stuck.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Goldman Sachs recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!