How to answer the program dependency interview question
The short answer
Interview Coach asks this question in these words:
Tell me about a dependency between two projects in your program that threatened a milestone.
Pick one dependency you found before it broke a milestone, or one that broke it and taught you something. Name the two projects and what one needed from the other. Say how you found the problem, who you brought together, and what you decided. End with what happened to the milestone and what it cost, from a record such as the RAID log or the steering minutes.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
This is the program manager question in its purest form: a project manager owns one plan, a program manager owns the places where plans touch. The bank lists three things a strong answer does:
- Names the two projects and what one needed from the other. A test environment, a data load, an interface, a person. "There were dependencies" says nothing; "billing needed the migrated customer data by March" says everything.
- Shows how you found the problem and who you brought together. A dependency map, a RAID review, a hallway remark. Then the people you put in one room, and why those people.
- Says what happened to the milestone, and what it cost. Held, slipped, or moved by agreement. Cost can be money, weeks, scope or goodwill.
A good answer shows a habit, not luck. If you found the dependency because you review the map every phase, say so: it tells the interviewer you would find the next one too.
A structure that works
Interview Coach describes a story answer in five parts:
- Situation. Two or three sentences on the context and what was at stake. Here: the program, the two projects and the milestone at risk.
- Action. What you did yourself, said with I, in the order you did it. Here: how you found it and the steps you took, in order.
- Result. What changed, and how you know. Here: what happened to the milestone.
- Evidence. A figure before and after, or a record a reader could ask for. Here: the RAID log, the steering minutes or the plan of record.
- Length. About one to two minutes when spoken. Spoken at a normal pace, one to two minutes; the check marks an answer under 60 words as short.
The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership and vague claims.
Answers as written, and what the check says
Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| When the billing milestone was at risk from a shared test environment, the dependency was mapped with both project managers and the migration test was moved ahead of the billing build, and billing went live on its milestone date, per the steering minutes. | No sentence says what you did yourself, with I. | Say which of these steps were yours, with I. |
| When the billing milestone was at risk from a shared test environment, I mapped the dependency with both project managers, and billing went live on its milestone date, per the steering minutes. | Only one first person action found. Say what you did yourself. | Add the second step that was yours, in the order you took it. |
| When billing was at risk, we mapped the dependency, we met both teams, we replanned the test, we moved the cutover and we rechecked the milestone. I mapped it and I moved the test, and billing went live, per the steering minutes. | Mostly we and the team. The interviewer cannot tell which part was yours. | Give the team's work one sentence, then say which calls were yours. |
| I mapped the dependency with both project managers and I moved the migration test ahead of the billing build, and billing went live on its milestone date, per the steering minutes. | No context is set before the action. Add what was at stake. | Open with what was at stake before you acted. |
| When the billing milestone was at risk from a shared test environment, I mapped the dependency with both project managers and I moved the migration test ahead of the billing build, per the steering minutes. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
| When the billing milestone was at risk from a shared test environment, I mapped the dependency with both project managers and I moved the migration test ahead of the billing build, and billing went live on its milestone date. | No figure and no named record. Name where the result shows, if you have it. | Name where the outcome is recorded, or give the figure before and after. |
| When the billing milestone was at risk from a shared test environment, I mapped the dependency with both project managers and I moved the migration test ahead of the billing build, and billing went live 2 weeks later than planned. | A figure is given, with no starting point. | Give the starting figure too, or name the record that holds both. |
| When the billing milestone was at risk from a shared test environment, I basically mapped the dependency with both project managers and I moved the migration test ahead of the billing build, and billing went live on its milestone date, per the steering minutes. | Filler words found. | Drop the filler word and say the step plainly. |
The check never adds a figure or a record for you. If the milestone slipped, say by how much and who agreed to the new date.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the story check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.
I ran a payments modernization program at a regional bank with four projects. When the new billing engine and the customer data migration both needed the same test environment in March, the billing milestone was at risk: the migration test plan ran three weeks into the billing build window. I mapped the dependency with both project managers in one session and wrote it into the RAID log with a date. I set out two options for the steering group: move the migration test earlier by running it on weekends, or move billing by three weeks. I recommended the weekend runs, because the migration team had the capacity and billing had a regulatory date. The steering group agreed, and I booked the environment on a shared calendar both teams could see. The migration test finished on the new dates, and the billing engine went live on its milestone, per the steering minutes of April. The weekend runs cost 160 hours of overtime, which the program budget absorbed.
Why it works. The two projects and the shared need are named. The dependency goes into a record with a date. There are two options, a recommendation with a reason, a decision by the right forum, and the cost of the choice is stated, not hidden.
What the check cannot see
The answer check reads the words of your answer, not the dependency behind them. This answer, sent on its own, gets every mark except length:
When the billing milestone was at risk, I mapped the dependency and I moved the test, and billing went live on time, per the RAID log.
It has a situation, two actions, a result and a record. An interviewer would still ask: which two projects, what did one need from the other, how did you find it, and what did moving the test cost? The words pass; the program manager behind them is still invisible.
Choosing your story
- Pick a dependency between two projects you both oversaw. A dependency inside one project is a project manager story; the question asks about the program view.
- Pick one you found early. Finding it is half the answer. If it surprised you, say what you check now so the next one does not.
- Pick one with a cost. Overtime, a later date, a dropped feature. A dependency resolved for free is rarely the one an interviewer remembers.
- Name the forum that decided. A steering group, a program board, a sponsor. The program manager prepares the decision; the right people take it.
Your resume is where an interviewer looks for these stories, and a line such as "managed cross-project dependencies" invites this question. Get a free AI review of your resume and see which lines Reed flags first.
Prepare the follow-up questions
- How do you keep a dependency map current across several projects?
- What would you have done if the steering group had chosen to move the milestone?
- Which dependency did you miss, and what happened?
Run the free review on your own resume lines.
Check your answer with Interview Coach in Claude
This question is in the program manager track of the Interview Coach question bank. Write your answer the way you would say it and ask for a check.
- It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
- It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
- It does not judge whether the story is true or good, and it never adds a figure you did not give.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
What if the milestone slipped anyway?
Tell it. Say how far it slipped, who agreed to the new date, and what you changed so it would not happen again. A program manager who never saw a milestone move has not run a program for long.
Can I use a dependency on a vendor or another department?
Yes, if it sat between two pieces of work you were accountable for. Name both sides and say what each needed. The question is about how you managed the link, not about who was on the other end.
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good. You decide what to say.
Keep going
- Interview questions: Program manager interview questions
- Guide: How to answer the stakeholder conflict question
- Guide: How to answer the failed project question
- Guide: How to answer the influence without authority question
- Guide: How to answer the hardest deadline question
- Guide: How to answer the program governance question
- Guide: How to answer the benefits realization question
- Guide: How to answer the scope change question
- Guide: How to answer the project risk question
Last updated: October 14, 2026