Software Development Engineer in Test (SDET)
Tuesday Health
—
Jul 10, 2026
—
Jul 21, 2026
What this job asks for AI summary
This is the first dedicated test automation role at a remote-first palliative care technology company, responsible for building and owning automated test coverage across a Blazor WebAssembly front end, .NET Core APIs, and a .NET MAUI mobile app. The position involves integrating test suites into CI/CD pipelines, tracking quality metrics, and making heavy use of an AI coding assistant as a core part of daily test authoring and maintenance. It suits an experienced SDET or software engineer with strong C#/.NET skills who is comfortable working independently on a small team.
Senior level · 4+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 5,300 people nationally plausibly meet what this posting asks for (software quality assurance analysts and testers). range 3,200–8,000
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $106,594 (middle half $82,076–$136,109).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (7)
The role is the company's first dedicated SDET, carrying high ownership over the full test automation domain — scope and independence support a Senior classification despite no level word in the title.
15-1252 (Software Developers) is a plausible runner-up: the JD explicitly requires 'production-quality test code' in C#/.NET and positions the role as a peer to developers, blurring the line between SDET and SWE.
AI tooling (Claude / Copilot) is listed under Required with firm language ('Comfort using AI tools … as a core part of your workflow — or strong enthusiasm to adopt them'); it is treated as a hard gate. The 'or strong enthusiasm' qualifier means the specific tool is flexible, so GitHub Copilot is listed as an alternative.
Playwright is listed in the Required section with '(Playwright, Selenium, or similar)' — Selenium is captured as an alternative; the UI automation capability itself is a hard gate.
Blazor, bUnit, Appium, OAuth/OIDC, Azure DevOps (specifically), and healthcare/HIPAA experience all appear under the 'Nice to Have' section and are marked preferred.
No compensation figures are disclosed; the posting references only 'competitive compensation.'
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.