Software Engineer in Test; SDET​/QA Automation Engineer

As a Software Engineer in Test, you will own the automated testing that keeps our platform dependable at the scale enterprises bet their partner revenue on. You will be embedded in an agile product team, testing new features hands‑on, building resilient end‑to‑end automation with Playwright in C#/.NET, and extending coverage into API test suites wired into our Git Lab CI/CD pipelines.

You will use AI tools like Claude Code as a daily lever to write and maintain tests faster and widen coverage, while applying the judgment to know what to trust and what to verify. When something breaks, you will reproduce, root‑cause, and report clearly, then partner with engineers to get fixes shipped and verify they landed.

Your key objective is to make risk‑based calls on what to automate versus explore, surface the signals the team needs to ship with confidence, and treat quality as an engineering discipline rather than a checkbox at the end of a sprint.

This role is ideal for someone with a strong engineering foundation who has owned end‑to‑end automation at scale, communicates clearly across technical and non‑technical audiences, and wants to be an embedded quality owner with real ownership and autonomy.

• Test your team’s work, hands‑on — embedded in an agile team, inspecting new features day to day with manual and exploratory testing first, reporting defects clearly, and automating what’s worth keeping.
• Own our end‑to‑end automation with Playwright — designing, building, and evolving UI automation in C#/.NET across our web application, focused on resilient tests rather than brittle ones.
• Test beyond the UI by building API test suites that validate our services and integrations, and wiring everything into Git Lab CI/CD so every change is checked automatically — fast, stable, and trusted.
• Use AI as a daily lever, working with tools like Claude Code to write and maintain tests faster and widen coverage, with the judgment to know what to trust and what to verify.
• Own failures end to end — reproducing, root‑causing, and reporting clearly, then partnering with engineers to get fixes shipped and verifying they landed.
• Shape test strategy by making risk‑based calls on what to automate versus explore, and surfacing the signals the team needs to ship with confidence.

• A strong engineering foundation — 5+ years building or testing production software, fluent in C# (or a comparable language). Experienced QA engineers and software engineers moving into quality are equally welcome.
• Experience owning E2E automation at scale — you’ve built or substantially evolved a Playwright (or Selenium/Cypress) suite, and you know why suites go brittle and how to fix it at the root, not with retries.
• Strong, practical use of AI coding tools with a formed point of view on where they shine and where they mislead.
• Exceptional communication skills — you can explain a bug, a risk, or a trade‑off clearly to engineers, PMs, and non‑technical stakeholders, and back a hold‑the‑release call with evidence.

• API testing depth, including Postman/REST fundamentals, SQL, and data validation.
• Type Script/JavaScript fluency — enough to read a modern front end.
• CI/CD pipeline authoring experience, such as Git Lab CI or similar.
• Familiarity working within agile sprints, code review, and Jira‑based workflows.

• A resilient, trusted Playwright automation suite that catches regressions without brittle, flaky failures.
• Growing API test coverage integrated into Git Lab CI/CD, giving the team fast, reliable signal on every change.
• Effective use of AI tools to widen…