Severity vs Priority
The one every interviewer asks, and the one that trips up even experienced testers. Here’s the clean version you can actually remember.
🧠 Severity = how bad the bug is. Priority = how soon you fix it.
Severity
How seriously the defect affects the application’s functionality. It’s about technical impact: does it crash, corrupt data, block a feature, or is it just cosmetic? The tester sets it, and it doesn’t change based on business mood.
Typical levels
Critical · Major · Minor · Trivial
Priority
How soon the defect should be fixed. It’s about business urgency: release deadlines, customer impact, visibility. Usually the product manager or lead decides it (with QA’s input), and it can shift as plans change.
Typical levels
High (P1) · Medium (P2) · Low (P3)
Side by side
| Severity | Priority | |
|---|---|---|
| What it measures | How badly the defect affects the product | How soon the defect should be fixed |
| Driven by | Technical impact / functionality | Business need & urgency |
| Usually set by | QA / tester | Product manager / lead (with QA input) |
| Changes over time? | Stays the same, it's the impact | Can change with release plans & business |
| Question it answers | “How bad is it?” | “When do we fix it?” |
The 4 combinations (with real examples)
This is the part interviewers love. Give an example for each and you stand out.
Fix immediately
Payment fails on checkout. Users can't pay. Breaks a core flow AND hurts revenue right now.
Bad, but can wait
The app crashes on a rarely-used report screen, or only on a phone model almost no one uses. Big impact, tiny audience.
Small, but fix now
The company name is misspelled on the homepage, or the logo is wrong. Cosmetic, but embarrassing and very visible, so fix it fast.
Backlog it
A minor text-alignment glitch on a help page that few people visit. Low impact, no urgency.
How to answer it in the interview
Don’t just define the two words. Show you understand the difference:
“Severity is how badly the bug impacts the product. It’s technical and set by QA. Priority is how soon we should fix it. It’s a business call. They’re independent: a misspelled company name on the homepage is low severity but high priority, while a crash on a screen almost no one uses can be high severity but low priority.”
Common follow-ups they’ll ask:
- “Give me an example of high severity but low priority.” (Use the rare-screen crash.)
- “Who decides each one?” (Severity → QA; Priority → PM/lead, with QA input.)
- “Can priority change but severity stay the same?” (Yes, severity is the impact; priority follows the release plan.)
Want more than the cheat sheet?
Free. Lands in a minute or two, check all folders.
Want the full interview prep?
Manual, Selenium, Playwright & Python kits: Q&A, coding, and résumé templates.
🔥 See the SDET Kits