You discover that a feature your team is building collects more user data than customers were told about. What would you do?
How to handle this hypothetical in an interview: a worked example answer, the missteps that signal poor judgment, and the follow-up questions that test your reasoning.
A strong example answer
Sounding the alarm before checking the facts would be the worst version of this. I'd pull the actual data schema and event logs, compare them field by field against what the privacy notice promises, and write down each specific gap — say, location data kept well beyond the disclosed retention window. Only with that evidence in hand would I raise it, the same day, with my manager and the product owner, framed as a fixable compliance risk rather than an accusation. Legal or the privacy officer gets looped in before anything ships.
If leadership wanted to launch anyway and patch consent later, I'd come back with a middle path: put the extra collection behind a flag, ship on time with only the disclosed fields, and switch the rest on once the notice and consent flow catch up. The last time I made that case we held the launch date, and the privacy review wrapped up quickly because the questionable collection was already off by default.
Staying quiet isn't an option, and neither is going anonymous first. Raising it directly — with evidence and a workable alternative — protects users and the company, and it buys the credibility to flag the next problem early instead of after a headline does.
A framework for your own answer
- Situation: Frame the stakes: user trust, legal exposure, and a launch deadline.
- Task: Define your responsibility as the person who spotted the gap.
- Action: Walk through verifying the gap, raising it, and proposing a fix.
- Result: Show how you balanced shipping, compliance, and trust.
Common mistakes to avoid
- Candidates often jump straight to regulators or the press before anyone has verified the gap internally.
- 'Legal owns that' is a dodge — the answer has to own raising the flag.
- Ship-or-ethics is a false choice; offer the middle path, like a flag that disables the extra collection.
- Treat suspicion as established fact and you lose credibility the moment one detail is wrong.
Follow-up questions to prepare for
Expect the interviewer to dig past your first answer. Common follow-ups for this question include:
- What if your manager tells you to drop it and ship as planned?
- How would you quantify the risk to leadership who only care about the launch date?
- Have you ever actually raised an ethical concern at work? What happened?
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 roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator