{"id":76,"date":"2026-06-03T00:00:00","date_gmt":"2026-06-03T00:00:00","guid":{"rendered":"https:\/\/springgreen-curlew-885344.hostingersite.com\/blog\/goldman-sachs-interview-guide\/"},"modified":"2026-06-19T05:46:36","modified_gmt":"2026-06-19T05:46:36","slug":"goldman-sachs-interview-guide","status":"publish","type":"post","link":"https:\/\/lastroundai.com\/blog\/goldman-sachs-interview-guide","title":{"rendered":"Goldman Sachs Interview Guide 2026"},"content":{"rendered":"

The Goldman Sachs interview process for technology roles is one of the more predictable in finance-tech, which sounds like good news. It mostly is. But “predictable” doesn’t mean forgiving. Goldman replaced in-person first-round campus interviews with HireVue specifically to expand beyond the schools they had historically recruited from, according to HireVue’s own writeup on the redesign<\/a>. That’s a meaningful change in surface area. More applicants get in the door. The bar for making it through doesn’t move.<\/p>\n

At LastRound AI<\/a>, we’ve watched candidates prep for Goldman Sachs interviews using our AI interview copilot across dozens of live mock sessions. The patterns are pretty consistent: people over-rotate on LeetCode hard problems and under-prepare for the “Why Goldman over Big Tech?” question, which trips up a surprising number of otherwise strong candidates. More on that below.<\/p>\n

\n

Why the Goldman Sachs interview feels different from FAANG<\/h2>\n

The short version: Goldman is a technology company that has to explain that to people. The longer version involves 30 years of SecDB, a proprietary risk platform that Goldman engineers built before “fintech” was a word, and which is reportedly still one of the most sophisticated real-time pricing systems running anywhere. The firm has open-sourced parts of that work through GS Quant on developer.gs.com<\/a>, a Python toolkit for quantitative finance. Worth reading before your interviews, not because they’ll ask about it directly, but because it tells you what kind of engineering culture you’re walking into.<\/p>\n

What you’ll hear from interviewers is a variant of: “we are a technology company that happens to be in finance.” That framing is genuine. What it means practically is that the interview values overlap with Google or Amazon on technical depth, but the domain context matters in ways it doesn’t at pure SaaS companies. You’re expected to know what a trade execution looks like end-to-end. You don’t need a CFA. But “I’m not really a finance person” reads as lack of preparation, not refreshing candor.<\/p>\n

The work-life balance question comes up constantly in the candidate prep sessions we run. Honest answer: tech hours at Goldman are not banking hours, but they’re not Google hours either. Expect something closer to a demanding product company during market events, quarterly closes, and regulatory filing deadlines. Most teams don’t have on-call rotations in the classic SRE sense, but when a trading system misbehaves before market open, people are expected to respond.<\/p>\n<\/section>\n

\n

The Goldman Sachs interview stages, one by one<\/h2>\n

The full process runs four to eight weeks depending on whether you’re a campus hire or lateral. Here’s what each stage actually involves.<\/p>\n

\n
\n

Stage 1: Online assessment (HackerRank)<\/h3>\n

Three coding questions, 120 minutes. You choose between a pure programming track or a combined programming and math track. The math track covers probability and basic statistics at a level that’s somewhere between a quantitative finance interview and a GMAT quantitative section. Most software engineer candidates take the programming track. The questions are medium-difficulty DSA: you won’t see DP hard problems here, but a naive O(n^2) solution probably won’t pass the test cases on time.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Stage 2: HireVue<\/h3>\n

This is the stage that catches people off guard if they’ve never done a one-way video interview before. No interviewer. You record your answers to pre-set questions: typically five to eight questions, 30 seconds to read each, two minutes to answer. Two optional retakes per question. Goldman AI scores the responses, though humans do a final review before decisions are made.<\/p>\n

Question types are behavioral plus a market awareness question or two. “Tell me about a time you disagreed with a technical decision and what you did about it.” “What’s a recent development in financial technology that interests you?” The behavioral questions are standard STAR format. The market question is the one people blank on because they didn’t think to prep for it.<\/p>\n

\n

One practical note: do your HireVue somewhere quiet with a clean background and stable internet. Goldman’s stated reason for rolling out HireVue was to “get to more places” and assess more candidates than campus visits allowed. The trade-off is that technical glitches make you look disorganized, even if the content of your answer is fine.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

\n
\n

Stage 3: Technical phone screen (CoderPad, 60 min)<\/h3>\n

Live coding, usually CoderPad. One interviewer, sometimes two. The questions tend toward practical data structures and algorithms rather than competition programming. Goldman is a Java shop for many production systems, so if you know Java well, bring it. They’re not hostile to Python or Go, but OOP concepts come up more directly here than they do at pure web companies.<\/p>\n

Finance-tinged problems appear here sometimes. “Given a stream of trade prices, find the maximum profit from a single buy-sell pair” is a sliding window problem dressed in trading clothes. The framing is intentional. Interviewers want to see whether domain context registers with you or whether it’s just noise. Say the words “bid-ask spread” correctly once and you’ve signaled more than a paragraph of explanation would.<\/p>\n<\/div>\n<\/div>\n

\n
\n

Stage 4: SuperDay<\/h3>\n

Three to five back-to-back interviews, usually in a single afternoon. For campus hires it’s closer to three. For lateral mid-career roles it tends toward five. The mix for engineering tracks typically includes: one or two technical coding rounds, one system design round, one behavioral round, and a hiring manager conversation that is half behavioral and half “why Goldman.”<\/p>\n

System design at Goldman is genuinely financial. Not “design Twitter” but “how would you architect a distributed market data feed that handles 100K price updates per second with guaranteed ordering?” Low-latency tradeoffs come up. Consistency vs. availability under network partition matters. If you’ve only prepped FAANG-style “design Instagram” problems, this is where you’ll feel the gap.<\/p>\n

The “why Goldman over a tech company” question happens in almost every SuperDay. I’d argue it’s the single most predictable differentiator in the whole process. Candidates who have a specific answer (a real project they read about, a trading system architecture that interested them) pass. Candidates who give the “prestige and learning” answer in generic terms tend not to.<\/p>\n<\/div>\n<\/div>\n<\/section>\n

\n

Goldman Sachs interview questions: what actually gets asked<\/h2>\n

These are patterns we see across the stages. Not a leaked question bank, just honest categorization.<\/p>\n

Coding<\/h3>\n
\n