Goldman Sachs Software Engineer interviews typically combine a HireVue or recruiter screen, a live CoderPad/HackerRank coding round, a multi-interview Superday with DSA and system design, and a resume-heavy final round with the hiring manager.
$122K
Avg. Base Comp
$160K
Avg. Total Comp
3-4 rounds
Typical Rounds
2 months
Process Length
Goldman Sachs' Software Engineer interview process typically opens with a recruiter call, a HireVue round, or an online assessment of easy-to-medium LeetCode-style problems. It then moves into a live CoderPad round, usually with two data-structure and algorithm problems. These range from string manipulation and BFS to harder classics like Trapping Rain Water or median of two sorted arrays.
From there, most candidates report a Superday-style virtual onsite with back-to-back rounds, often around 45 minutes each. These rounds mix three areas:
Interviewers consistently care about how you explain complexity and optimize, not just whether you reach a working answer.
A resume walkthrough is a recurring theme, both in HireVue behavioral prompts and in Superday or hiring manager conversations. Be ready to explain your projects clearly and to handle simple Java fundamentals if that matches your background. The process typically closes with a hiring manager or Managing Director conversation that leans on background and behavioral questions.
One candidate reported the full process taking around two months, and another described it as stretching over several weeks. Post-Superday communication can be slow, so asking for a decision timeline is worthwhile. Round count and difficulty vary by team and level, so treat any single loop as one data point rather than a fixed script.
Synthesized from 105 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Goldman Sachs process.
I started with a recruiter screening call that was pretty quick, just ten minutes to confirm basic fit and interest. Then came the online assessment, which felt straightforward enough — a 45-minute CoderPad session focused on SQL and Python coding problems. The first question asked me to find the longest substring of repeating characters and return an array with the starting index and length. The second was about finding the maximum average of candidate marks given as a 2D array. Both were solid medium-difficulty problems that tested basic data structure manipulation and iteration.
A few months passed before I heard back, and then I got invited to the super day. That consisted of two back-to-back 30-minute technical interviews. The first leaned more toward system design concepts, while the second was pure algorithm-focused — similar in spirit to the online assessment. The interviewers were friendly and approachable, which helped ease the pressure. The main issue was pacing: the structured 30-minute slots didn't leave much breathing room. By the time I'd finished explaining my solution and coding it up, there was barely time to ask questions about the role or the team. I wished I'd been more aggressive about using my talk-time efficiently.
Then came a manager round lasting 45 minutes, followed by a 90-minute cross-functional collaboration interview that tested how I'd work with other teams. The technical bar was solid — they went beyond just "does this code compile" and dug into edge cases, complexity tradeoffs, and how I'd communicate solutions. The DSA questions ranged from medium to hard, and there were some foundational CS core topics mixed in as well. Unfortunately, I didn't advance past this stage. Looking back, I think the challenge wasn't any single interview but the cumulative rigor across all of them.
Prep tip from this candidate
The technical rounds heavily emphasize DSA at medium-to-hard difficulty; drill string manipulation and 2D array problems specifically. Practice explaining solutions concisely in under 10 minutes to leave time for follow-ups and clarifications, as the structured timing is tight.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Goldman Sachs
Given a string, write a function to find its first recurring character.
| Question | |
|---|---|
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Size of Joins | |
| Level Of Rain Water In 2D Terrain | |
| Google Maps Improvement | |
| Append Frequency | |
| Cyclic Detection | |
| Minimum Absolute Distance | |
| Production Model Monitoring | |
| Success Measurement | |
| Target Indices | |
| Cross-Region Inventory Sync | |
| Portfolio Platform Architecture | |
| How Many Friends | |
| Messenger Service Design | |
| Optimistic vs Pessimistic Locking | |
| The Longest Journey | |
| Cloud-Agnostic Deployments | |
| SageMaker Deployment Architecture | |
| Deciding Between Solutions | |
| Impossibly Iterative Fibonacci | |
| Shortest Path Algorithms | |
| Alternative Vendor Tradeoff | |
| Client Solution Pushback | |
| LRU Cache 1 | |
| Using APIs for Downstream Tasks | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with an online application followed by a recruiter phone call, a HireVue round focused on behavioral and resume questions, or an online coding assessment with easy-to-medium LeetCode-style problems. Any of these can come before a live interview is scheduled.
Most candidates report a live coding round on CoderPad, usually two data-structure and algorithm problems in a single session (roughly 15-60 minutes). Difficulty ranges from string manipulation and BFS problems to harder questions like Trapping Rain Water or median of two sorted arrays. Interviewers expect a narrated, optimized approach.
Candidates typically face a Superday-style stage with several interviews of around 45 minutes on the same day. Rounds cover DSA problems (heaps, 2D DP, graphs, tries) and system design prompts (caching scenarios, chatbot scaling, financial transaction processing, parking or portfolio management systems). Some also include SDLC and engineering-practice questions on Agile, CI/CD, pull requests, and story scoring.
Interviewers frequently spend time on resume walkthroughs and past projects, sometimes as a dedicated SDLC/resume segment of the Superday. Some candidates also report behavioral prompts such as how they would test something, welcome a new team member, or explain recursion simply. Basic Java fundamentals tied to a candidate's background can also come up.
The last stage is typically a conversation with the hiring manager or a Managing Director. It focuses on background, behavioral questions, and how candidates handle real-world scenarios. Some candidates report notably slow communication after the Superday, so following up for a decision date is advisable.
