What is Root Cause Analysis (RCA)?

Root cause analysis (RCA) is a structured process for finding the underlying cause of a defect or incident, the thing that, if fixed, prevents the whole class of problem from recurring, rather than just patching the visible symptom.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

When a bug escapes to production or a test keeps failing, fixing the immediate symptom is rarely enough. RCA asks why the problem happened, and why that happened, until you reach a cause you can actually change. The most common technique is the 5 Whys: repeatedly asking "why" (roughly five times) until you move from symptom to systemic cause. A fishbone (Ishikawa) diagram is used when there are several contributing factors across categories like process, environment, code, and data.

In QA, RCA usually produces two outputs: a fix for the defect, and a prevention, often a new test, a guardrail, or a process change so the same class of bug cannot silently return. A mature RCA also asks "why did our tests not catch this?", which frequently surfaces a coverage or environment gap as the real root cause.

Good RCA is blameless. It targets systems and processes, not individuals, because a culture that blames people gets fewer honest post-mortems and learns less.

WHY IT MATTERS

Why interviewers ask about this.

Interviewers ask about RCA to separate testers who close bugs from engineers who prevent them. Tying a root cause to a new test or guardrail is one of the strongest quality signals you can give.

EXAMPLE

Example scenario.

A payment occasionally fails silently. 5 Whys: it failed because the client did not handle a 200-with-error response; why? because the contract was ambiguous; why? because there was no contract test; why? because integration coverage stopped at the happy path. The root cause is a missing negative contract test, so the fix plus a new test prevents the whole class.

TIP

Interview tip.

Walk an interviewer through a real 5 Whys you did, and end on the prevention (the test or guardrail you added). Adding "and I asked why our tests missed it" shows mature, systemic thinking.

FAQ

Frequently asked questions.

What is the 5 Whys technique?

The 5 Whys is a root cause analysis method where you repeatedly ask "why" (about five times) to move from the visible symptom to the underlying systemic cause you can actually fix and prevent.

Why should root cause analysis be blameless?

Blameless RCA targets systems and processes rather than individuals. When people are not blamed, they report problems honestly and the team learns more, which is the whole point of the exercise.