How it worksPricingInterview questions
Infosys · QA Automation Tester

Infosys QA Automation Tester Interview Questions (2026): process, questions and answers

Updated 4 November 2026 · prep guide

Infosys QA Automation Tester interviews usually test core automation concepts, coding ability and problem solving in a consulting context. Use this guide to rehearse short, precise answers, understand typical scenario questions and plan a focused final‑day review.

Preparing for Infosys? Rehearse these questions with Interview AI Helper: ask any question and get a suggested answer in seconds, written from your own resume.

Free 5-minute demo

How the Infosys QA Automation Tester interview usually works

  1. Application Screening: Candidates usually clear an online form and a short coding quiz.
  2. Technical Phone/Video: Often includes live coding, Selenium/Playwright questions and API basics.
  3. Onsite/Virtual Panel: Usually a mix of deep technical, scenario and behavioural questions.
  4. HR Discussion: Commonly focuses on teamwork, client handling and career goals.

Technical questions and answers

How would you locate a button whose text changes after a page reload?

Use a stable attribute like data-test-id if available, otherwise locate by XPath that matches the button tag and partial text, e.g., //button[contains(.,'Submit')]. Combine with WebDriverWait for visibility to handle the reload. This avoids relying on volatile text that may vary with locale.

Explain the difference between driver.navigate().back() and driver.get(url).

navigate().back() moves the browser history one step back, preserving the current session state, while get(url) loads a new page and replaces the current document. Use back() for typical user navigation, get() when you need to start from a known URL or reset session data.

What is a keyword‑driven test and how can you implement it with TestNG?

A keyword‑driven test separates test steps (keywords) from code. Store actions like CLICK, ENTER_TEXT in an external sheet, read them in a TestNG data provider, and map each keyword to a method in a utility class. This makes tests readable for non‑technical stakeholders and reusable across multiple test cases.

How can you take a screenshot only when a JUnit test fails without adding code to each test method?

Create a JUnit TestWatcher rule that overrides failed(Throwable e, Description d) and calls TakesScreenshot. Register the rule at the class level so it automatically captures a screenshot for any failing test, keeping test code clean.

Describe how to use Playwright’s locator to click the third item in a dynamic list without hard‑coding the index.

First locate the list container, then chain locator('li').nth(2) (zero‑based) to target the third item. Use await locator('li').nth(2).click() which works even if the list length changes, because Playwright resolves the element at runtime.

Interview with Infosys coming up?

Practise these QA Automation Tester questions out loud and get suggested answers in real time, based on your own resume. Free 5-minute demo, no subscription.

Try the free demo

What is contract testing for APIs and why is it useful in a micro‑service environment?

Contract testing verifies that a service’s request/response schema matches an agreed contract, often defined in OpenAPI or Pact. It catches breaking changes early, ensuring that consumer and provider can evolve independently, which is critical for large consulting projects with many integrated services.

How would you externalize environment URLs in a Maven‑based Selenium project?

Store URLs in a properties file (e.g., env.properties) and load them with java.util.Properties. Use Maven profiles to select the appropriate file via the -P flag, or pass a system property like -Denv=dev and read it in code to pick the right URL at runtime.

Explain why implicit waits are discouraged in modern Selenium scripts.

Implicit waits are global, cause hidden latency, and can interact poorly with explicit waits, leading to unpredictable timeouts. Using explicit waits (WebDriverWait) provides fine‑grained control, makes scripts faster, and improves reliability, which is why many teams disable implicit waits altogether.

How do you handle a modal dialog that appears after clicking a button, using Selenium?

After clicking, wait for the modal’s root element with an explicit wait, then switch to it if it’s in a separate frame. Interact with its controls (e.g., modal.findElement(By.id('confirm')).click()). Finally, wait for the modal to disappear before proceeding.

What is the purpose of a TestNG listener and give a practical example?

A TestNG listener implements interfaces like ITestListener to receive callbacks for test events. For example, onTestFailure can log failure details, capture screenshots, and push results to a reporting dashboard, centralising cross‑cutting concerns without cluttering test code.

