What would you do if you made a mistake that nobody else noticed?
Report it to the right person promptly, explain the impact and propose a fix. Hidden mistakes usually grow, and owning them early builds trust.
Explain it simply
It is tempting to stay quiet when no one has seen the error. But in software or finance, a hidden mistake can turn into a production bug or a wrong payment later, when it is much harder to fix and much worse for you.
The interviewer is testing honesty. Explain that you would inform your lead quickly, fix it if you can, and learn from it. Show that you understand trust is built this way.
Example
Situation: During her internship, Jyoti realised she had run a data cleanup script on the full customer table instead of a test copy, changing phone number formats for real records.
Task: Fix it before it caused problems, even though nobody had noticed.
Action: She told her mentor within ten minutes, explained exactly what the script did, and suggested restoring from the previous night's backup for that one column. They restored it together, and she added a confirmation prompt to the script that shows the target table before running.
Result: No customer was affected, and her mentor told the team about the confirmation prompt as a good practice.
What to say in the interview
"I'd tell my lead right away, explain what happened and the impact, and suggest how to fix it. Then I'd change my process so it doesn't repeat."
Common mistakes
- Saying you would quietly fix it and tell no one.
- Saying you would wait to see if anyone notices.
- Blaming the tool or process only.