We use analytics and advertising cookies to understand how the site is used and whether our ads on Facebook and Instagram work. They are set only if you accept. See our Privacy Policy for details.
Prep for Goldman Sachs engineering interviews - the HackerRank assessment, CoderPad live coding, a Superday of back-to-back technical and behavioral rounds, and the OOP, multithreading, and design depth that rises from Analyst to VP.
Goldman Sachs employs a large engineering workforce across trading platforms, risk, consumer and transaction banking, asset management, and core infrastructure. Its engineering interview guide says it assesses technical ability through phone interviews, onsite interviews, and live-coding platforms such as CoderPad and HackerRank. It asks for in-depth understanding of at least one language, preferably C/C++, Java, Python, or JavaScript, and lists APIs, object-oriented programming, multithreading, testing, and edge-case handling as fair game, along with data structures (arrays, hash maps, linked lists, stacks, trees, heaps, graphs, queues) and algorithms (binary search, dynamic programming, recursion, sorting). It says to aim for an optimal solution rather than one that simply works, and to explain and justify your choices. Campus candidates start with a HackerRank assessment: a 30-minute Software Fundamentals challenge for everyone, plus a 45-minute Software Diagnostics challenge for Engineering roles, where you debug an existing Django, Node.js, or Spring Boot application with a limited built-in AI assistant. Experienced hires more often start with a recruiter call and a CoderPad interview with an engineer. The final stage, widely called the Superday, is several back-to-back interviews of 30 to 60 minutes with engineers at different levels, one-on-one or in pairs. The mix shifts with level: Analyst loops are mostly coding, while Associate and VP loops add system design and deeper questions about your past systems. Finance knowledge is a bonus, not a requirement.
Goldman names binary search, dynamic programming, recursion, and sorting. Candidate reports for the HackerRank and CoderPad stages describe Easy-to-Medium problems with occasional harder ones - arrays, strings, hash maps, BFS/DFS. Practice reaching the optimal version and stating its complexity.
Goldman lists arrays, hash tables and maps, linked lists, stacks, binary trees, heaps, graphs, and queues, and may ask about time and space complexity of library structures. Know what your language's standard collections do under the hood.
Goldman's guide calls out OOP, APIs, and testing. Expect to model a small system with clean classes and interfaces, especially at Associate and VP, and to write or describe tests for edge cases.
Java is widely used across Goldman engineering, and Spring Boot is one of the Software Diagnostics stacks. Any of C/C++, Java, Python, or JavaScript is acceptable - but if you pick Java, expect collections, concurrency, and JVM questions.
Light at Analyst, standard at Associate and VP. Practice transactional systems, messaging, caching, and rate limiting, with attention to correctness, auditability, and failure handling - the concerns of financial systems.
Goldman's interviews focus on how you have handled real work situations. Prepare stories on teamwork, conflict, ambiguous requirements, and a mistake you owned, plus a specific reason for choosing Goldman over a tech company.
Goldman lists multithreading. Know threads, locks, race conditions, deadlocks, and thread-safe data structures well enough to discuss them in a coding or design round.
Only for some roles. Goldman says roles that need it may test probability and statistics or applied math; the Quant Strategist track has its own math challenge. Standard software engineering roles rarely go deep here.
Curated walkthroughs for the bounded designs that show up in Goldman Sachs's system design rounds. Capacity estimation, architecture, deep-dives, and trade-offs.
Idempotency keys, double-spend prevention, the ledger model, and why eventual consistency is wrong for balances. The interview where ambiguity costs you money.
Two-phase commit, sagas (choreography vs orchestration), TCC, idempotency keys, and the compensation logic that turns multi-service writes into something a customer-support agent can untangle.
Partitions, consumer groups, replication, retention, and the exactly-once myth - the implementation details Kafka users gloss over until they don't.
Consistent hashing, eviction, replication, and what really happens when a single hot key takes down the cluster.
Five algorithms, three sharding strategies, one fail-open vs fail-closed decision. The bounded design that surfaces in every backend interview loop.
Sample STAR answers, common prompts, pitfalls, and follow-up strategies for the behavioral themes that decide Goldman Sachs's loop.
The most universal behavioral question. Tested everywhere. The signal is in how you investigate the disagreement, not in how you 'won.'
Tested at Google, Anthropic, OpenAI, and any senior+ loop. Strong candidates show how they get curious; weak candidates show how they get anxious.
Microsoft's Growth Mindset core. Also tested at Google, Anthropic, and any company that screens for self-awareness. The signal is whether you actually changed.
The senior+ signal. Can you drive cross-team work, mentor, and build consensus when nobody reports to you - or do you only execute when given a mandate?
The software engineer learning path and the judgment cases that mirror this loop's execution and metrics questions.
506 MCQs and 256 coding challenges, grouped by topic. Free preview shows question titles - premium unlocks full content.
Behavioral and system design rounds reward practice with a live AI interviewer that probes follow-ups, not silent reading.
Start an AI mock interview →Per Goldman's Guide to HackerRank Success: a 30-minute Software Fundamentals challenge of data structures and algorithms problems in your chosen language for every candidate, and a 45-minute Software Diagnostics challenge for Engineering applicants, where you work inside an existing Django, Node.js, or Spring Boot app to diagnose and fix issues. A limited AI assistant is available in Diagnostics; it helps with syntax, navigation, and clarifying the problem, but will not give you the solution. Goldman suggests a HackerRank practice assessment first.
Goldman's advice is to practice working within an existing codebase: reading unfamiliar code, debugging, writing tests, and making targeted changes rather than building from scratch. Clone a small open-source Django, Express, or Spring Boot app, break something, and practice finding and fixing it under a 45-minute clock. Use the AI assistant the way you would at work - to speed up, while checking its suggestions yourself.
Superday is the common name for the final round: several back-to-back interviews, usually 30 to 60 minutes each, one-on-one or in pairs, with engineers from the team at different levels. Goldman does not share the interviewer lineup in advance. Candidate reports describe two to four rounds mixing coding, design, and behavioral questions; the exact mix depends on the team, level, and location.
Analyst loops, including campus hires, lean heavily on the HackerRank assessment and data structures and algorithms coding. Associate loops add more object-oriented design, language depth, and some system design. VP loops expect you to lead a system design discussion, defend past architectural decisions, and show judgment on reliability and tradeoffs; behavioral questions focus on leading work and people.
No. Goldman's guide states that candidates are not to review CoderPad questions in advance or share them afterward. Prepare by practicing the topics instead: Goldman lists the data structures and algorithms it draws from, and its CoderPad problems are standard computer science puzzles.
No. Goldman says its people come from all backgrounds and that knowledge of financial markets is a bonus, not a requirement. Having a clear reason for wanting to build technology at a bank, rather than at a pure tech company, does help in the behavioral rounds.