All jobs / Project / delivery manager

Risk Management interview questions

Risk Management questions a Project / delivery manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.

1. What goes in a RAID log, and how is an issue different from a risk?

   The strongest answer: Risks, assumptions, issues and dependencies, each with an owner and a review date; a risk might happen, an issue already has — so it needs action now, not a probability

   Why it works: Exactly — the four lists plus owners and dates; the risk-to-issue distinction is what tells you whether to plan or to act.

   • Risks, assumptions, issues, dependencies.
   • Owner and review date on each.
   • Issue: a risk that happened.
   • Review it; do not archive it.

2. Someone says “it should be fine” about a vendor we have never integrated. Strongest move?

   The strongest answer: I name it as a risk with a next check — a spike, a date they answer, a fallback — I do not file “should be fine” as a plan

   Why it works: Exactly. A named risk plus a next check. “Should be fine” is hope.

   • Name the risk.
   • Give it a next check.
   • Do not file and forget.
   • Do not freeze the slice forever.

3. What is the difference between mitigating a risk and having a contingency for it?

   The strongest answer: Mitigation acts before the event to cut its probability or impact; a contingency is the pre-agreed plan and reserve you trigger if it happens anyway — a serious risk usually needs both

   Why it works: Right — one reduces the chance or the damage, the other prepares the response; naming both per risk is what a register is for.

   • Reduce before, respond after.
   • Mitigation: lower probability or impact.
   • Contingency: pre-agreed plan and reserve.
   • Serious risks get both.

4. The risk register is a spreadsheet from last quarter. A new vendor risk is only in Slack. What do you do?

   The strongest answer: I bring the living risks into the room we already have — stand-up, planning, or steer — with an owner and a next check, I do not add a second document nobody opens

   Why it works: Exactly. Risks live where decisions live. A stale file is not management.

   • Put living risks in an existing room.
   • Owner and next check.
   • Do not worship the stale file.
   • Do not spawn a committee by default.

5. Legal risk and launch pressure disagree. What conversation do you run with the sponsor?

   The strongest answer: I name both risks, I ask which they are willing to hold, and I write the choice — I do not silently pick launch and hope legal sleeps

   Why it works: Exactly. Appetite is a choice in the open. Silent launch is how you get both a miss and a finding.

   • Name both risks.
   • Ask what they will hold.
   • Write the choice.
   • Do not silently ship past legal.

6. Your register lists thirty risks and the steering committee has twenty minutes for them.

   How do you decide which risks get attention?

   The strongest answer: I rate each on probability and impact with simple scales, add proximity — how soon it could bite — and bring the few high-and-near ones with owners and mitigation status; the rest stay on the register

   Why it works: Exactly — qualitative probability, impact and proximity put the committee’s attention where it moves something; the register keeps the rest honest.

   • Probability, impact, proximity.
   • Simple scales, not fake decimals.
   • Bring the high and near ones.
   • Keep the rest under review.

7. A launch is late and the bet may also be wrong for users. How do you talk about risk?

   The strongest answer: I separate “we may not finish in this range” from “this may not be worth finishing” — I do not fold them into one amber so nobody knows which talk we are in

   Why it works: Exactly. Two talks. One amber hides the decision you need.

   • Split finish-risk from worth-risk.
   • Do not fold them into one color.
   • Both talks are shared.
   • Do not leave one as a private worry.

8. In the budget review, finance proposes removing the contingency reserve “to keep the plan lean.”

   What do you say?

   The strongest answer: The reserve is sized to the identified risks, so cutting it removes the buffer, not the risk; I offer to govern it — drawn by explicit decision, reviewed at milestones, released as risks retire — not delete it

   Why it works: Right — a governed reserve is the honest form of contingency; a deleted one comes back as a surprise change request.

   • Reserve matches risks.
   • Governed, not deleted.
   • Draw by explicit decision.
   • Release it as risks retire.

9. The board has treated a conference date as immovable and cut learning, testing, and discovery to protect it. What risk do you name first?

   The strongest answer: The date itself — an immovable Tuesday that ate the system is now the biggest risk, and I put a range and a protect-or-move choice back in the room

   Why it works: Exactly. The date can be the risk. Put the choice back: protect it or move it, in the open.

   • Name the date as a risk.
   • Put protect-or-move in the room.
   • Do not cut learning to save a Tuesday.
   • Do not fear looking indecisive more than a miss.

10. The org celebrates the people who “saved the launch” every quarter. What risk do you put on the page?

    The strongest answer: Hero culture — it hides WIP, burns the saviours, and teaches everyone else to wait — I change the story to the system that made a save unnecessary

    Why it works: Exactly. The save is a smell. Celebrate the system that did not need a save.

    • Name hero culture as a delivery risk.
    • Tell the system story, not the save.
    • Do not hire more heroes.
    • Do not shame people who did not stay late.