Software Engineer in Test at PDQ
—
Jul 1, 2026
—
Jul 21, 2026
What this job asks for AI summary
A software engineer in test role embedded within an agile delivery team, focused on building and maintaining automated test frameworks and pipelines for device management software. Day-to-day work spans end-to-end, unit, integration, and performance testing across both a SaaS product and on-premises applications, using a stack that includes Elixir, Rust, JavaScript, TypeScript, and PowerShell. Suits engineers with solid test automation experience who are comfortable owning quality across the full development lifecycle.
Mid level · 3+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
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 8,800 people nationally plausibly meet what this posting asks for (software quality assurance analysts and testers). range 5,300–15,900
Applicant volume Heavy — This req sits in a large pool with little in its requirements to thin it, and auto-apply tools fire at everything in the occupation. Applying early and leading with the rare skills below is what gets read.
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 title 'Software Engineer in Test' carries no explicit seniority level word, so the title states no level. The requirements (3+ years of programming experience, 2+ years of E2E tooling, independent ownership with some ambiguity) support a Mid-level classification.
The programming-language requirement is stated as 'Must Have' but is deliberately open-ended: Elixir, Rust, JavaScript, TypeScript, and PowerShell are the preferred stack languages, with Python, Go, and Java listed as acceptable alternatives. Elixir is used as the primary skill name to represent the stack requirement, with all named alternatives captured accordingly.
The 2-year E2E framework requirement names Cypress, Playwright, and WebdriverIO as interchangeable options; Jest and React Testing Library are similarly interchangeable for unit/component testing.
Advanced testing practices (load/performance, visual validation, security, accessibility, chaos testing) and familiarity with on-premises device management appear under the 'Nice to Have' section.
TypeScript, PowerShell, and Rust are also called out individually as preferred stack languages and are listed as preferred skills to surface their relevance to the team's day-to-day work.
No compensation figures are provided in the posting.
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.