Technical program manager role-specific interview questions

As asked

Walk me through exactly how you build a dependency map for a large, multi-team initiative. What information do you gather first, where do you store it, and how do you keep it accurate over the course of a six-month program?

Sample answer outline

Strong answers identify dependencies across teams early via structured interviews and kick-off workshops, capture them in a shared tool (Jira, Asana, or a dependency register spreadsheet), assign owners to each dependency, and schedule a cadence for review. The candidate should mention blocking vs. non-blocking dependencies, how they visualize the critical path, and how they escalate when a dependency slips.

Expect these follow-ups

• What do you do when a team says their dependency is 'being worked on' but there is no visible progress?
• How do you handle circular dependencies between two teams?

As asked

Describe your process for maintaining a risk register on an actively running program. How do you identify new risks, score them, and decide which ones actually get escalated to leadership versus which ones you handle yourself?

Sample answer outline

A strong answer covers a structured intake process (retrospectives, stakeholder interviews, technical review meetings), a consistent scoring rubric combining probability and impact, a clear threshold for escalation versus self-management, and a regular review cadence. The candidate should distinguish between risks and issues and show they close out risks that no longer apply.

Expect these follow-ups

• Give me an example of a risk you chose not to escalate and it turned into a real problem. What did you learn?
• How do you get engineers to actually report risks rather than hiding them?

As asked

How do you identify the critical path in a complex program, and what tactics do you use to protect it when individual milestones start to slip?

Sample answer outline

Candidates should describe using network diagrams or Gantt-style dependency chains to identify the longest path, quantifying float on non-critical tasks, and proactively staffing or unblocking critical-path items. Strong answers mention re-calculating the critical path after each significant change and communicating the impact of slippage in terms of end-date risk rather than individual task delays.

Expect these follow-ups

• How do you convince an engineering manager to put their best people on a critical-path task they consider boring?
• When do you compress the schedule and when do you reduce scope instead?

As asked

You are running a program that involves eight engineering teams, two product managers, a design team, and a VP sponsor. Design the status reporting structure: what reports do you produce, at what cadence, for which audiences, and what information goes in each?

Sample answer outline

Strong answers distinguish between a weekly operational update for the working teams (detailed, task-level), a biweekly executive summary for the VP (milestone status, top three risks, decisions needed), and an ad-hoc escalation format for urgent issues. The candidate should describe RAG status, mention what they cut to keep reports readable, and show they tailor content to each audience's decision-making needs.

Expect these follow-ups

• What do you do when stakeholders stop reading your status updates?
• How honest are you about yellow or red statuses in a politically sensitive org?

As asked

A senior director, not your program sponsor, comes to you halfway through a program and says they need a new feature added before launch. This feature would add three weeks to your timeline. How do you handle it?

Sample answer outline

Strong candidates do not say yes or no immediately. They size the impact quickly, loop in the program sponsor, and present a clear tradeoff: add the feature and slip the date, descope something else to fit the feature, or defer the feature to a follow-on phase. They document the decision, whoever makes it, and make sure everyone who is affected by the date slip is informed.

Expect these follow-ups

• What if your program sponsor and the senior director disagree?
• How do you say no to a senior director without damaging the relationship?

As asked

You are preparing to launch a new public-facing backend API that will be used by three mobile clients and two partner companies. Walk me through the launch readiness checklist you would build and run through in the two weeks before launch.

Sample answer outline

A strong answer covers technical readiness (load testing, failover testing, security review, API contract freezing), operational readiness (runbooks, on-call rotation, alerting thresholds, rollback plan), partner readiness (integration testing complete, sandbox access, documentation delivered), and go or no-go criteria with a clear decision owner. The candidate should mention a dry-run launch and a staged rollout plan.

Expect these follow-ups

• How do you handle a go or no-go disagreement between engineering and product on launch day?
• A partner says they are ready but their integration test is still failing. What do you do?

As asked

