How to answer the project risk interview question
The short answer
Interview Coach asks this question in these words:
Tell me about a risk you saw early. What did you do before it became an issue?
Pick one risk you noticed before it hurt the project. Say what the risk was and the signal that showed it to you. Then say what you proposed, to whom, and what they decided. End with what the action avoided and what it cost. Spoken, the answer takes about one to two minutes.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
The question separates people who keep a risk log from people who act on one. The bank lists three things a strong answer does:
- It names the risk and the signal that showed it. Not "there were risks around testing", but what you saw, where and when: a calendar, a defect trend, a vendor email, a dependency date.
- It says what you proposed, to whom, and what was decided. A risk you raised and nobody decided on is still an open risk. Name the person with the right to choose and the choice they made.
- It ends with what the action avoided or cost. Mitigation has a price. Say what it was and what the project would have faced without it.
A risk that turned into an issue anyway can still be a good answer, if you saw it early, acted, and can say what the action saved. A risk you only logged is not.
A structure that works
Interview Coach describes a story answer in five parts:
- Situation. Two or three sentences on the context and what was at stake.
- Action. What you did yourself, said with I, in the order you did it.
- Result. What changed, and how you know.
- Evidence. A figure before and after, or a record a reader could ask for.
- Length. About one to two minutes when spoken.
The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record such as the steering minutes, a risk register or a report. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership ("tried to", "was responsible for") and vague claims.
Answers as written, and what the check says
Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.
| Answer as written | What the check says | What to change |
|---|---|---|
| When the vendor's test environment turned out to be booked for another client in March, the sponsor approved a second environment, per the steering minutes. | No sentence says what you did yourself, with I. | Say who spotted the double booking and who priced the second environment. |
| When I saw the vendor's test environment was double booked for March, the sponsor approved a second environment, per the steering minutes. | Only one first person action found. Say what you did yourself. | Add what you did between seeing it and the sponsor's decision: the options and the price. |
| When the test environment was double booked, we raised it, we priced a second one, we booked it, we moved the scripts and we tested on the planned date. I spotted it and I told the sponsor, per the steering minutes. | Mostly we and the team. The interviewer cannot tell which part was yours. | Keep the team's work to one sentence and give your own steps their own sentences. |
| I spotted the double booking, I priced a second environment, and the sponsor approved it, per the steering minutes. | No context is set before the action. Add what was at stake. | Open with the project, the test window and what a slip would have cost. |
| When the vendor's test environment was double booked for March, I priced a second environment, and I put the choice to the sponsor in the steering minutes. | No result is named. Say what changed. | Say what the sponsor decided and whether testing started on the planned date. |
| When the vendor's test environment was double booked for March, I priced a second environment and I put it to the sponsor, who approved it. | No figure and no named record. Name where the result shows, if you have it. | Name where the decision is recorded, such as the steering minutes or the risk register. |
| When the vendor's test environment was double booked, I priced a second environment and I put it to the sponsor, who approved it, and it all went great, per the steering minutes. | Vague amounts or claims found. Replace them with the figure or the record, if you have it. | Replace "it all went great" with what happened: testing started on the planned date. |
| When the vendor's test environment was double booked, I priced a second environment and I put it to the sponsor, who probably approved it, per the steering minutes. | Hedging or weak ownership words found. | If you do not know the decision, find out before the interview. "Probably" tells the interviewer you did not follow it through. |
The check never adds a figure or a record for you. If the cost of the slip you avoided was never worked out, say what was at risk in plain words rather than inventing a number.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the story check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.
I was the project manager for the move of a university's student records to a new system, with testing planned for March. In January, while I was checking the vendor's environment schedule against our plan, I saw that our test environment was also booked for another client in March. If testing slipped, the go-live would miss the summer window between terms, and the next window was in December. I raised it as a risk at the steering meeting that week. I priced a second test environment with the vendor at $18K, and I set out two options: pay for it, or test in April and put the summer window at risk. The sponsor approved the second environment, and the decision is in the steering minutes. Testing started on the planned date in March, and the system went live in the summer window. The second environment cost $18K. A slip to December would have meant six more months of license fees for the old system.
Why it works. The signal is concrete and the answer says how it was found. The stakes are named in terms the business cares about: a window between terms. There are two options with a price, the sponsor decides on record, and the answer gives both the cost of acting and the cost it avoided.
What the check cannot see
The answer check reads the words of your answer. This answer, sent on its own, gets every mark except length, although it never says what happened:
When the vendor's test environment was double booked for March, I raised the risk at the steering meeting and I priced a second environment.
The check takes "raised" as a sign that something changed, and "steering" as a record, so the result and evidence marks are present. An interviewer would hear no decision and no outcome: was the second environment approved, and did testing start on time? Use the marks to find what is missing, then read your answer the way an interviewer would.
Choosing your story
- Pick a risk you saw before it became an issue. The question says "early". A fire you put out is a different story.
- Pick one with a clear signal. You should be able to say what you saw and where.
- Pick one where someone decided. A sponsor, a steering group, a client. Raising a risk is half of the answer; the decision is the other half.
- Pick one with a cost on both sides. What acting cost, and what not acting would have cost.
Your resume is where an interviewer looks for these stories. A line such as "Maintained the RAID log" names the duty and gives this question nothing to start from; Reed flags it. Get a free AI review of your resume and see which lines Reed flags first.
Prepare the follow-up questions
- How did you decide this risk was worth the sponsor's time?
- What other risks were on the register at the time, and why did this one come first?
- What would you have done if the sponsor had said no to the cost?
Run the free review on your own resume lines.
Check your answer with Interview Coach in Claude
This question is in the project manager track of the Interview Coach question bank, which also serves delivery manager titles. Write your answer the way you would say it and ask for a check.
- It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
- It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
- It does not judge whether the story is true or good, and it never adds a figure you did not give.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
Can I use a risk that turned into an issue anyway?
Yes, if you saw it early, proposed an action and someone decided. Say what the action changed even if it did not prevent the issue: a shorter delay, a smaller cost, a fallback ready in time. Be plain about the part that did not work.
Do I need a risk register to answer this well?
No. A register helps you remember dates and owners, but the interviewer is listening for the signal, the decision and the cost. Name the record you do have, such as steering minutes or an email to the sponsor, and do not claim one you did not keep.
Does Interview Coach know whether my story is true?
No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good. You decide what to say.
Keep going
- Interview questions: Project manager interview questions
- Interview questions: Delivery manager interview questions
- Guide: How to answer the stakeholder conflict question
- Guide: How to answer the failed project question
- Guide: How to answer the influence without authority question
- Guide: How to answer the hardest deadline question
- Guide: How to answer the scope change question
- Guide: How to answer the product metric question
Last updated: October 13, 2026