This tests your ability to think through multiple competing risks at once and allocate limited planning effort where it matters most. Employers want PMs who are proactive but also pragmatic about budget.
Structure your answer by first stating a quick prioritization method, then assigning each risk a likelihood and impact score, and finally describing one concrete contingency per risk. Show that you think in trade offs, not just lists.
Start by naming a simple scoring method, like a 1 to 5 scale for likelihood and impact, and multiply the two to get a risk priority number. Say plainly that you would rank the three risks by that score, not by gut feel, and explain that the client adding scope late often scores highest because it hits both budget and deadline, while the vendor delay may be high impact but lower likelihood if you have a strong contract. For the team member being pulled away, treat it as a resource risk and prepare a low-cost contingency: identify a backup person early, cross-train them on the critical tasks, and keep a short handover checklist ready. For the vendor, build a buffer into the schedule, say a week of slack, and agree in writing on a penalty or expedited delivery clause before signing. For scope creep, set a change control process from day one, where any new request goes through a formal review and the client sees the cost and time impact before approval. Close by saying you would revisit these scores monthly, because in a Philippine BPO environment, shifting priorities and client requests are normal, so your plan must move with them.
A common Taglish answer is 'I will just monitor the risks po and update the team' without any actual fallback. Instead, give a clear scoring method and specific, low-cost contingencies for each risk.
Situation
In a recent mobile app delivery project at a software house, I was planning phase one with a hard store submission deadline and a fixed budget from the client.
Task
I had to choose which of three identified risks to address first and prepare practical contingencies without overspending.
Action
I scored each risk on likelihood and impact. The key team member being pulled was high likelihood and high impact, so I prepared a backup by cross-training a developer and arranging a shared resource agreement with another team. The vendor delay was medium likelihood but high impact, so I negotiated a penalty clause and identified an alternative vendor for the critical API module. The client scope creep was low likelihood but high impact, so I included a formal change request process with a cost and timeline impact statement in the project charter.
Result
The client did add a small feature late, but because the change request process was already in place, we agreed to swap it with a lower priority item and stayed within budget and deadline. The vendor did miss their date by one week, but the alternative vendor took over and we lost no time.
Prioritize contingencies by likelihood and impact, and use low cost pre-arrangements like cross-training and change processes.
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.