Goldman Sachs Software Engineer Interview Process 2026 Guide

The Goldman Sachs software engineer interview in 2026 usually has three stages. First comes a HackerRank online assessment, then a live CoderPad coding screen with a Goldman engineer, then a Superday of three to five back-to-back interviews covering data structures, design, your resume, and fit. The coding bar sits around LeetCode medium. Most offers are won or lost on clean code, design reasoning, and how convincingly you explain why you want to build software at a bank.

Key Takeaways

• The standard path is HackerRank OA, CoderPad technical screen, then a Superday of 3 to 5 rounds, each about 45 to 60 minutes. Campus candidates often also record a HireVue video interview.
• Goldman uses firm-wide corporate titles (Analyst, Associate, Vice President), not engineering levels. The interview bar shifts sharply between them, and the table below maps what each title is tested on.
• Coding questions skew toward arrays, strings, hash maps, linked lists, and classic design-a-class problems like an LRU cache, with fewer exotic graph or DP puzzles than at Google or Meta.
• Expect an SDLC or resume deep dive that FAANG loops rarely include: testing strategy, code review, deployment, and production incidents.
• Behavioral rounds map to the firm's commonly cited values (partnership, client service, integrity, excellence) and almost always include "Why Goldman?" and "Why a bank rather than a tech company?"
• Goldman pay leans on base salary plus a discretionary year-end bonus, with little stock below VP, so compare offers on cash and bonus history rather than headline numbers.

What do Analyst, Associate, and VP mean in Goldman Sachs engineering?

Goldman Sachs uses one corporate-title ladder for the entire firm: Analyst, Associate, Vice President, Managing Director, and Partner. Engineers sit on the same ladder as bankers and traders. That confuses applicants from tech companies, because "Vice President" sounds like an executive role when it is really a senior or lead engineer title.

Your title decides which interviews you get and how hard they push. Here is how the expectations shift in practice:

Two things stand out. First, the jump from Associate to VP is mostly about design and ownership, not harder algorithms. Second, pay is weighted toward base salary and a discretionary year-end bonus, with less stock than big tech packages at comparable titles. Check levels.fyi's self-reported data for current ranges, since they shift by office and year. Our salary negotiation guide covers how to handle a bank offer next to a tech offer.

Stage 1: The Goldman Sachs HackerRank online assessment

The HackerRank assessment is the main filter for engineering applicants, especially campus candidates. Most reports describe two coding problems, sometimes with additional multiple-choice questions on math, logic, or computer science fundamentals. Campus versions have historically run longer and mixed coding with quantitative questions. Lateral-hire versions are usually shorter and coding-only.

The problems tend to be standard LeetCode easy to medium difficulty:

• String manipulation and parsing (compression, anagrams, frequency counts)
• Array problems with hash maps or two pointers
• Sorting with custom comparators
• Simple greedy or prefix-sum problems
• Occasionally a basic graph traversal or dynamic programming question

Hidden test cases decide your score, so edge cases and time complexity matter as much as a correct-looking solution. Read the constraints before coding: an input of 10^5 elements rules out O(n²) loops. Our online assessment tips walk through a time-management routine for two-question OAs.

HackerRank also runs integrity checks, such as tab-switch tracking, copy-paste monitoring, and code similarity analysis. If you want to understand what is actually flagged, read our breakdown of whether HackerRank detects AI before your test window opens.

Stage 2: The Goldman Sachs CoderPad technical screen

The CoderPad screen is a live, 45 to 75 minute video call with a Goldman engineer, often someone from the team you would join. It usually opens with five to ten minutes on your resume, then moves to one or two coding problems in a shared CoderPad editor where your code actually runs.

Interviewers care about three things here:

1. Working code. CoderPad executes your solution, so you are expected to run it and fix failures, not just describe an approach.
2. Testing habits. Write a few test calls yourself, including empty input, duplicates, and boundary sizes. Candidates who test without being asked stand out.
3. Communication. Explain your plan before typing, state complexity, and talk through trade-offs. Our guide on thinking out loud in coding interviews has phrases that keep the interviewer with you.

Commonly reported CoderPad questions include two-sum variants, finding the first non-repeating character, merging intervals, string compression, trapping rain water, and implementing a data structure such as a stack with min, a queue using two stacks, or an LRU cache. The LRU cache comes up so often across Goldman reports that you should be able to write it from memory in your interview language:

import java.util.LinkedHashMap;
import java.util.Map;

public class LRUCache<K, V> {
    private final int capacity;
    private final LinkedHashMap<K, V> map;

    public LRUCache(int capacity) {
        this.capacity = capacity;
        this.map = new LinkedHashMap<>(capacity, 0.75f, true) {
            @Override
            protected boolean removeEldestEntry(Map.Entry<K, V> eldest) {
                return size() > LRUCache.this.capacity;
            }
        };
    }

    public V get(K key) {
        return map.get(key);
    }

    public void put(K key, V value) {
        map.put(key, value);
    }
}

Expect a follow-up asking you to build it without LinkedHashMap, using a hash map plus a doubly linked list. Then you may be asked how you would make it thread-safe. Have an answer ready that covers a single lock, a read-write lock, and why lock striping is hard for an LRU because every read mutates the recency order.

Stage 3: How is the Goldman Sachs Superday structured?