Scenario questions

A client reports that a newly deployed feature intermittently fails in production. How would you investigate using automation?

First, reproduce the issue locally using the same data set. Add logs and enable retries in the test to capture flaky behavior. Use API monitoring to verify backend responses. If the failure persists, create a small, focused test that isolates the failing component, run it across environments, and share detailed logs and screenshots with the client.

You need to add regression coverage for a legacy banking portal that has no test IDs. What approach would you take?

Start by mapping critical user flows and using robust locators such as XPath with stable text or relative positions. Introduce a Page Object Model to encapsulate these locators, and gradually refactor the application to add data-test-id attributes where possible. Prioritise high‑risk transactions for early automation.

During a sprint, a teammate merges a change that breaks your CI test suite. How do you respond?

Immediately check the Jenkins console to identify the failing step. Reproduce the failure locally, then open a concise ticket describing the root cause, steps to reproduce, and a suggested fix. Communicate with the teammate, propose a temporary revert if needed, and add a regression test to prevent recurrence.

HR and behavioural questions

Tell us about a time you missed a deadline on an automation task. What did you do?

Use the STAR method: Situation, a release deadline, Task, deliver a full regression suite, Action, identified missing test data, escalated early, and worked overtime with a teammate to create mock data. Result, delivered 90% of tests on time, learned to flag risks earlier and improve data management.

How do you handle conflicting priorities from multiple project managers?

Explain that you first clarify business impact, then negotiate realistic timelines, and keep all stakeholders updated via a shared tracker. Highlight a specific instance where you balanced two urgent releases by reallocating resources and documenting the decision.

Describe a situation where you had to learn a new automation tool quickly.

Mention the context (e.g., client switched from Selenium to Playwright), your learning plan (official docs, sample project, pair‑programming), and the outcome (delivered a proof‑of‑concept within a week, enabling the team to adopt the new tool).

Why do you want to work at Infosys as a QA Automation Tester?

Show knowledge of Infosys’s consulting focus, mention interest in large‑scale digital transformations, and align your automation skills with their need for robust, scalable test frameworks across diverse domains.

Your last 48 hours before the interview

  1. Review the 10 technical Q&A and rehearse each answer aloud, timing yourself.
  2. Run a small Selenium script that includes waits, screenshots on failure, and a listener; verify it works end‑to‑end.
  3. Create a one‑page cheat sheet of common Playwright locator patterns and Maven profile commands.
  4. Practice the three scenario answers, focusing on clear structure and measurable outcomes.
  5. Mock a behavioural interview with a friend, using the STAR format for each question.
  6. Set up a fresh Jenkins job that pulls your repo, runs the TestNG suite, and publishes the HTML report.

Common mistakes to avoid

Frequently asked questions

What topics are most heavily weighted in Infosys QA Automation interviews?

Technical fundamentals like Selenium/Playwright, test framework design, API testing, CI integration and problem‑solving scenarios are common, followed by behavioural questions on teamwork and client handling.

How long does the Infosys QA Automation interview process usually take?

Candidates often experience an initial screening, one or two technical rounds, and a final HR discussion, which can span a few weeks depending on scheduling.

Do I need to know Java for Infosys QA roles?

Java is the most frequently used language in their automation stacks, so a solid grasp of Java basics, OOP and common testing libraries is expected.

Should I bring a portfolio of automation projects?

Yes, a brief showcase of a few end‑to‑end automation suites, preferably with CI integration, demonstrates practical experience and helps answer scenario questions.

Interview with Infosys coming up?

Practise these QA Automation Tester questions out loud and get suggested answers in real time, based on your own resume. Free 5-minute demo, no subscription.

Try the free demo

More Infosys interview guides

QA Automation Tester interview questions at other companies

Related reading

This is an independent preparation guide based on commonly reported interview patterns. The process varies by team, location and year. Interview AI Helper is not affiliated with Infosys.

← All interview question guides