QA Automation Architect / Automation Framework Engineer, HeadSpin

• The ideal candidate brings hands-on experience designing frameworks for scale, security, and long-term stability as applications, teams, and delivery pipelines evolve. This role includes AI-assisted QA initiatives using Azure OpenAI, Claude, and Azure DevOps integrations
• Deep hands-on experience building and maintaining enterprise automation frameworks
• Advanced coding in TypeScript, JavaScript, or C#
• Strong experience with Playwright, Selenium, or similar frameworks
• Demonstrated CI/CD expertise, preferably with Azure DevOps
• Ability to provide real-world examples of framework design decisions and tradeoffs

Desirable

• We seek an architect-level Automation Framework Engineer to design, build, and scale enterprise automation frameworks across UI, API, document, and integration-heavy workflows
• 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

• 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
• This is an architect-level automation role. Candidates must discuss actual projects where they built, scaled, secured, or stabilized automation frameworks—not just concepts. Strong candidates naturally discuss scale, security, stability, framework architecture, CI/CD integration, and maintenance strategy with real-world examples and tradeoffs
• Candidates unable to provide detailed examples of real projects may not be the right fit