QA InfoTech Test Engineer Interview: Rounds, Questions and Preparation

What the job involves

Test Engineers in Indian IT services manually test software applications, write and execute test cases, log defects, and validate fixes across web, mobile, and desktop platforms. They work closely with developers and business analysts in agile teams, often on client projects with tight deadlines. The role is entry-level friendly and focuses on functional testing, basic automation exposure, and clear defect reporting.

Role and Technical Knowledge

1. 1

   What is the difference between verification and validation in software testing?

   Verification checks if the product is built correctly (reviews, inspections), while validation checks if the correct product is built (actual testing). Give a simple example like verifying a login form design vs validating login works.

2. 2

   Explain the defect life cycle with an example.

   Cover stages: New, Assigned, Open, Fixed, Retest, Verified, Closed, Reopened, Rejected, Deferred. Use a login bug example to show how a defect moves from tester to developer and back.

3. 3

   What is the difference between smoke testing and sanity testing?

   Smoke testing checks critical functionalities on a new build to decide if further testing is possible. Sanity testing checks specific fixes or small changes after a minor build. Mention that smoke is broad and shallow, sanity is narrow and deep.

4. 4

   How do you write a good test case? What are the key elements?

   List elements: Test case ID, description, preconditions, test steps, test data, expected result, actual result, status. Emphasise clarity, reusability, and traceability to requirements.

Practical Scenarios

1. 5

   You find a bug but the developer says it is not reproducible. What do you do?

   Show patience and evidence: provide exact steps, screenshots, video, environment details, test data, and logs. Offer to reproduce together and check if it is environment-specific or intermittent.

2. 6

   You have limited time before a release. How do you prioritise testing?

   Focus on critical and high-risk functionalities first, then regression for core features, then low-priority items. Mention risk-based testing and communication with the lead.

3. 7

   How would you test a login page? List some test cases.

   Cover valid login, invalid password, blank fields, SQL injection, password masking, remember me, forgot password, account lock after failed attempts, and session timeout. Show structured thinking.

4. 8

   What would you do if you found a critical bug just before the release?

   Immediately log it with high severity, inform the test lead and project manager, assess impact, and suggest a go/no-go decision. Do not hide it or delay reporting.

Automation and Tools

1. 9

   What is the difference between manual testing and automation testing?

   Manual testing is human-driven, good for exploratory and usability testing. Automation is script-driven, good for regression and repetitive tasks. Mention that both are needed and automation does not replace manual entirely.

2. 10

   Have you used any automation tool? Explain a simple script you wrote.

   If you know Selenium, describe opening a browser, locating an element, performing an action, and asserting a result. If not, be honest and mention you are learning and show willingness.

3. 11

   What is the use of Postman in testing?

   Postman is used for API testing: sending requests (GET, POST, PUT, DELETE), checking response codes, response body, headers, and validating data. Mention collections and environment variables.

4. 12

   How do you validate data in the database after a test?

   Write simple SQL queries (SELECT, JOIN, WHERE) to check if the UI data matches the database. Example: after registering a user, query the users table to confirm the record.

Behavioural and HR

1. 13

   Tell me about yourself.

   Keep it brief: name, college, degree, relevant skills (testing, SQL, automation basics), projects or internships, and why you want this role. Avoid personal life details.

2. 14

   Why do you want to work as a Test Engineer?

   Show interest in quality, attention to detail, and problem-solving. Mention that testing is a gateway to understanding the full product and you enjoy finding issues before customers do.

3. 15

   Are you willing to relocate or work in shifts?

   Be honest but flexible. Indian IT services often have client locations and shift requirements. Say yes if you are open, or explain your constraints clearly without sounding rigid.

4. 16

   Describe a time you found a mistake in your own work and how you handled it.

   Use a STAR format: situation, task, action, result. Show ownership, quick correction, and learning. Avoid blaming others or saying you never make mistakes.