The Goldman Sachs SWE Interview Guide
See how Goldman Sachs runs its software engineer hiring: the HackerRank assessment, the screen, and the Superday, plus what each rung on the Analyst-to-Partner ladder actually pays. Then drill the questions candidates report from recent loops so nothing in the room surprises you.
- Loop length: 3 to 5 weeks
- Expected difficulty: Mostly medium
- Online assessment: HackerRank
- Onsite format: Superday
Goldman Sachs levels & pay
- Analyst (Entry)
- Associate (Mid)
- Vice President (Senior)
- Executive Director (Lead)
- Managing Director (Staff+)
- Partner (Executive)
The Goldman Sachs SWE interview, round by round
HackerRank online assessment (~90 min · timed, HackerRank)
An auto-graded coding test sent early in the process, usually two or three problems against the clock, sometimes with a short multiple-choice section on computer-science fundamentals. It filters hard before a human reads your resume, so treat it as a real round rather than a warm-up.
- Timed data-structure problems. Full test-case coverage scores far higher than a clever partial solution, so handle edge cases before you optimize.
- Watch the clock. The window is tight for the number of problems, so bank the easy one fast and leave room for the harder one.
- Fundamentals can appear. Some tracks add multiple-choice on complexity, data structures, or core CS, so do not walk in cold on the basics.
Recruiter and HireVue screen (20 to 30 min · call or recorded)
A recruiter confirms your background, target division, and timeline, and many candidates also complete a HireVue: recorded video answers to behavioral and short technical prompts with limited prep time. It is your first read on the team and their first read on your communication.
- Know your desk. Goldman engineering spans markets, platform, and consumer tech, so be clear on which area you are targeting and why.
- Rehearse for recorded answers. HireVue gives you seconds to think and one or two takes, so practice concise, structured responses out loud beforehand.
- Light technical prompts. Expect a quick fundamentals or problem-solving question mixed in with the behavioral ones.
Technical phone interview (45 min · shared editor)
One or two live coding problems with a Goldman engineer on a shared editor. This is the first round where communication counts as much as the answer: clarifying the problem, narrating your approach, and reasoning through complexity out loud is what separates a clear pass from a borderline call.
- Reach a working, optimal solution and talk through the trade-offs as you build it, rather than coding in silence.
- Expect fundamentals follow-ups. Interviewers often probe time and space complexity, OOP, or language specifics after the problem is solved.
- Readable beats rushed. Clean, correct code you can explain outperforms a fragile optimum you cannot defend.
The Superday (3 to 5 rounds · back to back)
The main event: several back-to-back interviews in one block, usually virtual, mixing hands-on data-structures coding, behavioral fit, and rounds that fold in markets or finance context relevant to the desk. It is fast and professional, and you need to hold your form across every round, not just the coding ones.
- Coding, more than once. Core data structures and algorithms on a shared editor: arrays and strings, hash maps, trees, recursion, and complexity you can defend. Optimal solutions with edge cases handled unprompted.
- Behavioral and fit, throughout. Why Goldman, why this desk, how you work under pressure and with a team. Bring concrete STAR stories with your exact role and the outcome.
- Markets and business context. Desk-facing rounds may touch how systems serve trading or risk, and light finance or product reasoning, so know how your work connects to the business.
The decision (1 to 2 weeks after)
Your interviewers compare notes and the hiring team makes the call, often with a team-match step to place you on a specific desk. Consistency across every round matters here: a strong coding round paired with a flat behavioral or fit answer can stall an otherwise good Superday.
- Fit is weighted heavily. Goldman screens hard for people who will thrive in its culture, so thin behavioral answers sink strong technical loops.
- Team match can add time. Placement on a specific desk sometimes follows the loop, which stretches the timeline.
- Decisions take one to two weeks and can run longer during hiring pauses or when a desk match is still being worked out.
How hard is the Goldman Sachs interview?
Difficulty mix: 20% easy, 70% medium, 10% hard.
How to prepare
Build a daily coding rhythm (Weeks 1 to 4)
Code every day, timed, on a shared editor to mirror HackerRank and the live rounds. Rotate through the patterns Goldman leans on, arrays and strings, hash maps, trees, recursion, and complexity analysis, starting at medium and mixing in the occasional hard as the weeks go on.
Drill fundamentals and complexity (Weeks 1 to 3)
Alongside the coding, refresh the CS basics interviewers probe after a solution: time and space complexity, core data structures, OOP, and your primary language's quirks. Goldman rounds often turn into a fundamentals conversation, so be able to reason about trade-offs, not just recite them.
Prepare fit and Goldman context (Weeks 2 to 3)
Write concrete STAR stories for why Goldman, why this desk, and how you work under pressure and on a team. Learn enough about the division you are targeting, markets, platform, or consumer, to connect your engineering to the business, and rehearse concise answers for the HireVue format.
Run full mock Superdays (Week 4)
In the last week, put it together: sit a few back-to-back sessions that pair coding with behavioral and business-context questions, so your focus and answers hold across three to five rounds in a row the way they must on the real Superday.
Recently asked
Trapping rain water
About Goldman Sachs
Goldman Sachs is one of the world's leading investment banks, founded in 1869 and headquartered in New York. Its business spans global banking and markets, asset and wealth management, and platform solutions, serving corporations, financial institutions, governments, and individuals across market-making, advisory, financing, and trading.
Goldman Sachs Engineering is one of the largest divisions at the firm, building the low-latency trading systems, risk and pricing platforms, and client-facing products that run the business. Engineers work on tooling like the Marquee developer platform and Marketstream data feeds, and much of the work sits close to markets, where reliability, speed, and correctness carry real money.
Frequently asked
How many rounds is the Goldman Sachs interview?
Typically five stages: a HackerRank online assessment, a recruiter or HireVue screen, a technical phone interview, and a Superday of three to five back-to-back rounds, followed by the decision and a possible team match.
What is the Goldman Sachs HackerRank assessment?
An early, timed, auto-graded coding test, usually two or three problems and sometimes a short multiple-choice section on CS fundamentals. It filters before a human reviews your resume, so prepare for it like a real round rather than a formality.
What is a Goldman Sachs Superday?
The onsite: several back-to-back interviews in one block, usually virtual, mixing hands-on data-structures coding, behavioral fit, and rounds that fold in markets or finance context for the desk. It is fast and professional, and consistency across every round matters.
How hard is the Goldman Sachs SWE interview?
Mostly medium. The bulk of the coding sits at medium difficulty with a smaller share of easy and hard, and the tighter test is often the fundamentals depth and the fit bar rather than exotic algorithms.
Do I need finance knowledge to interview at Goldman Sachs?
Not deep finance, but it helps. Coding and fundamentals decide most of the loop, though desk-facing rounds may touch how systems serve trading or risk, so knowing how your engineering connects to the business is a real edge.
What is the difference between Analyst and Associate at Goldman?
Analyst is the entry title for new-grad and early-career engineers; Associate is the next rung, expected to own features end to end and take on more design and delivery responsibility. The Associate loop puts more weight on judgement and ownership.
What are the Goldman Sachs engineering levels?
The ladder runs Analyst, Associate, Vice President, Executive Director, Managing Director, and Partner. Analyst and Associate are the junior rungs, VP is broad and senior, and Executive Director through Partner are the leadership tiers.
Does Goldman Sachs pay a cash bonus?
Yes. Cash bonus is a defining part of Goldman comp and can be a large share of total pay, especially in strong years and on the markets side. Senior engineers also receive a portion in deferred GS stock, which vests over several years.
What coding topics does Goldman Sachs focus on?
Core data structures and algorithms: arrays and strings, hash maps, trees, recursion, sorting and searching, and complexity analysis. Expect fundamentals follow-ups on time and space complexity, OOP, and your primary language after you solve the problem.
Does Goldman Sachs ask system design?
Design shows up more at senior levels and can appear in Superday rounds as a discussion of a real service or platform. Junior loops lean on coding and fundamentals, while VP and above face more design judgement and architecture questions.
What is the Goldman Sachs HireVue?
A recorded video interview some candidates complete after the recruiter stage: you answer behavioral and short technical prompts on camera with limited prep time and one or two takes. Practice concise, structured answers out loud before you record.
How long does the Goldman Sachs interview process take?
Usually three to five weeks from the assessment through the Superday, then one to two weeks for the decision. A team-match step to place you on a specific desk can add time at the end.
Can I reapply to Goldman Sachs after a rejection?
Yes. Candidates generally wait several months before reapplying, and applying to a different division or role is common. Use the gap to close the specific weaknesses the loop exposed.
How should I prepare for the Goldman Sachs interview?
Keep a daily timed coding rhythm on core patterns, drill CS fundamentals and complexity for the follow-ups, prepare fit stories and desk context for the Superday, and rehearse concise answers for the HireVue. Karavine's Goldman Sachs pack is exactly this plan with worked solutions.
Is the Goldman Sachs interview mostly behavioral or technical?
Both carry real weight. Coding and fundamentals gate the early rounds, but the Superday and final decision lean hard on fit: why Goldman, why the desk, and how you work under pressure. Strong code with flat behavioral answers still stalls.
Goldman Sachs interview questions on Karavine