INTERVIEW GUIDE
Goldman Sachs Software Engineer Interview: Questions & Process
The interview process
Questions you're likely to get
Technical
- Reverse a linked list and walk through the time and space complexity.
- Given an array, find whether it contains any duplicates — optimize for time.
- Implement an LRU cache with O(1) get and put.
- Merge two sorted linked lists into one sorted list.
- How does a hash map handle collisions, and what's the worst-case lookup?
- Design the classes for a simple order book using OOP principles.
Role-specific
- How would you design a system to process incoming trades with low latency?
- When handling monetary amounts in code, how do you avoid rounding and precision bugs?
- Brainteaser: what's the expected number of coin flips to get two heads in a row?
Behavioral
- Why Goldman Sachs, and why engineering in finance rather than a pure tech company?
- Tell me about a time you worked under intense deadline pressure.
- Describe a time you had conflict on a team and how you resolved it.
- Walk me through a project you're proud of and the hardest technical decision in it.
Practice these problems live
Relevant LeetCode problems for the Goldman Sachs Software Engineer loop. Start a live, AI-run coding interview on any of them — or open the problem on LeetCode.
How to answer (worked examples)
What Goldman Sachs looks for
- Solid CS fundamentals — data structures, complexity, and clean coding under time pressure
- Genuine interest in finance and the firm, not a generic tech-job pitch
- Composure under pressure and tight deadlines
- Clear communication while coding — you narrate your approach and tradeoffs
- Attention to correctness, especially around money and edge cases
- Red flag: a weak or canned 'why Goldman' answer, or silent coding with no reasoning
FAQ
How hard is the coding bar at Goldman?
Generally easy-to-medium DSA rather than the hardest algorithmic puzzles. Solid fundamentals, clean code, and clear complexity analysis matter more than esoteric tricks — but you do need to be fast and correct under the timer.
What is a Superday?
Goldman's onsite (often virtual): several back-to-back interviews in one block — usually a mix of technical coding rounds and behavioral/fit rounds, sometimes with a brainteaser. Pace and stamina matter.
Do they ask brainteasers and probability questions?
Sometimes, especially for engineering roles touching trading or quant teams. Practice basic expected-value and probability reasoning, but they're a minority of the questions, not the focus.
Which language should I use?
Use what you're strongest in — Java, Python, and C++ are all common. Goldman has a large Java footprint, but interviewers care about your problem-solving more than the language.
How much does 'why finance' really matter?
More than at most tech companies. A strong candidate with a hollow motivation story often loses to a slightly weaker coder who clearly wants to be in finance.
Back-to-back rounds reward people who've rehearsed out loud — the coding narration, the 'why Goldman' answer, the pressure stories. Run this exact interview with OfferLoop's realtime voice coach so Superday feels like a repeat, not a surprise.
Practice this interview out loud →Related
OfferLoop is an independent interview-practice tool and is not affiliated with, endorsed by, or sponsored by Goldman Sachs. All company names and trademarks are the property of their respective owners.
Interview formats vary by team, level and year, and this guide is compiled from general knowledge of publicly discussed hiring processes — treat it as preparation material, not an official description of Goldman Sachs's current process.