QA Automation Engineer
Location:
Remote
Role Overview:
We’re hiring a QA Automation Engineer to own our end-to-end UI regression automation: the framework, the suite, and the signal it produces. This is a build-and-maintain role, not a run-the-scripts role. You’ll design the harness, grow coverage across a large and mature application, keep the suite fast and trustworthy, and wire it into our release pipeline so teams get real feedback before code ships.
Responsibilities & Duties:
Own the E2E automation framework. Design and maintain the structure — page objects or equivalent abstractions, fixtures, shared utilities, and reporting.
Build and expand the regression suite across critical workflows: e-filing submission and review, case and docket management, document generation and retrieval, search, notifications, and role-based access.
Fight flakiness relentlessly. Replace timing-based waits with deterministic conditions, isolate tests from each other, triage and quarantine unstable tests, and track pass-rate trends.
Integrate with CI/CD. Run the suite in Azure DevOps pipelines, manage parallelization and runtime budgets, and make failures legible — clear reports, screenshots, traces, and logs that point at a cause instead of starting an investigation.
Cover the permission matrix. Verify that what a user can see and do is correct across roles and tenants (court staff, clerks, judicial officers, filers, public access), where a mistake is a confidentiality problem and not just a bug.
Partner with development. Review UI changes for testability, push for stable selectors and test hooks, and raise quality risks early rather than at the end of a sprint.
Contribute to manual and exploratory testing where automation isn’t the right tool, and help the team decide which is which.
Skills, Knowledge & Abilities:
Own the E2E automation framework. Design and maintain the structure — page objects or equivalent abstractions, fixtures, shared utilities, and reporting.
Build and expand the regression suite across critical workflows: e-filing submission and review, case and docket management, document generation and retrieval, search, notifications, and role-based access.
Fight flakiness relentlessly. Replace timing-based waits with deterministic conditions, isolate tests from each other, triage and quarantine unstable tests, and track pass-rate trends.
Integrate with CI/CD. Run the suite in Azure DevOps pipelines, manage parallelization and runtime budgets, and make failures legible — clear reports, screenshots, traces, and logs that point at a cause instead of starting an investigation.
Cover the permission matrix. Verify that what a user can see and do is correct across roles and tenants (court staff, clerks, judicial officers, filers, public access), where a mistake is a confidentiality problem and not just a bug.
Partner with development. Review UI changes for testability, push for stable selectors and test hooks, and raise quality risks early rather than at the end of a sprint.
Contribute to manual and exploratory testing where automation isn’t the right tool, and help the team decide which is which.
Job Requirements:
Own the E2E automation framework. Design and maintain the structure — page objects or equivalent abstractions, fixtures, shared utilities, and reporting.
Build and expand the regression suite across critical workflows: e-filing submission and review, case and docket management, document generation and retrieval, search, notifications, and role-based access.
Fight flakiness relentlessly. Replace timing-based waits with deterministic conditions, isolate tests from each other, triage and quarantine unstable tests, and track pass-rate trends.
Integrate with CI/CD. Run the suite in Azure DevOps pipelines, manage parallelization and runtime budgets, and make failures legible — clear reports, screenshots, traces, and logs that point at a cause instead of starting an investigation.
Cover the permission matrix. Verify that what a user can see and do is correct across roles and tenants (court staff, clerks, judicial officers, filers, public access), where a mistake is a confidentiality problem and not just a bug.
Partner with development. Review UI changes for testability, push for stable selectors and test hooks, and raise quality risks early rather than at the end of a sprint.
Contribute to manual and exploratory testing where automation isn’t the right tool, and help the team decide which is which.