Engineering Analyst applicants have rated the interview process at Goldman Sachs with 3.5 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 83% positive. To compare, the company-average is 60.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Engineering Analyst roles take an average of 73 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Goldman Sachs overall takes an average of 33 days.
Common stages of the interview process at Goldman Sachs as a Engineering Analyst according to 6 Glassdoor interviews include:
IQ intelligence test: 17%
Group panel interview: 17%
One on one interview: 17%
Presentation: 17%
Background check: 8%
Drug test: 8%
Personality test: 8%
Skills test: 8%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 months. I interviewed at Goldman Sachs in Jan 2022
Interview
Hirevue with 4 questions (2 about markets/news, 2 about personality)
Coding Assessment through hacker rank
Super day
Assessment and Super day consisted of leetcode mediums and some mathematics questions from linear algebra and mathematical statistics
I did an online test for programming first, after this there was a hirevue, after this I got rejected after a long wait. The difficulty of the online test was not that bad. Hirevue questions were behavioural.
I applied through college or university. I interviewed at Goldman Sachs (Bengaluru) in Aug 2025
Interview
OA followed by 3 Tech/HR rounds. They ask medium DSA, SQL and sometimes system design as well. Prepare well from Trees & about how you can scale systems for interview. OA had DP, Graph questions more.
Interview questions [1]
Question 1
Questions were related to trees such as how to insert in BST, print the outer layer of the tree.
I applied through college or university. I interviewed at Goldman Sachs (Bengaluru)
Interview
I had two rounds. In the first round, the interviewer was really nice and made the experience comfortable, not stressful. Since my subproject involved machine learning, he asked related questions—like how I’d retrieve specific values (x, y, z) from a dataset—and even touched on some terminology . I also had to explain the model I used and code parts of it. Then we moved to technical questions: HashMap-related problem, and tree traversal (in-order, post-order), along with some sorting logic.
The second round was just a single coding question. I was later waitlisted and eventually informed they had selected other candidates.