Sr. SDET (Sr Software Engineer in Test & Merchandising Automation)

About the role

Subway's Merchandising Automation team is building the integration and data pipelines that replace manual Digital Merchandising workflows across owned channels and third-party delivery partners - and the Sr. SDET is the engineering voice of quality in that effort.

Responsibilities

• Lead the design and development of automated test frameworks and suites covering functional, integration, contract, performance, and end-to-end scenarios for Subway's Digital Merchandising platform - spanning the Node.js/TypeScript APIs and event-driven pipelines that drive menu publishing, promotional scheduling, and item availability across Mobile App, Web, Kiosk, and third-party delivery partners.
• Write test code to the same quality standards as production code.
• Leverage AI-assisted development tools (GitHub Copilot, Claude, and similar) as a core part of daily engineering work - from generating and refining test cases and synthetic merchandising data to analyzing failure patterns, mapping coverage gaps, and producing documentation.
• Catch scenario failures and data mismatches before they reach production.
• Partner with the Merchandising Automation integration engineers and the Senior Quality Engineer throughout the development lifecycle: collaborate on test strategy, review integration designs and API contracts for testability, define acceptance criteria, and integrate automated quality gates into CI/CD pipelines via Azure DevOps or GitHub Actions.
• Design and execute performance and reliability test strategies - including load, stress, and soak testing - against merchandising APIs and event-driven pipelines to establish service baselines, surface bottlenecks, and validate SLA compliance for high-volume promotional events and menu publishing windows.
• Define and track test coverage and quality metrics across the Merchandising Automation portfolio; contribute to incident post-mortems with defect analysis, regression findings, and recommendations for long-term test strategy improvements.

Qualifications, Competencies & Traits

• Demonstrated ability to architect and build automated test frameworks from the ground up for distributed, API-driven and event-driven systems.
• Bachelor's degree or higher in Computer Science, Software Engineering, or a related field (or equivalent practical experience).
• 5 or more years of experience as an SDET or software engineer with a strong focus on test automation and quality engineering.
• Proficiency in JavaScript/TypeScript (Node.js) for writing production-quality test code; Playwright required for UI and API automation.
• Experience testing event-driven and integration architectures - AWS Lambda, SQS/SNS, API Gateway, or equivalent async messaging systems.
• Hands-on experience validating iPaaS or workflow automation platforms - Adobe Workfront Fusion, MuleSoft, Zapier, or similar scenario-based integration tools strongly preferred.
• Experience designing and executing performance, load, and reliability test strategies against backend APIs and event pipelines.
• Experience embedding automated tests into CI/CD pipelines (Azure DevOps, GitHub Actions, or equivalent).
• Familiarity with contract testing approaches and consumer-driven contract frameworks (Pact or similar).
• Proficiency with AI-assisted development tools (GitHub Copilot, Claude, or equivalent) - comfortable using AI daily to author tests, generate synthetic data, and analyze failures.
• Strong software engineering fundamentals - able to write clean, maintainable, reviewable test code that the broader engineering team can own.
• Systems-level thinking: able to reason about distributed architectures, async data flows, and failure modes across integration boundaries - including both AWS-native and Fusion-based pipelines.
• Clear communicator who can translate test findings and coverage gaps into actionable engineering priorities for both technical engineers and marketing/ops stakeholders.
• Collaborative approach - operates as a full member of the engineering team, not a downstream QA gate.