Infosys Qa Automation Engineer Sdet Interview Questions (2026)

1. 1Infosys Online Assessment60 minMedium

   Timed test with logical reasoning, verbal ability, quantitative aptitude, and the well-known pseudocode section that decides interview shortlisting and track.

2. 2Power Programmer (SP) Coding Round50 minHard

   For HackWithInfy/InfyTQ-routed candidates, a competitive-programming style interview with 2-3 DSA problems requiring working code and complexity analysis.

3. 3Technical Interview40 minMedium

   Panel covers OOP, DBMS and SQL queries, one or two programs or pseudocode on paper/screen, and a walkthrough of academic or work projects.

4. 4Techno-Managerial Round40 minMedium

   For laterals, a delivery manager probes system-level decisions on past projects, estimation, client communication, and how the candidate handles production issues.

5. 5HR Round25 minEasy

   Values-and-stability conversation covering why Infosys, C-LIFE values awareness, relocation, training agreement, and salary/joining logistics.

1. Q1

   How would you test a REST API endpoint for Infosys's search and filtering experience with authentication, pagination, and error responses?

   MediumAPI/UI automationAPI testingInfosys-specific

   Context: Infosys search and filtering experience

   How to answer: Cover contract checks, status codes, auth failures, paging boundaries, and schema validation. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

2. Q2

   How would you integrate automated tests for Infosys's subscription billing workflow into CI/CD without slowing every pull request?

   MediumDebugging and test strategyCI/CD test executionInfosys-specific

   Context: Infosys subscription billing workflow

   How to answer: Use suite tiers, parallelism, ownership, quarantines, and release-blocking criteria. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

3. Q3

   When would you choose Cypress over Playwright or Selenium for Infosys's order tracking workflow, and what tradeoffs would you call out?

   MediumAutomation codingCypressInfosys-specific

   Context: Infosys order tracking workflow

   How to answer: Compare browser coverage, debugging, network control, speed, and CI behavior. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

4. Q4

   Explain Page Object Model for Infosys's checkout journey. When does it help, and when does it become a bad abstraction?

   MediumAutomation codingPage Object ModelInfosys-specific

   Context: Infosys checkout journey

   How to answer: Keep page APIs user-intent oriented and avoid hiding assertions or business rules. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

5. Q5

   How would you debug a flaky Playwright test in Infosys's admin approval workflow?

   MediumAutomation codingPlaywrightInfosys-specific

   Context: Infosys admin approval workflow

   How to answer: Discuss locators, waits, traces, retries, isolation, network timing, and deterministic assertions. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

6. Q6

   How would you use Postman/Newman in CI for Infosys's seller onboarding flow without making the suite hard to maintain?

   MediumAPI/UI automationPostman/NewmanInfosys-specific

   Context: Infosys seller onboarding flow

   How to answer: Use environments, data files, assertions, secret handling, and useful reports. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

7. Q7

   Design REST API tests for create, update, and delete operations in Infosys's subscription billing workflow

   MediumAPI/UI automationREST testingInfosys-specific

   Context: Infosys subscription billing workflow

   How to answer: Check idempotency, validation, permissions, response shape, and audit events. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

8. Q8

   Which SQL checks would you write to validate data created by Infosys's order tracking workflow?

   MediumAPI/UI automationSQL for testingInfosys-specific

   Context: Infosys order tracking workflow

   How to answer: Check records, joins, statuses, timestamps, aggregates, and reconciliation with UI/API results. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

9. Q9

   How would you handle dynamic elements in Selenium or Playwright for Infosys's notification preference center?

   MediumAutomation codingSeleniumInfosys-specific

   Context: Infosys notification preference center

   How to answer: Prefer stable locators, explicit waits, app test IDs, and avoiding brittle sleeps. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

10. Q10

    What accessibility checks would you include for Infosys's search and filtering experience?

    MediumDebugging and test strategyaccessibility testing basicsInfosys-specific

    Context: Infosys search and filtering experience

    How to answer: Cover keyboard navigation, labels, focus order, contrast, screen-reader basics, and automated plus manual checks. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

11. Q11

    Write the structure of a high-quality bug report for a failure in Infosys's admin approval workflow

    MediumDebugging and test strategybug reportingInfosys-specific

    Context: Infosys admin approval workflow

    How to answer: Include environment, steps, expected versus actual, evidence, severity, and business impact. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

12. Q12

    How would you work with developers when automation exposes recurring defects in Infosys's admin approval workflow?

    EasyBehavioral/project discussioncross-functional communicationInfosys-specific

    Context: Infosys admin approval workflow

    How to answer: Focus on shared ownership, actionable reports, root cause, and prevention. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

13. Q13

    How should a QA automation engineer handle a defect from discovery through closure for Infosys's notification preference center?

    MediumDebugging and test strategydefect lifecycleInfosys-specific

    Context: Infosys notification preference center

    How to answer: Cover triage, reproduction, ownership, retest, regression coverage, and communication. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

14. Q14

    Design an end-to-end test for Infosys's notification preference center. What would you automate, what would you mock, and what would you leave manual?

    MediumAPI/UI automationend-to-end testingInfosys-specific

    Context: Infosys notification preference center

    How to answer: Focus on a few critical journeys, stable data, and readable failure output. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

15. Q15

    A test for Infosys's order tracking workflow fails only in CI. How would you investigate and fix it?

    HardDebugging and test strategyflaky test debuggingInfosys-specific

    Context: Infosys order tracking workflow

    How to answer: Compare local versus CI state, browser versions, timing, data, parallelism, and logs. State the test objective, risk, and the user or system behavior being protected. Describe automation scope, data setup, assertions, observability, and CI ownership. Call out tradeoffs, failure modes, and how you would keep the suite maintainable.

Practice these with instant AI feedback in a live mock interview → Start a Infosys Qa Automation Engineer Sdet mock

Clear the online test; revise coding fundamentals and projects; prepare HR/behavioral

Qa Automation Engineer Sdet interviews at other companies