QA Engineer

Someone needs to make sure the thing we ship behaves the way the specification says — before the client finds out, not after. This role writes and runs the tests across every stack we touch. What you’d do…

Someone needs to make sure the thing we ship behaves the way the specification says — before the client finds out, not after. This role writes and runs the tests across every stack we touch.

What you’d do

• Write end-to-end tests for critical client paths (Playwright primary; Cypress or similar for legacy)
• Smoke-test releases across the stacks — a Next.js frontend, a Phoenix API, a Rust CLI tool, a Frappe workflow
• Write test plans in English before any assertion is written in code
• Partner with the engineer and the client, in that order, on what “done” actually means

What we’d expect

• 3+ years in a dedicated QA / SDET role, or 5+ years as an engineer who shipped tests alongside features
• E2E testing fluency — Playwright strongly preferred
• Light scripting across at least two of our languages (reading, not writing production features)
• A patient eye for inconsistency: spacing, copy, state, race conditions, keyboard navigation

Nice to have

• Accessibility testing (WCAG 2.2) experience
• Load/perf testing instincts (k6, Locust, or similar)
• Comfort filing bugs that make the fix obvious to the engineer

How we work

• Not a gatekeeper role — part of the shipping team, with release authority

#J-18808-Ljbffr…