The Goldman Sachs SWE Interview Guide
See how Goldman Sachs actually hires software engineers: the HackerRank assessment, the recorded HireVue, the Superday itself, and the desk match that decides when you sign. Then see what each rung from Analyst to Partner pays, and drill the questions candidates report from recent loops so nothing in the room surprises you.
- Loop length: 4 to 8 weeks
- Expected difficulty: Medium coding, high fit bar
- Online assessment: HackerRank
- Onsite format: Superday, 3 to 5 rounds
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
Application and recruiter screen (20 to 30 min · phone)
Goldman takes an enormous volume of applications, so the first human step is a short call with a recruiter rather than an engineer. They confirm your background, your work authorization and start date, and which part of the firm you are aiming at. Goldman Engineering spans Global Banking and Markets, Asset and Wealth Management, and Platform Solutions, and the recruiter's real job on this call is routing you toward a business that has an open seat. Be ready to say in one clean sentence what you have built and where you want to sit, because vague answers get parked rather than rejected.
- Name the division. Saying "markets engineering" or "core platform" moves you through the routing faster than saying you are open to anything, and it shapes which Superday panel you land in front of.
- Have the logistics straight. Notice period, location preference, visa status and any other live processes all come up on this call, and fuzzy answers stall the scheduling for a week.
- Not everyone gets this call first. Campus and early-career applicants are often sent straight to the online assessment, and the recruiter conversation only happens once they clear it.
HackerRank online assessment (60 to 90 min · HackerRank)
Goldman runs its coding screen on HackerRank, auto-graded and on a hard timer. Most candidates report two or three problems, and some tracks bolt on a multiple-choice section covering complexity, core data structures, and language behavior. Almost nobody reads your resume closely until this is cleared, so treat it as a real cut rather than a warm-up. Scoring is by hidden test cases, which means a half-finished clever approach scores below a plain solution that handles every edge case.
- Test cases decide the score. Handle empty input, single elements, duplicates and integer overflow before you spend any time making the solution faster, because partial credit tracks cases passed.
- Budget the clock deliberately. Bank the easiest problem quickly and leave the bulk of the window for the hardest one, since an untouched problem scores close to zero however good the other two are.
- Fundamentals can appear. Some tracks mix in multiple-choice questions on time and space complexity, data structures, OOP and your primary language, so go in warm on the basics.
HireVue recorded interview (~30 min · recorded video)
Many Goldman candidates, especially at Analyst and Associate level, record a HireVue before they ever speak to an engineer. A prompt appears on screen, you get a short window to think, and you record one or two takes with nobody on the other end. The questions are mostly behavioral, why Goldman, why this division, a time you delivered under pressure, with the occasional short technical or problem-solving prompt folded in. It feels awkward precisely because there is no interviewer to react to, and candidates who ramble lose this round on delivery rather than on content.
- Rehearse out loud, on camera. The format punishes people who think on the page, so practice structured two-minute spoken answers until they land cleanly without sounding memorized.
- Make "why Goldman" specific. Generic investment-bank answers read as filler; tie your interest to a product, a desk, or a class of system the firm actually runs.
- Check the setup before you start. Quiet room, stable connection, camera at eye level. The recording is all the reviewer sees, and a technical fault can burn one of your two takes.
First technical interview (45 min · shared editor)
One live round with a Goldman engineer on a shared editor, usually one or two problems on core data structures. This is the first stage where how you talk counts as much as what you type: restating the problem, naming your approach before you write anything, and reasoning about time and space out loud. Interviewers routinely follow a working solution with fundamentals questions, on complexity, on object-oriented design, or on how your language handles something specific. Coding in silence is the most common way candidates lose a round they technically solved.
- Talk through the approach before you type. State the brute force, state why it is too slow, then state the better idea, so the interviewer can steer you before you burn ten minutes down a dead end.
- Expect follow-ups once the code runs. Complexity, alternative data structures, OOP design and language internals all come up after the problem is solved, and they carry real weight in the write-up.
- Readable code carries the round. Write correct, well-named code you can walk through line by line and justify every choice in, rather than a compressed optimum you cannot defend.
The Superday (3 to 5 rounds · one block)
The Superday is Goldman's signature round and the real gate: three to five interviews back to back in a single block, run virtually or on site depending on the division and the hiring cycle, with a mix of engineers and senior people from the business. Expect at least two hands-on coding rounds on core data structures, at least one heavily behavioral round, and often a desk-flavored conversation about how systems support trading, risk, or a client product. Interviewers compare notes afterwards, so a story you tell in round two can be picked up and probed in round four, and inconsistencies get noticed. Stamina is a genuine factor: the candidates who are sharp for the first two rounds and flat by the fifth are the ones who get turned down on fit rather than on skill.
- Coding, more than once. Arrays and strings, hash maps, trees, recursion, sorting and searching, plus complexity you can defend, with edge cases handled before anyone asks about them.
- Fit is weighted heavily. Why Goldman, why this desk, and how you behave when a deadline slips or a production issue lands, each answered with your exact role and the actual outcome.
- Know how your work touches the business. Desk-facing interviewers ask how a system serves trading, risk or a client, and a candidate who can connect engineering decisions to money stands out sharply.
Desk match and offer (1 to 3 weeks · after the Superday)
After the Superday your interviewers write up feedback and the hiring team decides together, which is why a strong coding day can still stall on one weak fit round. Experienced hires usually go through a desk or team match on top of that, because the offer belongs to a specific business rather than to Goldman in general. Level and compensation then need internal sign-off, and a Vice President title takes noticeably longer to approve than an Analyst one. Campus offers can land within days of the Superday, while experienced-hire offers commonly take one to three weeks from the last round to a signed contract.
- One weak round can sink the loop. Feedback is compared across interviewers, so a flat behavioral answer sitting next to strong coding reads as a risk rather than as a rounding error.
- Desk match adds calendar time. You are hired into a specific business, and waiting for the right seat to open is the single biggest source of variance in the overall timeline.
- Level and pay need sign-off. Senior titles go through more approval steps, so the gap between a verbal yes and a signed offer widens as you go up the ladder.
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?
Usually six stages: a recruiter screen, a HackerRank online assessment, a recorded HireVue, one live technical interview, a Superday of three to five back-to-back rounds, and then desk match and offer approval. Not every candidate sees all six. Campus applicants are often sent straight to the assessment before any recruiter call, and some experienced hires skip the HireVue entirely.
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?
Goldman's onsite, run as three to five interviews back to back in a single block, virtually or on site depending on the division and the hiring cycle. It mixes hands-on data-structures coding with heavily weighted behavioral rounds, and often a desk-flavored conversation about how systems support trading, risk, or a client product. Interviewers compare notes afterwards, so consistency across every round matters more than one standout answer, and candidates who fade by the last round get turned down on fit rather than on skill.
How hard is the Goldman Sachs SWE interview?
The coding sits at a standard interview medium rather than at exotic algorithm difficulty, and candidates most often report core data structures rather than obscure tricks. The tighter tests are the fundamentals follow-ups that come after each solution, and the fit bar across the Superday, where one flat behavioral round can sink an otherwise strong technical day.
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 judgment 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. A discretionary year-end cash bonus is a defining part of Goldman comp and can be a large share of total pay, especially on the markets side in a strong year. Above certain levels part of the award is delivered as Goldman Sachs restricted stock units instead of cash, and those vest in three equal annual installments.
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 judgment and architecture questions.
What is the Goldman Sachs HireVue?
A recorded video interview that many candidates, especially at Analyst and Associate level, complete before they speak to an engineer at all. A prompt appears on screen, you get a short window to think, and you record one or two takes with nobody on the other end. The questions are mostly behavioral with the occasional short technical prompt, so rehearse structured two-minute answers out loud and check your camera, room and connection before you start.
How long does the Goldman Sachs interview process take?
Most candidates see four to eight weeks from the recruiter screen to a signed offer. The assessment, the HireVue and the technical round usually run inside the first two or three weeks, the Superday is scheduled after that, and the decision follows within one to three weeks. Campus offers can arrive within days of the Superday, while experienced hires wait longer because of desk matching and level approval.
Can I reapply to Goldman Sachs after a rejection?
Yes, and reapplying is common. No fixed waiting period for engineering roles is publicly documented, and candidates commonly come back in the next cycle or apply to a different division or desk. Use the gap to close the specific weakness the loop exposed, since the same assessment and Superday format will come around again.
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.