Tell me about a time you identified a significant technical risk in a project before it became a problem. What did you do?

behavioral · Mid level · general

What the interviewer is really asking

Evaluate proactive risk awareness and the ability to translate a technical concern into action.

What to say

• Explain what clued you in to the risk — a code pattern, an architectural assumption, a dependency version.
• Describe how you validated it was a real risk before raising the alarm.
• Walk through how you communicated it and what concrete step prevented the problem.

What to avoid

• Don't describe a risk you spotted but didn't act on.
• Avoid being so technical in the explanation that the business impact is lost.
• Don't frame it as 'I told them so' if the team initially pushed back.

Example answers

Strong: Six weeks before launch I noticed our session tokens never expired. I wrote a small proof-of-concept showing token replay and presented it in the next architecture review. We added 30-minute TTLs and a refresh mechanism in one sprint — a change that would have been much harder post-launch with real users.

Weak: I mentioned it in a Slack message but no one responded so I let it go.