Goldman Sachs · Primly Community

Goldman Sachs technical program manager (TPM) interview, here's what the four rounds actually covered

hardware_hugo · 4 replies

Finished my GS TPM loop in February 2026 and figured I'd write this up since I couldn't find a single recent post when I was prepping.

Background: 7 years in B2B SaaS, mostly technical delivery with some light infra ownership. The GS TPM role I applied to was on the platform engineering side, so not consumer, not trading. That context matters for how they scoped questions.

The process was four rounds, all virtual:

Round 1: Recruiter screen, 30 min. Standard role-fit stuff. They asked a lot about what "technical" means in my background. If you're coming from a non-engineering TPM track this is where they'd probably screen you. Be ready to talk about specific systems, dependencies, API contracts, not just delivery process.

Round 2: Technical screen, 60 min. This was 1:1 with a senior engineer. We did a system design: design a distributed task scheduler that handles retry logic and priority queues. Didn't need to code but I was expected to talk through consistency tradeoffs, queue depth monitoring, backpressure handling. GS cares a lot about operational rigor, they kept asking "what happens when this breaks at 2am."

Round 3: PM/program management, 60 min. Behavioral plus a case. The case was: you're running a multi-team infrastructure migration and one dependency team is 3 sprints behind. Walk me through how you escalate, re-scope, or replan. Classic TPM scenario, but they wanted specific artifacts: RACI, dependency map, escalation matrix. Mentioning these by name helped.

Round 4: Cross-functional leadership panel, 90 min. Three interviewers back-to-back, 25-30 min each. One was a director-level person who asked mostly about influencing without authority and how I navigate regulatory/compliance constraints on timelines. GS operates in a heavily regulated environment and they wanted to see that I've dealt with audit requirements affecting delivery.

I got an offer. Happy to answer specifics in comments.

One thing I'd flag: GS TPM is not a typical tech-company TPM role. You need to be comfortable with a lot more governance overhead. The tone in interviews reflected that. Less startup scrappiness, more "how do you document this for a regulator."

4 replies

growth_gabe

Super useful. Did they ask much about agile/scrum mechanics or was it more about program-level planning? Trying to gauge how process-heavy the prep needs to be.

pm_priya

Not really scrum mechanics. More like program-level sequencing, dependency tracking, and how you handle slippage at the portfolio level. "We missed a milestone, what do you do" was the flavor, not sprint ceremonies. Agile knowledge is assumed but not the focus.

infra_ines

The regulatory angle is real. I interviewed for a platform role there a while back and they asked multiple times about change management process and how I'd handle an emergency change request in a regulated window. Goldman doesn't run like a startup and they want you to know that going in.

tired_recruiter

From what I've heard from candidates, the TPM bar at GS is unusually high on the technical side compared to most non-FAANG companies. A lot of people think the role is mostly coordination and then get surprised by the systems design round.