This reveals whether you actually plan for risks in a practical way, not just identify them. Employers want PMs who can activate a fallback without chaos and still meet the client's critical date.
Use the STAR method: set up a real risk, show what you had prepared in advance, then walk through the trigger and the orderly activation. Emphasize the pre-work, not just the drama of the moment.
Start by naming the specific risk you had flagged during planning, then move quickly to the concrete contingency you had already put in place. Say plainly what the trigger was, whether it was a sudden resignation, a vendor failure, or a spike in volume that threatened your timeline. The key is to show that the activation was not a scramble but a switch you had rehearsed. Explain that you had documented the fallback steps in your risk register, briefed the team on them ahead of time, and identified who would take over which task the moment the trigger hit. When the trigger did occur, you called a short huddle, confirmed the situation against your pre-agreed criteria, and then executed the plan without re-litigating it. Emphasize that your role during activation was coordination, not heroics, and that you tracked the fallback against the original milestones. In a Philippine BPO or shared services setting, this might mean activating a cross-trained teammate on the night shift or pulling a documented process from a shared drive, not asking everyone to stay late. Close by stating the outcome in terms of the client's critical date and what you updated in your risk log afterward.
Some Filipino candidates say 'I just asked everyone to work overtime para hindi ma-delay' or describe heroic individual effort instead of a prepared backup plan. Instead, describe a specific pre-arranged fallback like a cross-trained teammate and a documented process.
Situation
In my previous role as a project coordinator at a digital marketing agency, we were handling a website migration for a retail client with a fixed launch date. I had prepared a contingency plan in case our lead developer was pulled into a high-priority emergency.
Task
My task was to activate that contingency smoothly without delaying the migration and without alarming the client.
Action
When the lead developer was indeed assigned to a critical outage, I immediately informed the project manager, then brought in a cross-trained junior developer from another team as planned. I had already documented the migration steps and scheduled a handover session the week before. I also adjusted the timeline by using the two-day buffer we had built into the schedule.
Result
The migration was completed one day later than originally planned but still two days before the client's hard deadline. The client never knew about the resource change, and the lead developer returned to review the work.
A contingency plan is only useful if you have already prepared the backup person and documented the steps.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.