# Doing Well in a Debugging Interview
Some companies hand you broken code and watch you fix it. They want a method, not luck.
1. **Reproduce first.** Run the failing test or input and read the actual error.
2. **Form one hypothesis at a time** and say it aloud.
3. **Narrow the search** with prints, a debugger, or bisecting the input.
4. **Fix the cause, not the symptom,** then add a test that would have caught it.
Explain what you rule out as you go; a methodical miss can score better than a lucky guess.
---
*Disclosure: I work on Linkjob AI. If you'd like real-time help in live interviews, see [AI coding interview assistant](https://www.linkjob.ai/coding-interview-copilot/).*