Technical program manager behavioural interview questions

As asked

Tell me about a programme that was heading for a slip and you turned it around. What was happening and what did you do?

Sample answer outline

Pick a real story. Walk through: the symptoms you spotted (which feature was actually behind, which team was overloaded, which dependency was decaying), the diagnosis (often a missed assumption or hidden work), the corrective action (rescope, reallocate, escalate, replan), and the outcome. The strong answer notes that 'saving' a programme often means cutting scope honestly, not heroics. Show that you got buy-in from the affected stakeholders, not just decreed the change.

Expect these follow-ups

• What scope did you cut and how did you negotiate it?
• Could you have spotted this two weeks earlier?
• What changed in your programme process after?

As asked

Walk me through a time you missed an important program deadline. What happened, what was the impact, and what did you learn?

Sample answer outline

Strong candidates are direct about what went wrong and their specific contribution to it (not just external factors). They describe the impact honestly, explain what they communicated and when, and articulate a specific behavioral change they made afterward. Candidates who deny any personal accountability or blame entirely external factors are weak.

Expect these follow-ups

• When did you first know the deadline was at risk?
• What would have happened if you had communicated the risk earlier?

As asked

Describe a time you drove a critical program outcome when you had no direct authority over the people you needed to move. What was the situation, and specifically how did you get people to act?

Sample answer outline

Strong answers describe building credibility through preparation and technical understanding, framing requests in terms of shared goals rather than personal authority, creating visibility that aligned the other party's self-interest with your program's needs, and knowing when to involve a mutual manager rather than forcing the issue. The candidate should give specific tactics, not just describe the outcome.

Expect these follow-ups

• What is the most useful influence tactic you have found in an engineering org?
• How do you maintain the relationship after you have pressured someone to do something they did not want to do?

As asked

Tell me about the most complex cross-organizational initiative you have managed. How many teams, how many months, and what was the biggest coordination challenge?

Sample answer outline

The story should be concrete and scaled appropriately to the role level. Strong candidates describe the specific coordination challenge clearly (not just 'lots of teams') and their specific mechanisms for managing it: a shared tracker, a program-level standup, a dependency review board, or a clear escalation path. They name what they would do differently.

Expect these follow-ups

• At what scale does your coordination approach break down?
• What is the single most important thing you did to hold that initiative together?

As asked

Tell me about a time you strongly disagreed with a program or technical decision made above your level. How did you handle your disagreement, and what happened?

Sample answer outline

Strong candidates describe voicing the disagreement clearly, with data, through the right channel, at the right time. Once the decision was made, they committed to executing it fully while documenting their concern. They distinguish between continuing to fight a settled decision (wrong) and asking for a decision revisit when new evidence emerges (right). They do not just say 'I always disagree and commit.'

Expect these follow-ups

• Did the decision turn out to be wrong, right, or unclear in hindsight?
• Is there a situation where you would refuse to execute a decision you disagreed with?

As asked

Tell me about a time leadership asked you to deliver more scope within the same timeline and the same team. How did you respond?

Sample answer outline

Strong candidates describe pushing back with data: showing the capacity model, the current critical path, and the explicit trade-off the additional scope would require. They offer options (extend timeline, reduce other scope, add resources) rather than simply saying no. They make the trade-off visible so leadership can make an informed decision, and they are honest when the request is simply not achievable.

Expect these follow-ups

• What did leadership decide, and what was the actual outcome?
• How do you handle it when leadership says 'just make it work'?

As asked

Team A says they are blocked on Team B's API change. Team B says they are blocked on Team A's clarified requirements. Both have escalated to you. What do you do?

Sample answer outline

Get the three of you in a room (literal or video) within 24 hours. Establish facts, not accusations: what does each team actually need from the other, in concrete terms, by when. Surface the underlying tension, which is usually misaligned priorities or different interpretations of the same brief. Pick a path: scope down to unblock, or escalate to the joint leadership for a prioritisation call. The TPM's job is not to mediate forever, it is to force a decision and document it. Follow up in writing so nobody re-litigates next week.

