Skip to main content
Strategy & Process
DEFINITION

What is QA vs QC (Quality Assurance vs Quality Control)?

Quality Assurance (QA) is a process-oriented, preventive activity focused on improving how software is built so defects are less likely, while Quality Control (QC) is a product-oriented, detective activity focused on finding defects in the built software. QA prevents; QC detects.

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

QA and QC are often used interchangeably (and many job titles blur them), but they describe different things. Quality Assurance is about the process: defining standards, reviews, definitions of done, training, and improvements that make defects less likely in the first place. It is proactive and preventive, you are assuring quality by improving how the work is done.

Quality Control is about the product: actually testing the software to find defects, executing test cases, inspecting outputs, and verifying the result against requirements. It is reactive and detective, you are controlling quality by catching problems in the deliverable.

A useful analogy: in a restaurant, QA is designing the recipes, kitchen hygiene standards, and staff training so meals come out right; QC is the chef tasting each dish before it leaves the kitchen. Most testing activity (running test cases) is QC; setting up the process that makes testing effective is QA. Mature teams invest in both, prevention is cheaper than detection, but you still need to catch what slips through.

WHY IT MATTERS

Why interviewers ask about this.

QA vs QC is a classic interview question, and many candidates conflate them. Distinguishing process/prevention (QA) from product/detection (QC), with an example, demonstrates that you understand quality as more than just running tests.

EXAMPLE

Example scenario.

After repeated production bugs, a team adds a definition of done, code reviews, and earlier test involvement (QA, process changes to prevent defects), and continues running its regression suite to catch defects in each build (QC). The process changes reduce how many defects QC has to catch at all.

TIP

Interview tip.

Lead with the one-liner: QA is process and prevention, QC is product and detection. Use the recipe-vs-tasting analogy, and note that running test cases is QC while improving the process is QA. Acknowledge that titles often blur the two.

FAQ

Frequently asked questions.

Is testing QA or QC?

Executing tests to find defects in the product is Quality Control (QC). Quality Assurance (QA) is the broader process work, standards, reviews, definitions of done, that makes defects less likely. The job title "QA" usually covers both in practice.

What is the difference between QA and QC in one line?

QA is process-oriented and preventive (improving how software is built); QC is product-oriented and detective (finding defects in the built software). QA prevents, QC detects.

Related Resources

Dive deeper with these related interview prep pages.

FREE TOOLS  /  no signup

Free QA career tools, no account needed

Instant and private, everything runs in your browser. Try them before you sign up.

EXEC.NOW

Ready to Ace Your QA Interview?

Practice explaining qa vs qc (quality assurance vs quality control) and other key concepts with our AI interviewer.

Join 1,200+ QA engineers already practicing with AssertHired.

Start your free QA interview
FREE.TO.START  ·  7.DAY.TRIAL ON PAID PLANS
Written by Aston Cook, Senior QA EngineerLast updated May 2026