Skip to main content
Automation Juice 🥤
Log inBrowse courses

Defects and bug reporting interview questions, 2026

Looking for clear, calm bug-reporting craft.

Defect questions test the craft of finding, reproducing, classifying, and communicating a bug. The most common ones: severity vs priority, how to handle "cannot reproduce", what fields a good bug report has. Calm, collaborative answers win over combative ones every time.

2 questionsIndia context · 2026
  1. Q1What's the difference between severity and priority?
    What the interviewer is really listening for

    Looking for: severity = impact on the system; priority = urgency of fix; they are independent.

    Sketch answer (adapt, do not memorise)

    Severity is the impact on the system, a crash is high, a typo is low. Priority is how urgently we fix it, driven by business context. A logo typo is *low severity* but *P0 priority* the day before a press event. Decoupling them is the whole point of having two fields.

  2. Q2A bug you filed was marked "Cannot Reproduce." What do you do?
    What the interviewer is really listening for

    Looking for: collaboration, not combat. Add detail, share environment, sit with the dev.

    Sketch answer (adapt, do not memorise)

    I'd revisit my repro: am I on the same build, same data, same environment? Attach video + HAR if I haven't already. Sit with the developer for 10 minutes, half the time the bug surfaces immediately. If it's truly intermittent, I'd label it as such and try to bracket the trigger.

More interview prep