Expect these follow-ups

• What if the leaders of the two teams disagree?
• How do you stop the same teams getting stuck on each other repeatedly?
• When is the right answer 'this should not be two teams'?

As asked

Tell me about a program that was in serious trouble when you inherited it or took it over. What was the situation, what did you do, and what was the outcome?

Sample answer outline

Strong answers describe a rapid diagnosis phase (identify the real problem, not the surface symptoms), a stabilization plan, and honest communication with the sponsor about what is realistic. The outcome does not have to be a complete rescue; a candidate who recovered 60% of the program and honestly communicated the rest is often more credible than someone who claims a flawless turnaround.

Expect these follow-ups

• How long did it take you to understand what was actually wrong?
• What did the previous TPM get wrong, and how did you know?

As asked

Tell me about a time two senior engineers on your program had a fundamental disagreement that was blocking progress. How did you resolve it?

Sample answer outline

Strong answers describe understanding both positions (not just the loudest one), finding the underlying constraint or interest behind each position, and driving toward a time-boxed decision rather than an open-ended debate. The candidate should show they can make a recommendation or escalate appropriately when the team cannot converge, and that they maintain the relationship with both parties after the decision.

Expect these follow-ups

• What if one of the engineers is more senior than you and does not respect your role?
• How do you ensure the losing side stays engaged and does not quietly undermine the decision?

As asked

Describe a situation where your technical understanding of an engineering problem directly changed a program decision or outcome. What did you understand that a non-technical PM might have missed?

Sample answer outline

Strong candidates describe catching a hidden dependency buried in a technical design doc, identifying that an architecture choice would make a future milestone much harder than estimated, or recognizing that two teams were building the same thing. The story should be specific and technical enough to be credible, showing genuine engineering fluency rather than surface-level familiarity.

Expect these follow-ups

• How did you develop that level of technical depth in that domain?
• Has your technical understanding ever led you to the wrong conclusion on a program?

As asked

Tell me about a time you were handed a mandate with very little clarity and had to create enough structure to actually make progress. How did you do it, and what mistakes did you make?

Sample answer outline

Strong answers describe proactive discovery, stakeholder alignment on what success looks like, and a willingness to propose a direction even when leadership had not decided. The candidate should mention at least one mistake: over-scoping the discovery phase, committing to too much before requirements were stable, or misreading a stakeholder's true priority.

Expect these follow-ups

• How long is too long to spend in discovery before you start execution?
• What is the fastest you have ever gone from 'no clarity' to 'first milestone shipped'?

As asked

Walk me through a time a key stakeholder was actively resistant to your program. What was the root cause of their resistance, and how did you handle it?

Sample answer outline

Strong candidates diagnose the resistance: was it fear of losing resources, disagreement with the direction, or a past bad experience? They describe addressing the root cause rather than managing the symptoms, adjusting the program to incorporate legitimate concerns where possible, and escalating when the resistance crossed into blocking behavior. They maintain a professional relationship throughout.

Expect these follow-ups

• Was there any part of the stakeholder's concern that turned out to be valid?
• What would you do differently if you encountered that stakeholder again?

As asked

Tell me about a time you had to make a real tradeoff between shipping speed and quality or safety on a program. What did you decide, and do you still think it was the right call?

Sample answer outline

Strong candidates make the tradeoff explicit rather than avoiding it. They describe what was at stake on both sides, how they made the decision, who was involved in it, and what actually happened. They are honest if the decision turned out to be wrong and what they learned. Candidates who claim they never had to make this tradeoff are not credible.

Expect these follow-ups

• How did you communicate the quality risk to stakeholders before making the call?
• What signal would have changed your decision?

As asked

Describe a time you had to give difficult feedback to a peer engineer, team lead, or senior stakeholder on a program where you had no direct authority over them. What was the feedback, how did you deliver it, and what happened?

Sample answer outline