The Superday is the final round: three to five interviews of 45 to 60 minutes each, usually on one day, sometimes split across two. Experienced hires often do it over video. Campus Superdays have run both in person and virtually depending on the year and office. Each interviewer writes independent feedback, so a stumble in one round does not have to end your day.

A typical engineering Superday looks like this:

The SDLC round surprises candidates from startups and big tech alike. Interviewers ask how you test code, how a change moves from your laptop to production, how you handle a failed deployment, and what you would do if you found a bug in code that had already shipped. Regulated firms care about controls and auditability, so answers that mention code review, automated tests, staged rollouts, and rollback plans land well.

What data structures, OOP, and system design topics does Goldman test?

Goldman's technical rounds lean on fundamentals and object-oriented design more than on tricky algorithms. Prioritize these topics in roughly this order.

Data structures and algorithms

• Hash maps and sets: frequency counting, deduplication, two-sum patterns
• Arrays and strings: two pointers, sliding window, prefix sums, in-place manipulation
• Linked lists: reversal, cycle detection, merging sorted lists
• Stacks and queues: min stack, balanced brackets, queue from stacks, monotonic stack
• Trees: traversals, lowest common ancestor, BST validation
• Heaps: top-k problems, merging sorted streams
• Light dynamic programming: climbing stairs, coin change, longest common subsequence

If you want a structured problem list, the coding interview patterns cheat sheet covers every pattern above with templates.

Object-oriented and low-level design

Analysts and Associates get low-level design prompts more often than distributed systems. Commonly reported examples include a parking lot, a library management system, an elevator controller, a vending machine, and finance-flavored ones like a simple order book or a bank account ledger. Interviewers look for clear classes, interfaces, encapsulation, and sensible use of patterns like strategy or observer. Our parking lot low-level design walkthrough shows the expected depth.

Java knowledge gets probed more at Goldman than at most tech companies. Be ready for equals and hashCode contracts, how HashMap handles collisions, ConcurrentHashMap versus synchronized maps, immutability, and garbage collection basics. The firm has deep Java roots: its former GS Collections library now lives on as Eclipse Collections. Our Java interview questions list covers these areas.

System design

Associates may get a lighter system design round. VPs should expect a full one. Reported prompts include a URL shortener, a rate limiter, a notification service, and finance-adjacent systems such as a trade booking pipeline, a market data feed, or a payments ledger. For bank prompts, interviewers push on consistency, idempotency, audit trails, and what happens when a downstream system is unavailable. Practice with the URL shortener system design walkthrough, then adapt the same framework to a ledger or trade flow.

Behavioral and fit questions engineers miss at banks

The behavioral bar at Goldman is higher than many engineers expect, and it is where tech-focused candidates most often lose offers. Goldman's commonly cited core values are partnership, client service, integrity, and excellence. Your stories should map to them.

These are the bank-specific questions engineers most often fail to prepare:

1. "Why Goldman Sachs and not a tech company?" A vague answer about prestige fails. Talk about engineering problems that are specific to finance: low-latency systems, data correctness where errors cost real money, regulatory constraints, and working close to the business.
2. "Why this division?" Know which business the role supports, such as Global Banking and Markets or Asset and Wealth Management, and what engineers there build.
3. "Tell me about a time you made a mistake that affected users." This is an integrity question. Own the mistake, explain the fix, and describe what you changed so it would not recur.
4. "Describe working with a non-technical stakeholder who kept changing requirements." This is client service. Engineers at banks work directly with traders, operations, and compliance staff.
5. "Tell me about a time you disagreed with a teammate." This is partnership. Show you can disagree with evidence and still commit to a team decision.
6. "What do you know about our recent news or results?" Read the latest quarterly earnings headlines and any recent technology announcements.
7. "Walk me through your resume." At Goldman this is not a warm-up. Interviewers pick a project and ask detailed follow-ups for 15 minutes.

Use the STAR format, keep each story to about two minutes, and prepare six to eight stories you can adapt. Our list of top behavioral interview questions with STAR examples is a good bank of prompts to rehearse against.

Goldman Sachs interview timeline

The full process for an experienced hire usually takes three to eight weeks from first contact to offer. Campus programs follow a seasonal calendar that can stretch over several months.

Silence between stages is common and usually reflects batching and scheduling, not a rejection. A polite check-in with your recruiter after two weeks is fine. If you are also interviewing at other banks, the JPMorgan technical interview process follows a similar shape and pairs well with Goldman prep.

A four-week Goldman Sachs prep plan

This plan assumes you already know the basics of data structures and can code in one language.

• Week 1: 25 to 30 LeetCode easy and medium problems on arrays, strings, hash maps, and linked lists. Time yourself in a plain editor with no autocomplete.
• Week 2: Stacks, queues, trees, heaps, and light DP. Implement an LRU cache from scratch twice, once with a library structure and once with a hand-built doubly linked list.
• Week 3: Two low-level design problems and, for Associate or VP, two system design problems with a finance twist. Write up your SDLC story: how your last team tested, reviewed, deployed, and handled incidents.
• Week 4: Behavioral prep mapped to the four values, a polished "Why Goldman" answer, and at least one full mock Superday of three back-to-back rounds to build stamina.

New grads should pair this with our new grad software engineer interview guide, which covers how to talk about internships and class projects with enough depth for a resume deep dive.