Goldman Sachs

Goldman Sachs's Interview Process (2026)

Blog / Goldman Sachs's Interview Process (2026)

The Goldman Sachs software engineer interview process typically unfolds across several stages, blending classic DSA challenges with finance-flavored system design and a culture-heavy behavioral component. The exact number of rounds can vary depending on the team and level, but most candidates go through some version of the pipeline described below.

Initial Assessment (HackerRank or HireVue): Most candidates start with either a HackerRank online assessment featuring 2 to 3 coding problems, or a HireVue video screen with recorded behavioral questions. This stage typically takes between 60 and 120 minutes.
Technical Screen (CoderPad): A live coding session with a Goldman engineer, usually around 45 to 75 minutes. Expect a short resume discussion followed by 1 to 2 coding problems where you are expected to write and test working code.
Superday (Virtual Onsite): The core of the process, typically consisting of 3 to 5 back-to-back rounds covering DSA, system design, SDLC practices, and behavioral questions. Each round is usually 45 to 60 minutes.
Skillset and Team Fit Rounds: After the Superday, candidates often interview with 1 to 2 specific teams to assess alignment on tech stack and team culture. If one team passes, another may pick up the process without restarting from scratch.
Managing Director Round: A shorter final conversation, usually 15 to 30 minutes, with a Managing Director covering high-level technical thinking and career goals. Candidates in 2025 report occasional surprise technical questions here, so do not treat it as purely conversational.

To prepare effectively, focus your study plan around the core question types Goldman consistently tests across all stages:

Data Structures & Algorithms (DSA): LeetCode-style coding problems tested at the OA, technical screen, and Superday stages.
High-Level System Design: Designing scalable, often finance-specific distributed systems and platforms.
Low-Level Design: Object-oriented design problems with a focus on SQL schema and concurrency.
SQL and Database Design: Schema design and query challenges tied to financial data models.
Frontend Engineering: JavaScript fundamentals, performance, and frontend system design for candidates on UI-facing teams.
Behavioral: Scenario-based questions anchored to Goldman's 14 Business Principles.

1. Data Structures & Algorithms (DSA)Goldman heavily tests DSA at multiple stages, from the initial OA through the Superday. The most common patterns are Sliding Window, Two Pointers, BFS/DFS, and HashMaps, so make sure these are second nature before your first interview.Recent candidates report questions like Trapping Rain Water, Design LRU Cache, and a "Transaction Segments" problem asking you to identify strictly increasing subarrays. Parsing logs for frequent IPs and finding the highest average student score (similar to the High Five problem) also appear regularly.Goldman is known for pulling from a consistent set of tagged problems, so working through our top 100 DSA questions is a smart starting point. Supplement that with focused practice on sliding window and two-pointer patterns, which come up frequently in their medium-difficulty array and string questions.

2. High-Level System DesignThe Superday almost always includes at least one High-Level Design round, and the prompts tend to be finance-specific. Expect problems like designing a real-time trade processing system, a distributed messaging queue, or a flash sale backend under high throughput constraints.A key differentiator at Goldman is that interviewers want to hear your trade-offs explicitly stated. If you choose NoSQL for horizontal scalability, say so, and acknowledge the eventual consistency cost. Candidates who just produce a diagram without reasoning tend to struggle here.Brush up on High-Level Design concepts and practice drawing out architectures with our System Design practice tool to get comfortable thinking out loud under time pressure.

3. Low-Level DesignThe LLD round at Goldman typically centers on designing financial or operational systems with clear class hierarchies, SQL schemas, and concurrency handling. Common prompts include designing a banking system with Customers, Accounts, and Credit Cards, or a payment module using the Strategy Pattern.Interviewers at this stage are paying close attention to how you model relationships and handle edge cases like concurrent transactions. Sketch out your schema and class design before writing any code.Practice with prompts like Design Splitwise, Design a Parking Lot, and Logger Rate Limiter on our Low-Level Design practice section to build the right instincts for this format.

4. SQL and Database DesignSQL comes up both inside LLD rounds and as standalone questions, particularly for candidates targeting data-heavy or backend teams. Recent examples include designing a banking system schema, a simplified Splitwise data model, and queries like running totals of sales and customer transaction analysis.Beyond writing correct queries, interviewers often ask you to avoid certain keywords (like DISTINCT) and solve the problem another way, which tests your depth of SQL knowledge. Revisit window functions, CTEs, and join strategies as core topics.Our SQL theory section covers the concepts most likely to come up, including schema normalization and query optimization.

5. Frontend EngineeringFrontend questions are specific to candidates interviewing for UI-facing teams and do not appear in every loop. When they do show up, Goldman tends to ask about JavaScript fundamentals like hoisting and closures, polyfill implementations for things like Promise.all, and frontend system design for trading dashboards.Performance questions are also common in this track, particularly around rendering large data tables efficiently in a browser. Be ready to talk through virtual scrolling, lazy loading, and minimizing reflows.If you are targeting a frontend-heavy team, make sure your React fundamentals are solid, since React and Spring Boot are frequently mentioned as the core stack across Goldman's product teams.

6. BehavioralGoldman's behavioral rounds are directly tied to its 14 Business Principles, with a strong emphasis on Ownership, Client Service, and Integrity. Interviewers will ask scenario-based questions like "Tell me about a time you solved a high-pressure technical issue" or "Why Goldman over a pure tech company?"The most effective approach is to prepare your stories using the STAR principle and consciously tie your answers back to Goldman's stated principles. Generic leadership stories that could apply anywhere tend to land flat.Also expect a resume grilling segment where an interviewer picks a single bullet point and asks you to walk through the architecture, the failures you hit, and the measurable outcome. Our Behavioral Playbook can help you structure these stories with the specificity Goldman looks for.

ConclusionGoldman Sachs rewards candidates who combine strong fundamentals with the ability to explain their thinking clearly and connect it to real-world constraints. Focus on the question patterns that come up most often, practice talking through trade-offs in design rounds, and prepare your behavioral stories with Goldman's principles in mind. Follow the Goldman Sachs Interview Roadmap for a structured, stage-by-stage prep plan that ties everything together.