A vendor misses a critical delivery commitment and then goes quiet. How would you handle it?
Scenario questions test judgment under uncertainty. Below is a sample answer for this one, the traps candidates fall into, and the probes interviewers follow up with.
A strong example answer
The account manager's manager got a call request within 24 hours — not the usual weekly check-in — because a vendor that misses a critical delivery and then goes quiet is almost always hiding a bigger problem than it's admitted.
Before that call I put the miss in writing against the contract: what was due, when, and what our exposure is. Then I assume the worst-case delay and plan around it immediately, rather than rebuilding the schedule around whatever revised date eventually arrives. In parallel the fallback activates. On a past project, a vendor blew a data-migration deadline by weeks, and because we'd identified the contingency in advance, our own engineers shipped a narrower version in days. I'd also re-read the contract for remedies — service credits, penalty clauses, termination rights. Not necessarily to use them; a vendor that knows you know your options responds differently.
Internally, the team hears the truth about the delay and the contingency, so nobody builds on a fantasy timeline. Once the fire is out, the retrospective targets vendor management itself — milestone-based payments and a short-notice termination clause went into our next renewal. Trust gets rebuilt through verified milestones, not assurances, and silence after a miss is itself a data point I price into how much rope the next milestone gets. Every critical dependency deserves a plan B before it's needed.
A framework for your own answer
- Situation: Set up the dependency: their miss blocks your timeline.
- Task: Own both the escalation and the contingency plan.
- Action: Escalate inside the vendor, activate the fallback, check contract remedies.
- Result: Close with the structural fix that prevents recurrence.
Common mistakes to avoid
- Wait for the vendor to resurface and you lose the days you most need.
- Their revised date is usually optimism; rebuild your plan around the worst case instead.
- Candidates sometimes threaten legal action before understanding what went wrong — escalation inside the vendor comes first.
- Fix the delay but skip milestones and contingencies, and the same fire returns next quarter.
Follow-up questions to prepare for
A strong answer invites follow-ups — interviewers probe to check the reasoning holds up. Prepare for questions like:
- When would you actually terminate the contract rather than escalate?
- How do you keep the internal team productive while the dependency is blocked?
- How do you rebuild trust with this vendor afterward — or would you?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator