FoundationBehavioural

Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?

What they are really testing: They want to know if you act when no one has handed you a ticket, and whether you raise problems responsibly instead of either staying silent or going rogue.

A real interview question

Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?

What most people say

drag me

I always take ownership. If I see a problem I fix it, because I am a very proactive person and I do not wait to be told.

It is a personality claim with no story, no system, no number, and no evidence that anyone else noticed the change happened.

The follow-ups they ask next

  • What if your lead had ignored the message?

    Say you would raise it once more with the cumulative cost, then accept the decision and log it. Escalate facts, not feelings.

  • How did you know deleting them was safe?

    Talk about the evidence you gathered first, the stop-before-delete step, and the wait period. Reversibility is the point.

What the interviewer is listening for

  • Named a real number before touching anything
  • Chose a reversible step, stop before delete
  • Told a human before acting, not after
  • Turned a one-off fix into a repeatable habit

What sinks the answer

  • Claims to be proactive but tells no story
  • Deleted or changed shared resources without telling anyone
  • Blames the intern or the ex-teammate
  • Cannot say what the impact actually was

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

I have not owned a big orphaned system yet, but here is the smallest version I have seen and how I would reason about it: I would first make the problem visible with a number, then propose a reversible step to whoever is closest to it.

Keep going with behavioural

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free