About the role
You’ll own quality across one or two client engagements at a time — typically web apps with backing APIs, sometimes mobile. We don’t see QA as the “bug catchers at the end of the pipeline”; we expect you to shape acceptance criteria, push back on under-specified features, and partner with engineers from sprint planning onwards.
You’ll have full input on tooling. If our current stack doesn’t fit the engagement, we change the stack — not the engineer.
How we hire
One intro call → a paid scenario take-home (real bug-triage + test-plan exercise) → a 60-minute working session on your submission → an offer. About two weeks end to end.
What you'll do
- Define the test strategy for client engagements — risk-based, not exhaustive checkboxing.
- Build and maintain automated test suites (UI + API) that run in CI on every pull request.
- Run exploratory and regression test passes before each production release.
- Triage defects from production and pre-production environments and write the regression test that catches them next time.
- Pair with engineers on shift-left practices — testability, observability, and acceptance criteria upfront.
What we're looking for
- 3–6 years of professional QA experience, with at least 2 years writing automation in a mainstream framework (Playwright, Cypress, Selenium).
- Strong API-testing chops — Postman or equivalent, and you can write tests directly in code.
- Comfortable writing SQL — you can query the DB to verify test data and reproduce defects.
- Solid grasp of the defect lifecycle, severity vs. priority, and how to write a bug report engineers don't push back on.
- Real Agile / Scrum experience — sprint planning, refinement, retros aren't new to you.
Nice to have
- Performance / load testing with k6, JMeter, or Locust.
- Mobile-app testing (iOS / Android) — manual or with Appium / Detox.
- Security testing fundamentals — OWASP Top 10, basic threat modeling.
- Accessibility testing — WCAG, axe-core, screen-reader passes.