Goldman Sachs software engineer candidates commonly report an assessment or video screen followed by live coding and, in some cases, Superday-style technical, design, and behavioral conversations.
$143K
Avg. Base Comp
$180K
Avg. Total Comp
2-5 rounds
Typical Rounds
4-20 weeks
Process Length
Goldman Sachs Software Engineer interviews described by candidates do not follow one fixed loop, but the recurring preparation theme is clear: explain the engineering decision, not just the final answer. Several candidates started with an online coding assessment, a HireVue, or both before moving to live technical conversations. Reported coding material includes arrays, strings, linked lists, graph problems, dynamic programming, binary search, priority queues, and Wiggle Sort. In live settings, be prepared to narrate complexity, identify edge cases, and explain the broad approach before or while implementing it.
Later-stage formats also vary. Some candidates encountered a Superday with two online interviews, while others described several technical rounds, a hiring-manager session, or a Zoom conversation with senior engineering staff. One reported system-design prompt involved handling high-volume data uploads. Treat that as an example rather than a fixed question, and practice turning an open-ended requirement into a structured design with clearly explained tradeoffs.
Prepare a concise walkthrough of projects listed on your résumé, including your contribution and the technical choices you made. Also expect behavioral questions about motivation, teamwork, goals, prior challenges, why Goldman Sachs, or why its engineering division. The reports span different pathways and seniority levels, so prioritize adaptable communication alongside efficient data-structures-and-algorithms practice.
Synthesized from 66 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.
The Superday was much less technical than I expected for a Goldman Sachs software engineering role. I first completed a HireVue virtual interview, and after networking with a specific team, they reached out with a Superday invitation. The conversations were largely centered on my resume rather than live coding. I was asked to walk through my projects, including explaining the architecture behind one of them, and to go deeper on the decisions I had made.
The interviewers also used the resume discussion to explore how I think in workplace situations. I got behavioral, scenario-based questions and questions about why I made particular choices, such as why I decided to use controllers. The tone was easygoing, which helped with nerves, but I still made sure I had thoughtful questions ready for them; that seemed important both for learning about the team and showing initiative. I did encounter some basic DSA discussion, but it was not the focus of my Superday and the questions felt approachable.
I ultimately received and accepted an offer. My biggest takeaway is to know every resume project beyond the headline: be ready to explain its architecture and defend your technical decisions in plain language. Also prepare a few specific questions about the team, since the conversations can be heavily behavioral and resume-driven rather than coding-heavy.
Prep tip from this candidate
Be ready to explain the architecture of every resume project and the reasoning behind choices such as using controllers. Prepare specific questions for the interviewers, since the Superday can be largely behavioral and resume-focused.
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 | |
| Target Indices | |
| Success Measurement | |
| 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 | |
| Impossibly Iterative Fibonacci | |
| Deciding Between Solutions | |
| 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 report starting through different routes: an online coding assessment, a HackerRank-style test, a CoderPad screen, or HireVue. Assessments may combine coding with broader fundamentals or behavioral prompts, while video responses may ask about motivation for Goldman Sachs and engineering.
Candidates commonly report screen-shared or CoderPad coding on data structures and algorithms. Topics vary from arrays, strings, linked lists, and hash maps to graphs, trees, dynamic programming, and heaps; interviewers may probe complexity, edge cases, testing, and optimization.
Some candidates report later technical sessions on practical architecture, such as scalable uploads, caching, data storage, distributed systems, or platform design. Typically, preparation should emphasize clarifying requirements and explaining tradeoffs rather than memorizing a single system-design prompt.
Candidates report behavioral questions throughout the process or in a later conversation. Be ready to explain résumé projects, technical choices, teamwork and ownership examples, why Goldman Sachs, and how you approach a prior challenge or ambiguous workplace situation.
