The employer wants to see if you can think systematically about project risks before they occur, rather than reacting to problems after the fact. This is a core PM discipline for protecting delivery dates and budgets.
Outline a practical risk register structure, then explain a simple prioritization method like a likelihood impact matrix. Give one concrete example of a risk that would and would not need a formal contingency plan.
Start by naming the risk categories you actually use in your day to day work, such as scope, schedule, cost, quality, resources, and external dependencies, and note that in the Philippine BPO context you often add client communication and shifting regulatory requirements to that list. Then explain that you do not treat every risk equally, you score each one on likelihood and impact using a simple one to five scale, and you multiply those two numbers to get a priority score. Say plainly that you only build a formal contingency plan for risks that land in the high zone, usually a score of fifteen or above, because those are the ones that can genuinely derail your timeline or budget. For a medium or low scoring risk, you would still log it in the risk register and assign an owner to monitor it, but you would not spend the team's time drafting a detailed response plan. Give a concrete example, such as a key developer resigning mid project, which is high likelihood and high impact, so that deserves a formal plan like cross training or a backup hire, whereas a minor delay in a non critical vendor delivery might only need a watch list entry. Close by saying that your decision rule is always about protecting the critical path and the committed deliverables, not about chasing every possible what if.
Many candidates say 'I will list all possible risks' without prioritization, or say 'Bahala na, I will handle it if it happens.' Instead, show a scoring method and explain why you would only build formal contingencies for high-scoring risks.
Situation
During my first project as a junior PM at a BPO, I was asked to create a risk register for a client onboarding project.
Task
I had to identify the main risk categories and propose which risks warranted formal contingency plans.
Action
I grouped risks into resource, timeline, vendor, scope, and data privacy categories, then scored each on likelihood and impact using a simple 1 to 5 matrix. I proposed contingency plans only for risks scoring 12 or higher, such as cross-training a backup for the sole payroll specialist and booking a buffer week with the client.
Result
The risk register was approved, and when the payroll specialist actually took emergency leave, the backup handled payroll without missing the cutoff.
Prioritize risks by likelihood and impact, not by fear.
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.