Infosys QA Automation Interview Questions (3–4 YOE) | Real-Time Interview Questions

If you’re preparing for QA Automation, SDET, or Test Automation Engineer roles with 3–4 years of experience, here are some real-time interview questions reportedly asked during an Infosys QA Automation interview.

📌 Interview Questions
1- Self Introduction and explain your current project in brief.
2- What Agile ceremonies are followed in your project?
3- What is a Product Backlog and who owns it?
4- During Sprint Planning, how do you estimate story points for a user story?
5- Do all tickets require QA intervention? Can you give some examples?
6- What is Regression Testing and why do we perform it?
7- Which test management and defect tracking tools are you using in your current project?
8- What are some Selenium exceptions you have encountered in your project?
9- What is StaleElementReferenceException and in what scenarios have you faced it?
10- Explain the difference between Implicit Wait, Explicit Wait, and Fluent Wait.
11- How do you handle dynamic web elements in Selenium?
12- How do you handle dropdowns when the Select class cannot be used?
13- I have multiple browser windows opened. 14- How will you switch from one window to another?
15- How do you handle alerts and popups in Selenium?
16- What is the difference between findElement() and findElements()?
17- What is an API and how is it different from a Web Service?
18- What is a JWT Token and Bearer Token?
19- What validations do you perform while testing APIs?
20- Write a Java program to remove duplicate characters from a String.
21- Write a Java program to print a pyramid star pattern.
22- Write the syntax for Login Functionality.
23- Suppose a release is planned for tomorrow and you still have many tickets in your testing bucket. How will you manage the situation?
24- What will be your approach if a critical defect is found just before Production deployment?
25- Have you ever faced a Production issue? What was your role in identifying or resolving it?
26- A bug is reproducible in Production but not in QA. How will you investigate the issue?