What is Severity vs Priority?
Severity measures the technical impact of a defect on the system, while priority measures how urgently it should be fixed relative to other work. They are set independently and do not always move together: a typo in the company name on the homepage is low severity and high priority; a crash in a rarely used admin report is the reverse.
No account needed · Scored in under a minute against a senior rubric
What does Severity vs Priority mean in practice?
Severity is an objective, mostly QA-owned judgment about how badly the bug damages functionality: a crash or data loss is high severity; a cosmetic misalignment is low. Priority is a business-owned decision about scheduling: how soon, relative to everything else, the team should fix it.
The reason this is the most common defect-management interview question is that the four combinations each tell a different story. High severity, high priority: a checkout crash blocking all purchases, fix now. High severity, low priority: a crash on an admin screen one internal user touches monthly, real but can wait. Low severity, high priority: a typo in the company name on the landing page or a wrong logo, trivial technically but embarrassing and urgent. Low severity, low priority: a minor padding issue on a rarely visited page, backlog.
Separating the two prevents two failure modes: treating every crash as drop-everything regardless of who it affects, and ignoring "cosmetic" issues that are actually brand or trust emergencies. Mature teams let QA propose severity and let product or a triage forum set priority.
Why do interviewers ask about Severity vs Priority?
This is a near-guaranteed QA interview question. Interviewers want to hear that you keep impact (severity) and urgency (priority) separate and can give a crisp example of each non-obvious combination, especially low severity with high priority.
What does Severity vs Priority look like in a real project?
A release has two bugs: a rare crash in an internal admin export (high severity, low priority) and a misspelled product name on the public homepage (low severity, high priority). The admin crash waits for the next sprint; the typo ships as a hotfix that afternoon. Same release, opposite handling, exactly because severity and priority are independent.
How should you talk about Severity vs Priority in an interview?
Define both in one sentence each (severity = impact, priority = urgency), then immediately give the low-severity/high-priority example. That single example proves you understand they are independent.
Go Deeper on Severity vs Priority
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about Severity vs Priority
Can a bug be low severity but high priority?
Yes, and it is the example interviewers want. A typo in the company name or a wrong logo on the homepage is technically trivial (low severity) but embarrassing and urgent (high priority), so it gets fixed immediately.
Who decides severity and priority?
Severity is usually proposed by QA based on technical impact. Priority is owned by product or a triage forum based on business urgency. Keeping the two roles distinct is part of a healthy defect process.
Which terms relate to Severity vs Priority?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining severity vs priority and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account