Goldman Sachs Program / Project Manager Interview Questions

1.Tell me about a project where you had to pull together teams that didn't naturally work together. How did you get alignment, and what broke down along the way?

2.Walk me through a project that went sideways because of a mistake you made. What did you learn, and where did you apply that lesson next?

3.Tell me about a time you coached someone on your team through a skill gap that was blocking project delivery. What approach did you take and how did it turn out?

4.Tell me about a time you had to tell a client or senior stakeholder something they really didn't want to hear — a missed deadline, a scope cut, or a material risk to their outcome. How did you handle it and what happened to the relationship?

5.Describe a situation where your project was the critical dependency for another team's delivery, and a key handoff was at risk of breaking down. What did you do to protect both timelines?

6.Tell me about a time you inherited a failing or off-track project and had to fundamentally change how the team was operating to get it back on course. What was broken, what did you change, and what did you learn that you've carried into every project since?

7.Estimate how long it would take to onboard 50 new corporate clients onto Goldman Sachs's Transaction Banking platform. Walk me through your assumptions.

8.A Goldman Sachs institutional client using Marquee tells you that adoption among their analysts has stalled at about 30% of licensed users despite months of availability. You've been asked to figure out what's going wrong. How do you approach this?

9.Estimate the total project management capacity you'd need to support a full migration of Goldman Sachs's internal applications from a legacy infrastructure to the GS Engineering Platform over two years. How many PMs, and what's your reasoning?

10.Goldman Sachs's Transaction Banking team is reporting that average client onboarding time increased 35% over the past two quarters, but there were no major staffing changes or system outages. How do you figure out what's driving it?

11.You're the PM on a program to launch a new Marcus savings product feature by a hard marketing date — six weeks away. Your lead engineer just told you the feature needs three more weeks of development than originally scoped, and you have no budget for additional resources. Walk me through how you decide what to do.

12.Goldman Sachs is evaluating whether to expand a pilot program — say, a new institutional client onboarding automation tool — from 5 clients to 50. You've been asked to build the business case. What's your framework and what data would you need?

13.Walk me through how you typically build and maintain a project status dashboard. What metrics do you track, and how do you decide what rises to senior leadership?

14.How do you structure a project kickoff to surface dependencies and risks before the first sprint starts? What specifically do you do in the first two weeks?

15.Your program is two months in and the engineering team's velocity has dropped 30% over three consecutive sprints. How do you diagnose the cause and what do you do differently depending on what you find?

16.You're managing a program with a fixed regulatory deadline — say, a trading compliance update tied to a new reporting requirement. Three weeks before go-live, you discover a scope item that was assumed complete but isn't. How do you evaluate the options and what do you recommend?

17.You're the PM on a platform migration — say, moving a set of Goldman Sachs internal applications from a legacy system to the GS Engineering Platform. The business owner keeps expanding the scope mid-project while engineering is already at capacity. How do you manage this without derailing the delivery or burning out the team?

18.You're managing a cross-divisional program at Goldman Sachs — say, a joint initiative between Transaction Banking and the technology division — and you have no direct authority over any of the team members. Two workstreams have been consistently missing their commitments, and their leads each blame the other. How do you break the deadlock?

19.You're running a project and a stakeholder from a different division asks you to share a draft deliverable — risk analysis, vendor comparison, something sensitive — before it's been reviewed by your manager. How do you handle it?

20.You're three weeks into a new project and you realize the team has been using a tracker and status reporting format that's creating noise rather than clarity for stakeholders. The team is comfortable with it and no one has complained. Do you change it, and if so, how?

21.You're managing a project with a vendor delivering a critical integration, and midway through you realize the vendor's technical lead has been consistently overstating progress in status updates. Delivery is still three months out. How do you handle it?

22.A senior business stakeholder wants to compress your project timeline by six weeks because of a market opportunity — but that compression would require skipping several testing phases your engineering team considers non-negotiable. How do you navigate this?

23.You're the PM on a program that spans three business divisions. Halfway through, you discover that two of the divisions have been building their components with different data standards, and the integration won't work without one side rebuilding six weeks of work. Nobody flagged it earlier. How do you handle the next 72 hours and then the next six weeks?

24.You're managing a high-visibility program, and two weeks before a board-level review, your key analytical lead tells you privately that the financial projections underpinning the program's business case are significantly overstated. They're asking you to keep it quiet until after the review. What do you do?

25.Tell me about a time you had two senior stakeholders who wanted completely different things from the same project. How did you get them to a shared definition of success?

26.Walk me through how you keep a project's executive sponsor genuinely engaged — not just updated — throughout delivery. What does good sponsorship look like in practice, and how do you cultivate it?

27.You need a team to prioritize your project, but you have no budget authority and no reporting relationship over them. Their manager keeps saying the team is too busy. How do you get traction?

28.You're halfway through a program and you realize the business stakeholder who signed off on the requirements has been replaced by someone new — and the new stakeholder has different priorities and is skeptical of the approach. How do you handle the transition without losing momentum?

29.You're running a working group where one key participant — a director-level stakeholder — keeps missing meetings, delegating to someone who can't make decisions, and returning deliverables weeks late. The program is starting to slip. How do you fix it without burning the relationship?

30.You're the PM on a high-visibility program, and you realize that two divisions have been telling their respective senior leaders very different things about the program's status and expected outcomes. Both narratives are partially true, but they're incompatible. What do you do?