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.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

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 IT MATTERS

Why interviewers ask about this.

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.

EXAMPLE

Example scenario.

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.

TIP

Interview tip.

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.

FAQ

Frequently asked questions.

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.