• Test development: Maintain and extend the existing Selenium-based E2E automation suite; improve stability, coverage, and execution efficiency over time. Identify opportunities to introduce automation at additional layers — API, integration, or component — as the team's practices evolve. • Observability for tests: Instrument logs/metrics/traces, define SLIs/SLOs, and build dashboards for build health and flake rates. • Shift-left collaboration: Drive testability discussions with product and engineering; shape acceptance criteria, identify gaps early in design, and influence how features are built to support automated verification. • Hands-on coding: Write clean, maintainable C#/.NET code in both product and test repositories; architect test harnesses, utilities, and shared libraries with longevity in mind. • Test data: Define and implement test data strategies for the team — seeding, anonymization, and repeatable fixture management. • CI/CD quality gates: Design and implement YAML-based pipeline stages in Azure DevOps; take ownership of quality gate configuration, artifact management, and test execution scheduling within the pipeline. • Cloud & infrastructure: Develop working knowledge of AWS-hosted environments; take increasing ownership of environment configuration and infrastructure practices as the team scales its cloud footprint. • Documentation: Produce and maintain documentation for automation frameworks, test processes, and runbooks; raise the floor for the team's collective knowledge.