Software Testing and QA Interview Questions for India 2026

Types of testing: Unit (individual functions), Integration (component interactions), System (complete application), Acceptance/UAT (stakeholder end-to-end), Regression (after code changes), Smoke (critical features after a build), Sanity (narrow re-test of changed area), Exploratory (unscripted experience-based). Test design techniques: Equivalence Partitioning (valid and invalid input groups), Boundary Value Analysis (values at input range edges), Decision Table Testing (complex business rules with multiple conditions), State Transition Testing (login/logout flows, carts). Verification vs validation: Verification: are we building the product right? Validation: are we building the right product?

Selenium WebDriver + Java/TestNG is the standard stack at Indian service IT QA teams. Python + Selenium is increasingly common. Key concepts: locators (id, className, CSS selector, XPath), waits (explicit vs implicit vs fluent), Page Object Model (POM: separating page element code from test code). Cypress: modern JavaScript-based testing, faster execution, better debugging: increasingly preferred at product companies. Playwright (Microsoft): multi-browser, better parallel execution, growing rapidly. Appium: mobile app testing for iOS and Android. API testing: Postman, RestAssured (Java), pytest-requests (Python).

Defect lifecycle: New, Assigned, In Progress, Fixed, Closed/Reopened/Rejected/Deferred. Good bug reports: concise title, environment, numbered reproduction steps, expected vs actual result, severity, priority, screenshots/logs. Severity vs Priority: severity = impact on system. Priority = urgency to fix. A cosmetic bug on the homepage might be Low Severity but High Priority. Test management tools: JIRA (most common), TestRail, HP ALM (large enterprise). ISTQB Foundation Level (CTFL): widely referenced in Indian QA job postings. Recommended for early-career QA professionals.

Senior QA interviews test framework design: POM (Page Object Model): page-specific code separated from test code: maintainability and reusability. When UI changes, update the POM class, not the tests. Data-Driven Testing: separate test data from test logic. Data stored in Excel/CSV/JSON. TestNG DataProvider, pytest parametrize. BDD (Behaviour-Driven Development): Gherkin Given-When-Then syntax readable by non-technical stakeholders. Tools: Cucumber (Java/Ruby), Behave (Python). Widely used where PMs are involved in QA. Test parallelism: Selenium Grid or TestNG parallel groups to reduce execution time.

QA engineers in India earn 4-8 LPA at entry level, typically joining service firms like TCS, Wipro, or Capgemini. Manual QA specialists with 3-5 years earn 9-18 LPA, while automation engineers with strong Selenium or Cypress skills command 14-25 LPA. SDET roles at product companies like Swiggy, Razorpay, Atlassian India, or Flipkart pay 22-40 LPA for senior profiles. Hyderabad and Pune have significant QA hiring due to Microsoft and Veritas offices. Automation engineers who learn performance testing with JMeter and cloud testing on BrowserStack or Sauce Labs can negotiate 20-30 percent higher packages compared to pure functional testers.

Indian product companies increasingly test QA candidates on non-functional testing skills beyond functional automation. Performance testing questions focus on JMeter test plan design, identifying think time, and interpreting response time percentiles like P90 and P99 under load. Security testing basics are expected at fintech firms like Paytm, PhonePe, and BankBazaar, including knowledge of OWASP Top 10 vulnerabilities such as SQL injection and XSS. Candidates should understand how to write negative test cases for payment flows and boundary value analysis for form inputs. Knowing how to test REST APIs for authentication bypass and improper error message exposure is a strong differentiator in fintech QA interviews.

Most Indian product companies follow Scrum or Kanban, so expect behavioral questions around your role in sprint ceremonies. Interviewers want to know how you handled shifting requirements mid-sprint, how you collaborated with developers during unit test design, and how you tracked defect metrics like defect density and escape rate. Companies like Juspay, Razorpay, and Cred specifically ask about shift-left testing practices where QA involvement begins at story grooming rather than after development. Knowing how to write Given-When-Then BDD scenarios using Cucumber and integrating them into CI pipelines with Jenkins or GitHub Actions is a strong signal that you can operate at the pace modern Indian startups require.