Zensar Technologies—AI Pod- Selenium Java / Playwright Automation Tester

Job description

Description: • Test engineering across unit, integration and regression levels, on codebases they did not write. • Building a validation path where none exists, and automating regression suites that are currently run manually. This is the binding constraint on the whole program — an AI-authored change cannot be merged if nothing can prove it broke nothing. • Working knowledge of at least two of: JUnit, xUnit/NUnit, Selenium or Playwright, REST Assured or equivalent API testing. • Test data management, environment and stub strategy, and flaky-test triage. • Integrating suites into CI and setting quality gates. • Using an AI assistant or agent to generate and maintain tests, and the judgment to know when generated tests are worthless. • At least one of the two seats on each team must be at the upper end of the mid band with demonstrable legacy-stack depth. Nice To Have Performance and load testing. • Testing SQL-heavy systems where business logic sits in stored procedures. • Mainframe or COBOL test tooling. • Test coverage measurement and reporting. • QA lead experience on a regulated product. Requirements: Nice To Have Performance and load testing. • Testing SQL-heavy systems where business logic sits in stored procedures. • Mainframe or COBOL test tooling. • Test coverage measurement and reporting. • QA lead experience on a regulated product Responsibilities: Test engineering across unit, integration and regression levels, on codebases they did not write. • Building a validation path where none exists, and automating regression suites that are currently run manually. This is the binding constraint on the whole program — an AI-authored change cannot be merged if nothing can prove it broke nothing. • Working knowledge of at least two of: JUnit, xUnit/NUnit, Selenium or Playwright, REST Assured or equivalent API testing. • Test data management, environment and stub strategy, and flaky-test triage. • Integrating suites into CI and setting quality gates. • Using an AI assistant or agent to generate and maintain tests, and the judgment to know when generated tests are worthless. • At least one of the two seats on each team must be at the upper end of the mid band with demonstrable legacy-stack depth.