situational Hard GeneralSoftware Engineer

You see a colleague copy production customer data onto a personal laptop, which violates company policy. What would you do?

This is a hypothetical scenario question — the interviewer wants your decision framework, not a war story. Here is a model answer, the mistakes to avoid, and the follow-ups to expect.

A strong example answer

This is a security incident before it is a personal dilemma. Copying production customer data onto an unmanaged personal device is exactly how breaches start — at a previous company I saw the aftermath of one, where a single lost laptop triggered regulatory notification for 40,000 customers and weeks of remediation work.

So I would go to the colleague directly, the same day, without accusation: "I noticed customer data went onto your personal machine. That violates policy and carries real risk — you need to delete it and report it." People convince themselves of legitimate reasons — debugging from home, a looming deadline — but none of them make it acceptable, and offering the chance to self-report is fairer to them and better for the company. If they refused, downplayed it, or I doubted they would follow through, I would report it myself to security or through the ethics hotline that same day. No waiting, no weighing the friendship, no quietly fixing it myself — concealing an incident makes me complicit, and under most security policies, knowing silence is its own violation.

Afterward I would flag the process gap too: if engineers feel they need personal machines to debug production issues, the fix is better tooling and clearer procedures, not leniency. Protecting customer data outranks collegial comfort every time.

A framework for your own answer

  • Situation: Describe what you witnessed and why the policy against it exists.
  • Task: Clarify the stakes: customer data exposure, regulatory consequences, and trust.
  • Action: Show how you confronted the colleague directly, pushed for self-reporting, and escalated if needed.
  • Result: Share the outcome and the process fix you advocated afterward.

Common mistakes to avoid

  • Looking away to preserve a friendship makes you complicit under most security policies.
  • Give the colleague a chance to self-report before you go to security or the hotline yourself.
  • Good intent does not excuse the violation, and it does nothing to shrink the data risk.
  • The incident has to be logged — quietly deleting the data yourself conceals it.

Follow-up questions to prepare for

Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:

  • What if the colleague is a senior engineer or a close friend?
  • Would you still report it if you were confident no data actually leaked?
  • What if you later learned the colleague was fired over your report — how would you feel about it?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator