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.
Job Requirements:
3+ years building UI automation for a non-trivial web application, with demonstrated ownership of a suite over time — not just authoring tests inside someone else’s framework.
Strong hands-on experience with a modern E2E framework — Playwright, Cypress, or Selenium/WebDriver — and the judgment to explain the tradeoffs between them.
Experience testing single-page applications (Angular, React, or Vue) and comfort with the async behavior, dynamic rendering, and component-level quirks that make SPAs harder to automate than server-rendered pages.
Working SQL ability — you can query and manipulate a relational database directly to set up state and verify results the UI doesn’t show you.
CI/CD experience running automated suites in a pipeline (Azure DevOps, GitHub Actions, Jenkins, or similar).
Track record of maintaining a suite through application change — you’ve dealt with a UI redesign or major refactor and kept coverage alive through it.
Clear written communication. Defect reports that a developer can act on without a follow-up conversation.
Skills, Knowledge & Abilities:
Experience with Angular specifically, including component testing and Angular’s async patterns.
API-level test automation (REST/SOAP) and an understanding of when to test below the UI instead of through it.
Accessibility testing against WCAG 2.1 AA / Section 508, including automated scanning tools — a real requirement for public-facing court systems.
Experience testing document-heavy workflows: file upload, PDF generation and validation, e-signature, batch processing.
Experience with multi-tenant or highly configurable applications where behavior varies by client or jurisdiction.
Familiarity with .NET-based backends.
Performance or load testing exposure.