Goldman Sachs · Primly Community

Goldman Sachs onsite / final round, how it really goes (2026 format)

corp_refugee · 5 replies

cleared the Goldman Sachs onsite earlier this year. wanted to write up the final round experience because the information out there is mostly from 2021-2023 and the format has shifted.

current format (as of early 2026): fully virtual for most technology roles. they may do in-person for senior/VP-level or certain desks but expect virtual by default. they schedule 4 interviews across a single day or sometimes split across two days.

my day: 9:00am: coding round 1 10:00am: coding round 2 11:30am: system design 1:30pm: behavioral

30-minute breaks between each. that sounds like a lot but you're mentally drained by round 3.

coding rounds. both were in a Google doc. no IDE autocomplete, which matters more than you'd think for a 45-minute interview. one interviewer jumped in when i got stuck and gave a nudge; the other didn't. problems were medium/hard range, both had multiple valid approaches and they wanted to discuss tradeoffs.

system design. i wrote about this separately. very finance-context-heavy. they care about auditability and failure modes more than most.

behavioral. the interviewer was a senior engineer on the team i was interviewing for. not HR. they asked me two main questions and went very deep on each. i used one story for two different questions with different framing and they noticed and called it out gently. have three distinct stories minimum.

debrief timing. mine came 5 business days later. the recruiter called, which is usually a good sign. email-only is riskier. they gave me verbal notice of the outcome before the formal letter arrived.

overall impression. more process-oriented than FAANG, less emphasis on algorithmic cleverness and more on sound engineering judgment and communication. if you've been grinding hard leetcode, dial it back a little and work on your verbal walk-through.

5 replies

infra_ines

the "email-only is riskier" thing for debrief delivery is actually a pretty universal tell, not just Goldman. if they call you it's usually good news. if it's an email with a calendar link for "next steps discussion" you might be bracing.

frontend_fran

no autocomplete in a Google doc for 45 minutes sounds painful. i can write java in a doc but my brain starts forgetting standard library signatures under pressure. any tips for prepping for that specifically?

corp_refugee

just code in a plain text editor for a few sessions during prep. deliberately turn off intellisense. after a few hours it becomes much less disorienting.

jp_newgrad

using the same story twice and getting called out on it is kind of haunting me. i only have like 4 good work stories from my internship.

brand_ben

the fact that the behavioral interviewer was a senior engineer on the team is interesting. not a recruiter or HR. that changes how i'd prep, i'd be more specific about technical tradeoffs in my stories.