AI Central - Unit Test Automation Engineer

Test automation on large enterprise codebases, including code written without testability in mind.
• Demonstrable experience putting a validation path onto code with little or no existing coverage: characterization tests, introducing seams, dependency breaking, test-data and fixture strategy.
• Deep in at least two of: Java (JUnit 5, Mockito), C#/.NET (xUnit, NUnit), C++, JavaScript/TypeScript (Jest, Selenium, Playwright).
• Designing and running regression automation as a managed, repeatable process rather than a set of scripts.
• CI integration and quality gates: GitHub Actions, or Jenkins pipelines; coverage instrumentation and static analysis gates.
• Practical, current use of an AI coding assistant or coding agent to generate, triage and maintain tests at volume — not tool familiarity, operating experience.

Nice To Have

Mutation testing.
• Contract testing and service virtualization.
• Test tooling for mainframe or COBOL estates.
• SQL-heavy systems where business logic sits in stored procedures.
• Building reusable internal test libraries for other teams to consume.

Test automation on large enterprise codebases, including code written without testability in mind.
• Demonstrable experience putting a validation path onto code with little or no existing coverage: characterization tests, introducing seams, dependency breaking, test-data and fixture strategy.
• Deep in at least two of: Java (JUnit 5, Mockito), C#/.NET (xUnit, NUnit), C++, JavaScript/TypeScript (Jest, Selenium, Playwright).
• Designing and running regression automation as a managed, repeatable process rather than a set of scripts.
• CI integration and quality gates: GitHub Actions, or Jenkins pipelines; coverage instrumentation and static analysis gates.
• Practical, current use of an AI coding assistant or coding agent to generate, triage and maintain tests at volume — not tool familiarity, operating experience.

Nice To Have

Mutation testing.
• Contract testing and service virtualization.
• Test tooling for mainframe or COBOL estates.
• SQL-heavy systems where business logic sits in stored procedures.
• Building reusable internal test libraries for other teams to consume.