Technical Program Management interview questions and answers

Cross-functional delivery, risk mitigation, and dependency management.

6 published across 2 topics.

Technical Program ManagementA 18-minute read on how the topic fits together, before the questions.Technical program management fundamentals60 short answers on one page, for revising rather than studying.

Program Delivery

3 questions

Handling slippage, unblocking critical paths, and stakeholder comms.

hardScenarioBehavioural

A platform team your program depends on has just told you their deliverable will land three weeks late, and it is on your critical path. How do you handle telling the VP the launch date has moved?

Establish the real new date before you talk to anyone, by re-running the critical path with the slip in it rather than adding three weeks to the end. Then present one recommended date with the two rejected options and what each would have cost. It also connects stakeholder communication to the point an interviewer is testing.

5 minsenior, staff, lead

hardScenarioDesign

Every workstream in your program is reporting green, but you are fairly sure the program is going to miss its date. What is going on, and what do you do?

Workstream status is reported against local scope while the date depends on the integration between them, so a program can be green everywhere and still miss. Track the joins - handoffs, shared environments, the first end-to-end run - and change what green is defined against.

5 minsenior, staff, lead

hardScenarioBehavioural

Two engineering teams in your program each insist their work has to come first, and both leads have dug in. You have no authority over either. How do you get to a decision?

Convert a priority argument into a sequencing question with a stated cost, because two teams can both be right about importance while only one ordering is cheaper. Find the shared constraint, price each ordering against it, then take the residual disagreement to the one person who owns both.

5 minmid, senior, staff, lead

All 3 in Program Delivery

Technical Risk Management

3 questions

Identifying architectural bottlenecks and resource constraints.

hardScenarioBehavioural

In standups you keep hearing engineers refer to a scaling limit as a known thing, but it has never appeared on any risk register or in any status report. What do you do with that?

Widely known and never escalated usually means the risk has no owner and no threshold, not that it is being hidden. Get it written down with a trigger and an owner, and find out why the existing escalation path did not carry it.

5 minsenior, staff, lead

hardScenarioBehavioural

One engineer is the only person who understands the payments integration, and four of your workstreams queue behind them. How do you manage that as a program risk?

Treat it as a throughput constraint first and a knowledge risk second: measure the queue, take work off the expert that only needed their review, and buy down the single point of failure with paired delivery on real tasks rather than with documentation.

5 minmid, senior, staff, lead

hardScenarioCase Study

You need a steering committee to fund a quarter of platform hardening instead of two customer features. How do you put technical risk and feature risk side by side so an executive can choose?

Express both in the same currency, which is expected cost to the business over a stated horizon, and show the arithmetic from assumptions the room can argue with. Give the committee a real choice with a decision date rather than a single option and a plea.

5 minsenior, staff, lead

All 3 in Technical Risk Management