InterviewEra.com

AI-powered mock interviews and resume-aware scoring — built for Indian campus and early-career hiring. Now in private beta.

Start Mock Interview
Secure payments via Razorpay

Tools

  • Question Generator
  • ATS Resume Checker
  • STAR Builder

Interview Questions

  • Software Engineer Questions
  • TCS Interview Questions
  • React Interview Questions

Resources

  • Blog
  • Placement Guide
  • STAR Method Guide

Company

  • About
  • Pricing
  • Contact

© 2026 InterviewEra.com. All rights reserved.

Privacy PolicyTermsRefundRanchi, Jharkhand, India
Interview Questions›QA Engineer

quality · Fresher-friendly

QA Engineer Interview Questions India 2026

QA Engineer interview questions on manual testing, test case design, automation fundamentals, and bug lifecycle.

Fresher-friendlyquality role12 curated questionsUpdated 2026

QA Engineers Interview Questions

Placement-oriented · Updated 2026
  1. 01

    What is the difference between functional and non-functional testing?

    TechnicalEasy

    Tip: Functional: tests WHAT the system does (login works, payment processes correctly). Non-functional: tests HOW WELL it does it (performance under load, security hardening, usability). Both are required.

  2. 02

    What is the Software Testing Life Cycle (STLC)? List and explain each phase.

    TechnicalEasy

    Tip: Phases: Requirement Analysis, Test Planning, Test Case Design, Environment Setup, Test Execution, Test Closure. QA is involved from requirements — not just at the end. Early defect detection is 10x cheaper than post-release fixes.

  3. 03

    What is the difference between black-box and white-box testing?

    TechnicalEasy

    Tip: Black-box: tester has no knowledge of internal code — tests against requirements (functional testing, UAT). White-box: tester knows the internal code — tests code paths, branches, and conditions (unit tests, code coverage).

  4. 04

    What is regression testing and when is it run?

    TechnicalEasy

    Tip: Regression testing: re-running existing test cases after a code change to ensure nothing that worked before is now broken. Run after every code change, especially before releases. Automated regression suites make this practical at scale.

  5. 05

    What is Selenium WebDriver? What are its key limitations?

    TechnicalMedium

    Tip: Selenium controls browsers via WebDriver protocol — ideal for simulating real user interactions. Limitations: flaky tests due to timing (use explicit waits, not Thread.sleep), no built-in test runner, slow compared to component tests. Playwright is the modern alternative.

  6. 06

    What is the difference between TDD and BDD?

    TechnicalMedium

    Tip: TDD (Test-Driven Development): write unit tests before code (red-green-refactor cycle). BDD (Behaviour-Driven Development): define behaviour in Given-When-Then language (Gherkin), bridging business and technical teams. TDD is a coding practice; BDD is a collaboration process.

  7. 07

    How do you test a REST API? What aspects do you check and what tools do you use?

    TechnicalMedium

    Tip: Check: status codes, response schema, error messages, edge cases (empty input, large payload), auth (unauthenticated gets 401, wrong role gets 403), performance (response time within SLA). Tools: Postman (manual), REST Assured (Java), pytest (Python), Newman (CI).

  8. 08

    Tell me about the most critical bug you found. How did you find it and what was its impact?

    BehavioralMedium

    Tip: Describe the bug discovery method: exploratory testing, edge case in test design, or automated test catching a regression. Quantify impact: "would have caused data loss for 12,000 users." Show you understand what made it critical.

  9. 09

    You find a production-impacting bug 1 hour before a scheduled release. What do you do?

    SituationalHard

    Tip: Immediately escalate to the release manager — do not try to fix it yourself in an hour. Assess severity and workaround availability. Document the bug clearly. The team decides: delay release, hotfix, or release with a known limitation.

  10. 10

    What makes a good test case? List the essential attributes.

    TechnicalEasy

    Tip: Essential attributes: unique ID, clear title, preconditions, step-by-step actions, expected result, actual result field, priority/severity. A good test case is: unambiguous, repeatable, traceable to a requirement, atomic (tests one thing), and maintainable.

  11. 11

    How do you prioritise which bugs to test and report first?

    TechnicalMedium

    Tip: Prioritise by: severity (data corruption > crash > functional failure > cosmetic) multiplied by frequency (how many users hit this). Align with the product manager on release goals.

  12. 12

    When do you choose manual testing over automation? Give two concrete examples.

    HREasy

    Tip: Manual is better for: exploratory testing (investigating unknown defects), short-lived features (automation ROI is negative if the feature ships once), usability testing (human judgement required). Automation wins for: regression, load testing, repetitive smoke tests.

Key topics to prepare for QA Engineer interviews

Recruiters test these skill areas specifically. Click any topic to see curated questions.

SQLRESTGit

Practice, not just reading

Get scored on your QA Engineer answers

Upload your resume and practice a full QA Engineer mock interview with AI-generated questions and rubric-based scoring across 5 dimensions — free to start.

Start free mock interviewGenerate more questions free

Companies hiring QA Engineers

  • Wipro QA questions

Practice tools

  • QA question generator
  • QA ATS checker
  • STAR answer builder

Guides and resources

  • All interview questions
  • STAR method with examples
  • HR interview answer tips
  • Placement interview prep guide