Strong answers describe specific, behavior-based feedback delivered directly and promptly rather than accumulated resentment or passive-aggressive hints. The candidate explains how they framed the feedback (impact on the program, not personal judgment), what they expected the person to do with it, and how the relationship evolved. The outcome does not need to be perfectly positive.

Expect these follow-ups

• How do you give feedback to someone who is known to react defensively?
• What is the feedback you are most glad you gave, looking back?

As asked

Tell me about a time when something changed mid-program and your entire plan had to be rethought. What triggered it, how fast did you replan, and how did you communicate the change?

Sample answer outline

Strong answers show the candidate can absorb a major change (strategy shift, key engineer departure, technical failure) without freezing or panicking. They describe assessing impact quickly, communicating the new reality to stakeholders early, and presenting a revised plan with clear options rather than just a problem statement.

Expect these follow-ups

• What did you stop doing to make time for the replanning?
• How did the team respond to the change?

As asked

Tell me about a programme that failed despite your best efforts. What went wrong and what would you do differently?

Sample answer outline

Pick a real failure. The interviewer is testing for self-awareness, not perfection. Cover: the goal, the plan, the warning signs you saw (or missed), the decisions you would change. Strong answers identify a process failure (lack of explicit decision rights, missing dependency surfaced too late, scope that kept growing) or a judgement failure (over-trusted a team's estimate, underestimated political opposition). End with what you carried forward into the next programme.

Expect these follow-ups

• What was the warning sign you missed?
• Whose fault was it?
• What did the org learn, not just you?

As asked

You are joining as a TPM on a team that has never had a TPM before. Engineers are sceptical. How do you build trust in the first 90 days?

Sample answer outline

Listen first. Spend the first weeks understanding the team's actual problems before proposing process. Find one or two concrete pains the team has (a dependency that keeps slipping, a meeting that wastes everyone's time, a status report nobody reads) and fix them visibly. Avoid the new-TPM trap of adding rituals: each new meeting costs trust. Show that you are technical enough to follow the work without making every engineer explain it twice. Be the person who unblocks, not the person who tracks. Trust accumulates through small wins, not through credentials.

Expect these follow-ups

• What if the engineering manager is also new and unsure of your scope?
• What is one ritual you would add early?
• How do you handle a senior engineer who refuses to engage with you?

As asked

Walk me through a time your program sponsor was disengaged or unavailable when you needed a key decision, and how you handled it.

Sample answer outline

Strong candidates describe a clear process for pre-empting this: aligning with the sponsor early on escalation criteria so they know when they will be needed. When the sponsor is unavailable, they describe the options they considered, what they decided to do themselves versus defer, and how they documented the interim decision to get explicit sponsor sign-off later. They do not simply wait.

Expect these follow-ups

• What did you do to prevent the same thing from happening again?
• Is there a type of decision you would never make without sponsor sign-off, no matter what?

As asked

Have you ever run a program where a major organizational change, like a reorg, leadership change, or acquisition, happened mid-program? How did you manage it?

Sample answer outline

Strong candidates describe proactively re-mapping stakeholders after the change, re-confirming program mandate with the new leadership, and communicating program status and any at-risk elements to new decision-makers quickly. They do not assume the old mandate still holds. They also address how they kept the team focused and motivated through the uncertainty.

Expect these follow-ups

• What is the first thing you do when you find out your program sponsor has changed?
• How do you protect program continuity when key engineers are moved by a reorg?

As asked

Describe a time you had to keep a team motivated through a particularly long or difficult program. What were the specific morale challenges, and what did you actually do about them?

Sample answer outline

Strong candidates go beyond generic answers like 'celebrated wins.' They describe specific morale problems: burnout from repeated slippage, disillusionment from scope changes, or lack of visibility to the impact of their work. Their interventions are concrete: a mid-program celebration, direct feedback to leadership to reduce noise, or surfacing individual contributions to senior stakeholders.

Expect these follow-ups

• What is the most effective thing you did for team morale, and why did it work?
• Is there anything you tried that made things worse?