Automation Framework Architect

We are seeking an architect-level Automation Framework Engineer to design, build, scale, and maintain enterprise automation frameworks across UI, API, document, and integration-heavy workflows. This role will also support AI-assisted QA initiatives (E.g. test generation, pipeline support and failure analysis)

The ideal candidate can speak to real-world examples of how they have designed frameworks for scale, security, and long-term stability as applications, teams, environments, and delivery pipelines evolve.

Key Responsibilities

• Architect, build, and maintain scalable UI automation frameworks using Playwright and Selenium
• Design frameworks supporting multiple teams, applications, environments, and CI/CD pipelines
• Build reusable API and integration testing components (Postman, GraphQL, PactumJS, REST clients)
• Support document-heavy and compliance-driven workflows (disclosure validation, OCR, document intelligence)
• Implement automation observability: logging, diagnostics, flaky test detection, and trend reporting
• Support AI-assisted automation: test generation, regression optimization, and failure triage

Requirements

Required Experience

• Deep hands-on experience building and maintaining enterprise automation frameworks
• Advanced coding experience in TypeScript, JavaScript, or C#
• Strong experience with Playwright, Selenium, or similar automation tools
• Strong CI/CD experience, preferably with Azure DevOps
• Experience designing automation for distributed systems, APIs, integrations, and complex workflows
• Ability to explain real-world framework design decisions, tradeoffs, and long-term maintenance strategies

Core Evaluation Areas

Scale

Candidates must explain how they designed automation frameworks that scaled across teams, applications, and environments. Examples may include scaling test execution across CI/CD pipelines, supporting multiple products from one framework, designing reusable components, and managing test data and environment configuration.

Security

Describe security practices when building frameworks: secure credential management, avoiding hardcoded secrets, role-based access, secure test data handling, pipeline security, and protection of sensitive data.

Stability

Explain how automation remained stable as applications evolved: reducing flaky tests, maintaining reusable selectors, versioning framework components, handling application changes without large rewrites, and separating true defects from automation failures.