Senior Lead Engineer, Testing

We are looking for a JB-4 tester who combines strong manual testing skills with hands-on automation experience.

You will support teams by investigating customer issues, validating fixes, improving regression coverage, and helping teams use our proprietary automation platform consistently.

You will work with Product Team, Support QA, Engineering, and the internal tooling team.

You will also guide Automation Design Specialists on complex test scenarios and help scale reusable testing practices across products and client variants.

What You’ll Do Manual testing and support Investigate and reproduce customer issues across environments, roles, configurations, and client variants.

Design and execute functional, integration, regression, smoke, exploratory, and end-to-end tests.

Validate business rules, permissions, APIs, databases, batch jobs, integrations, and time-based scenarios.

Review requirements and acceptance criteria for testability and coverage gaps.

Validate fixes, hotfixes, and releases, and provide clear test evidence.

Create clear defect reports with impact, reproduction steps, logs, and supporting data.

Work with Support and Engineering on defect triage and root-cause analysis.

Convert recurring issues into regression tests, reusable test data, or automation where appropriate.

Automation and framework guidance Evaluate the automation platform against real product and support needs, including dynamic data and multi-role workflows.

Compare platform-generated tests with Selenium or Playwright automation for reliability, coverage, and maintainability.

Recommend the right approach: platform-based, coded, or hybrid automation.

Guide Automation Design Specialists on reusable test components, shared action libraries, and suite design.

Help define API, database, batch-job, and CI/CD integration patterns.

Promote parameterized and reusable test data instead of hardcoded values.

Review automation for stability, useful assertions, diagnostics, and maintenance effort.

Help manage Git branching across multiple products and client variants.

Document platform limitations, POC results, solutions, and workarounds.

Standards and adoption Recommend standards for naming, folder structure, test organization, test data, reporting, and governance.

Encourage reusable test design and consistent practices across teams.

Partner with the tooling team to raise issues and influence the platform roadmap.

Support the rollout of the platform and standards from pilot teams to the wider enterprise.

Coach testers on manual testing, automation practices, troubleshooting, and migration decisions.

Must-Have 3+ years supporting or leading an enterprise-scale test automation platform.

Strong experience in manual testing, defect investigation, regression testing, and release validation.

Hands-on experience with Selenium and/or Playwright.

Good knowledge of API testing, database validation, test data management, and CI/CD.

testing dynamic data, multi-role workflows, integrations, asynchronous processing, or batch jobs.

with Git branching across multiple products, clients, or variants.

Ability to compare automated approaches and recommend practical solutions.

influencing teams to follow standards without formal authority.

Clear written and verbal communication, strong troubleshooting skills, and sound testing judgment.

Nice-to-Have Experience in insurance or another regulated industry.

supporting products with multiple client configurations.

leading a test framework migration.

building or configuring automation frameworks, reusable libraries, or test utilities.

building a custom automation framework from scratch.

partnering with an internal tools or platform engineering team.

Familiarity with accessibility, performance, security, or compliance testing.

What Success Looks Like Support issues are reproduced and validated quickly with clear evidence.

Manual testing leads to focused, reliable regression coverage.

Teams use common standards, reusable components, and maintainable test data.

Automation choices are based on risk, value, stability, and support needs.

Platform gaps are documented and reflected in the tooling roadmap.

The automation platform is adopted consistently across products and client variants.

Track and report OKRs for test coverage, defect prevention, automation adoption, platform usage, and support quality.