Skip to main content

QA fundamentals interview questions, 2026

Almost every QA interview opens here. Get these right and you set the tone.

Every QA interview opens with at least one of these. Hiring managers use them as a calibration check before getting into specifics: do you understand the relationship between QA, QC, and testing; can you respond professionally to "works on my machine"; can you structure an answer when asked "test a pencil." The questions below come from real interview rounds at Indian product companies in 2025-2026.

3 questionsIndia context · 2026
  1. Q1What's the difference between QA, QC, and testing?
    What the interviewer is really listening for

    They want to hear that you understand the difference between process (QA), product check (QC), and the act of executing (testing). Most candidates conflate all three.

    Sketch answer (adapt, do not memorise)

    QA is *process focus*, are we building things the right way? Standards, reviews, training. QC is *product focus*, did this specific build come out right? Smoke tests, sign-offs. Testing is the *act* of executing the system to find defects. Testing sits inside QC; QC sits inside QA.

  2. Q2A developer says "my code works on my machine." How do you respond?
    What the interviewer is really listening for

    They want to see that you understand environment, data, and config differences, and that you ask sharp questions rather than push back combatively.

    Sketch answer (adapt, do not memorise)

    I'd ask: which environment? Same OS, same browser, same data, same feature flags, same network? "Works on my machine" usually means there's a hidden assumption, my job is to find and document what's different.

  3. Q3How would you test a pencil?
    What the interviewer is really listening for

    The classic "test anything" question. They want structured thinking: clarify, identify users + uses, list scenarios across families, prioritise by risk.

    Sketch answer (adapt, do not memorise)

    I'd clarify first: who uses it, where, for what? Then I'd list scenarios across positive (write on paper), negative (write on glass), edge (write upside-down, write in vacuum), and exploratory (drop test, eraser life). Finally I'd prioritise by risk, the highest-impact failure modes get tested first.

More interview prep