How do you write effective bug reports?
- bug reports
- defect management
- communication
Answer it first, then compare. Nothing here is saved or scored.
Model answer
A good bug report contains: (1) Clear title: "[Component] Specific behavior description." (2) Steps to reproduce: numbered, starting from a clean state. (3) Expected result: what should happen. (4) Actual result: what actually happened. (5) Environment: browser, OS, device, user account. (6) Evidence: screenshots, video, console errors, network logs. (7) Severity and priority assessment. (8) Workaround if known. Bad example: "Login is broken." Good example: "Login page shows spinner indefinitely when submitting valid credentials on Firefox 120 / macOS, works on Chrome."
What interviewers listen for
- Risk-based prioritisationYou can defend skipping coverage on a path because the risk maths supports it.
- Test design fluencyYou apply equivalence partitioning and decision tables to concrete inputs in real time.
- Metric judgmentYou distinguish between metrics that drive learning and metrics that drive theatre.
- Strategy under constraintYou can produce a defensible plan when the team has half the time and twice the scope.
Related questions
- Tell me about a time you found a critical bug close to a release deadline. How did you handle it?
- Describe how you've handled a situation where requirements were unclear or incomplete.
- How do you communicate testing status and risk to non-technical stakeholders?
- Tell me about a time you worked with a remote or distributed team. What challenges did you face?