Initial screening interview
Live coding interview: 2 easy tasks 2.1. Average value from the roster of multiple entries (hashtable task) 2.2. Newton approximation method implementation (divide and conquer based task)
4-hour interview with 4 different groups of people 3.1. Coding -> hashtable 3.2. SE practices: SDLC, CI/CD, testing of distributed systems 3.3. System design: design a chat application 3.4. Hiring Manager interview: experience discussion, team fit, behavioral
HCM follow-up discussing the offer details
The interview process was overall good, and I felt warm and welcomed. However, during the offer details discussion, the HCM team continued in a pushing, blaming manner with a lot of judgments, and was overall inflexible. This was even before bringing the offer to the table.
Given that the process was driven by an ED-level employee, I expected much more flexibility and thoughtfulness during the HCM follow-up. I'm really concerned about the working conditions in this company when I see such an attitude even before I have actually committed to anything.
They eventually lowballed the salary, refused to negotiate, and I had to decline. The HCM team called me after the decline without notice in the late evening, which was largely disrespectful. During the call, they devalued my CV and questioned my overall expertise and experience, trying to justify the lowballed offer to my face.
Average value from the roster of multiple entries.
The following metrics were computed from 1 interview experience for the Goldman Sachs Lead Java Developer role in Warsaw, Masovian Voivodeship.
Goldman Sachs's interview process for their Lead Java Developer roles in Warsaw, Masovian Voivodeship is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Goldman Sachs's Lead Java Developer interview process in Warsaw, Masovian Voivodeship.