Tell me about a time you had to explain a technical risk to management and get a decision.
Show the answer
Say this first
Use your own real story. A model answer, STAR shaped: our headquarters had one internet circuit and one firewall carrying SaaS, VPN and the contact center, and earlier requests for a second circuit had been declined as nice to have. I translated it into business terms, cost per hour of contact center downtime from finance and last year's outage hours, and gave three options with cost and remaining risk on one page. They funded a second circuit and an HA firewall pair; months later a fiber cut took the primary circuit down for hours and users did not notice.
Go deeper
What the interviewer is testing
Whether you can speak the language of the business, give options instead of complaints, and get a clear decision, including a documented acceptance of risk if the answer is no.
The model, step by step
- Situation: single circuit and single firewall at headquarters; two outages the previous year.
- Task: get either funding or an explicit, recorded acceptance of the risk.
- Action: I asked finance what an hour of contact center downtime costs, added the outage history and the carrier's repair times, and wrote one page with three options: do nothing, add LTE backup, or add a second carrier and an HA firewall pair. Each had cost, expected downtime and what it still did not cover. I made a recommendation and kept the jargon out.
- Result: they chose the third option. A later fiber cut on the primary circuit had no user impact.
- Lesson: numbers and options get decisions; warnings get postponed.
If the answer had been no
Say so in your story if it happened. Record the risk acceptance with the owner's name, and set a date to revisit it.
Traps
- Saying management "did not understand". Your job was to make it understandable.
- Presenting only the expensive option.