Before a program kicks off, how do you assess whether the teams involved actually have enough capacity to deliver on the proposed timeline, and what do you do when the answer is no?

Sample answer outline

Strong candidates describe gathering committed capacity percentages from each team, accounting for on-call, technical debt, and other concurrent commitments, then comparing against the effort estimates for the program's work. When capacity is insufficient they describe three options: extend the timeline, reduce scope, or negotiate additional headcount, and they present these with data to the sponsor rather than just flagging the problem.

Expect these follow-ups

• How do you handle it when an engineering manager commits capacity they do not actually have?
• What is your model for how much capacity overhead to leave for unknowns?

As asked

Describe your personal framework for when you escalate an issue versus when you resolve it yourself. Where is the line, and how do you avoid under-escalating on one end or being a constant noise generator on the other?

Sample answer outline

Strong candidates describe criteria: escalate when the issue requires authority or resources you do not have, when it has breached a risk threshold defined at program start, or when two parties cannot agree and time is burning. They avoid escalating prematurely (undermining the team's ability to self-resolve) and under-escalating (absorbing problems silently until they compound). They mention giving a one-time warning before escalating so teams are not blindsided.

Expect these follow-ups

• Tell me about a time you escalated too late. What would you do differently?
• How do you escalate without making the team feel like you are throwing them under the bus?

As asked

You have just been assigned as TPM to a program you know nothing about. How do you identify, map, and then manage all relevant stakeholders?

Sample answer outline

Strong candidates describe a structured stakeholder interview process in the first two weeks, categorizing stakeholders by influence and interest, identifying decision makers versus influencers versus observers, and tailoring communication format and cadence accordingly. They should mention revisiting the map periodically as the program evolves and identifying stakeholders who are risks (resistant, disengaged, or misinformed).

Expect these follow-ups

• How do you handle a high-influence stakeholder who is actively opposed to your program?
• What is the smallest useful stakeholder map you have produced?

As asked

What are the three to five metrics you watch most closely to assess the health of a running program, and what does each one tell you?

Sample answer outline

Strong candidates mention schedule performance index or milestone completion rate, number of open blockers and their age, open risk count and trend, dependency resolution rate, and team capacity versus committed capacity. Each metric should have a clear interpretation: a rising blocker age signals the team is absorbing problems rather than escalating. The candidate should distinguish leading indicators (early warning) from lagging indicators (confirming a problem already happened).

Expect these follow-ups

• What is the earliest leading indicator that a program is in trouble?
• How do you stop teams from gaming your health metrics?

As asked

Walk me through a program you are most proud of delivering. What made it complex, what was your specific contribution, and what would you do differently?

Sample answer outline

Strong answers are specific and self-aware. The candidate describes the scale and complexity, names what they personally drove (not what the team did), and identifies one or two genuine mistakes or things they would change. Vague answers full of 'we' language and no honest reflection are weak.

Expect these follow-ups

• What was the hardest single decision you made on that program?
• If you handed that program to someone else today, what would you warn them about?

As asked

A platform team tells you their dependency for your program will be three weeks late. Your program launch date is fixed due to a public announcement. What are your options and how do you evaluate them?

Sample answer outline

Strong candidates identify four to five options: resequence work so other teams continue while waiting, ask the platform team to deliver a stub or interim version, invest in temporarily parallelizing the blocked work, negotiate the announcement date with the business, or descope the dependent feature. They evaluate each option with the data they have and bring a recommendation to the sponsor rather than just presenting all options equally.

Expect these follow-ups

• What if the platform team's manager says their team is too busy to accelerate?
• How do you protect against this happening again in future programs?

As asked

A VP pulls you aside and demands a hard date commitment for a program milestone that you are genuinely not confident you can hit. What do you say in that conversation?

Sample answer outline

Strong candidates describe being honest about the uncertainty rather than giving a false commitment to reduce pressure in the moment. They explain what is driving the uncertainty, offer a confidence interval or a range, and describe what would need to be true to hit the VP's preferred date. They do not just say 'I need more time' without substance.

Expect these follow-ups

• The VP says 'that is not good enough, I need a date.' What do you say next?
• How do you maintain the VP's trust while telling them something they do not want to hear?

As asked

How do you define go or no-go criteria for a program launch, and how do you run the actual launch decision meeting so it is efficient and leads to a real decision?

Sample answer outline

Strong candidates describe defining criteria in advance (not the day before launch), categorizing each criterion as hard blocker versus advisory, assigning a verification owner to each criterion, and running the meeting as a structured review of green or red status for each criterion rather than an open discussion. They define decision authority clearly beforehand, so the meeting ends with a documented decision and a named decision-maker.

Expect these follow-ups

• What do you do when half the launch criteria are green and one critical one is red?
• How do you handle disagreement in the room about whether a criterion is actually met?

As asked

You are running the kickoff meeting for a new six-month program with 50 people from eight teams in the room. Walk me through the structure and content of that meeting.

Sample answer outline

Strong answers describe: executive sponsor sets the 'why' and the business context, TPM presents the charter and goals, team leads walk through their scope and how it connects to the whole, a dependency walkthrough, a risk overview, and next steps. The candidate should mention making the meeting interactive (Q and A, concerns surface), sending materials in advance, and producing a clear meeting record with action items.

Expect these follow-ups

• What is the most important outcome of a kickoff meeting?
• What goes wrong when a kickoff meeting is skipped or done badly?

As asked

Say your company sets new OKRs at the start of each quarter, but your program spans three quarters and involves six teams. How do you make sure the program stays aligned to those OKRs as they evolve, and how do you handle it when a new quarterly OKR pulls team capacity away from your program?

Sample answer outline

Strong candidates describe mapping program milestones to key results, building a lightweight traceability matrix, and establishing a quarterly re-alignment check with stakeholders. On capacity conflicts, they describe a structured prioritization conversation with the relevant VP or director, present tradeoff options with impact data, and do not absorb scope silently.

Expect these follow-ups

• What happens when two OKRs genuinely conflict for the same team's time?
• How do you communicate OKR drift to the program sponsor?

As asked

An engineering lead gives you a twelve-week estimate for a piece of work that your experience says should take five or six weeks. How do you investigate that estimate without undermining the lead or poisoning the relationship?

Sample answer outline

Strong answers describe asking the lead to walk through the breakdown, looking for gaps like testing, code review, and integration time alongside unexplained buffers. The candidate should mention comparing to similar past work, asking about known risks that justify the buffer, and framing the conversation as 'help me understand' rather than 'I think you are wrong.' They should also show they know when to accept the estimate and when to escalate.

Expect these follow-ups

• What if, after the review, you still believe the estimate is inflated?
• When is a large estimate actually correct and you should trust it?

As asked

Your program's most critical team gets pulled into a major production incident three weeks before a key milestone. The incident is expected to last four to seven days. How do you respond in the first 24 hours, and how do you replan the program?

Sample answer outline

Immediate response: assess actual capacity lost, identify which milestone tasks can proceed without the affected team, and communicate early to the sponsor. Replanning: calculate the revised critical path, identify any tasks that can be parallelized or re-sequenced, present two or three options to the sponsor with tradeoffs. The candidate should mention documenting the decision and setting a new baseline only after stakeholder sign-off.

Expect these follow-ups

• How do you rebuild team morale and pace after a disruptive incident?
• What if this is the third incident in six months affecting the same team?

As asked

You are handed ownership of a six-month, six-team program and told to set it up in Jira. Walk me through the hierarchy, fields, and workflows you create, and explain the choices you make.

Sample answer outline

Strong answers describe a clear hierarchy: program-level Epics or a Portfolio/Program board, team-level Sprints, and milestone issues with due dates. The candidate should discuss cross-team linking, custom fields for dependency status and milestone flags, and the tradeoff between tight centralized control and team autonomy over their own boards. They should mention the risk of Jira becoming stale and their process for keeping it current.

Expect these follow-ups

• How do you get six different engineering teams to actually follow the Jira structure you set up?
• What do you do when a team refuses to use Jira at all?

As asked

Why do you keep a decision log on programs you run, and what specifically does each entry contain? Give me an example of a time the log proved valuable.

Sample answer outline

A decision log captures the decision, the context and options considered, who made the decision, the date, and the rationale. Strong candidates emphasize it prevents relitigating settled questions, creates accountability, and gives new joiners context. The example should be concrete: a decision that was questioned months later and the log resolved the dispute.

Expect these follow-ups

• How long do you keep decision logs accessible to the team?
• What is the lightest-weight format you have used that still worked?

As asked

Your six teams each run two-week sprints on their own cadence. Your program milestone is twelve weeks out. How do you take sprint velocity and completion data from six teams and translate it into a reliable program-level forecast?

Sample answer outline

Strong answers describe mapping sprint outputs to milestone deliverables, tracking percentage complete on each work stream, and applying a burn-up or burn-down at the program level. The candidate should discuss the limits of velocity-based forecasting across heterogeneous teams, how they handle teams with inconsistent sprint completion, and when they override the data with judgment from technical leads.

Expect these follow-ups

• What is the earliest signal that tells you a milestone will slip, before the sprint data shows it?
• When do you show a forecast range versus a single date?

As asked

You are given a mandate to 'improve developer platform reliability' with no concrete requirements, no defined scope, and a six-month deadline. How do you start, and how do you create enough structure to begin execution?

Sample answer outline

Strong candidates describe a discovery phase: stakeholder interviews to surface pain points, data gathering (incident reports, SLO dashboards, developer surveys), and a lightweight problem statement document. They then propose a scoped set of bets with measurable success criteria, run these through a prioritization session with the sponsor, and lock down the first milestone before committing to later ones. They do not wait for perfect clarity before beginning.

Expect these follow-ups

• How do you stop the discovery phase from dragging on indefinitely?
• What if your sponsor disagrees with the priorities you surface from engineers?

As asked

Your program delivered eight weeks late and significantly over the original scope. The program is now complete. How do you structure the retrospective, and how do you make sure the lessons are actually retained?

Sample answer outline

Strong answers describe a blameless, structured retrospective with pre-work (each team fills in a template before the meeting), a timeline walk-through to surface root causes, and clear separation between 'what happened' and 'what we do differently.' The candidate should describe how they turn findings into concrete process changes and track adoption, not just write a document nobody reads.

Expect these follow-ups

• How do you get candid feedback from teams when the sponsor is in the room?
• What is the most useful lesson you have taken from a program retrospective?

As asked

Your program team is split across San Francisco, London, and Bangalore, with no more than four hours of overlap between all three. How do you structure the program to make sure nothing gets stuck waiting for a synchronous decision?

Sample answer outline

Strong answers emphasize asynchronous-first communication: well-structured async updates, documented decision frameworks so team members can make local decisions without waiting for a sync, clear ownership per timezone region, and short daily handoff notes. The candidate should describe how they handle time-sensitive blockers and what escalation path they set up for out-of-hours emergencies.

Expect these follow-ups

• A blocking dependency is owned by the San Francisco team and the Bangalore team hits it at 9am their time. How have you pre-empted this?
• How do you build cross-timezone team cohesion on a program?

As asked

Once a program is baselined and in execution, how do you handle a request to change scope, timeline, or resources? Walk me through the process from intake to approval.

Sample answer outline

Strong answers describe a lightweight change request form (what changes, why, impact on scope/timeline/resources, who is requesting, who approves), a defined approval authority matrix (team lead, TPM, director, VP depending on impact size), and a process for communicating approved changes to all affected parties. The candidate should stress that every approved change re-baselines the plan so slippage is measured against the new baseline, not the original.

Expect these follow-ups

• How lightweight can a change control process be before it stops working?
• What happens when changes are approved verbally but never documented?