Jsper (jsper.com.au) is a small Australian software studio. We build web and mobile apps, and
lately a lot of AI-heavy stuff. We ship often. We don't enjoy flaky releases, which is the main reason
this role exists.

The job

You're our QA Engineer. Keep our products from breaking in front of customers.

Most weeks that means:

• Writing Playwright tests for the flows we can't afford to break: sign-in, the core product journey, billing, the integrations we lean on.
• Writing API and integration tests against our backend and the third parties we plug into (Stripe, Twilio, Postmark, etc.).
• Poking at multi-tenant edge cases. Org A should never see Org B's data. Roles should do what the UI says. Trial and upgrade paths shouldn't quietly fall apart.
• Filing bugs people can actually reproduce. This sounds boring; it isn't.
• Looking after CI so a red build means something.
• Pairing with engineers on PRs and pushing back when something needs a unit test, not another E2E.

           You won't only write automation. A lot of good QA is still clicking around with intent.

What we're looking for

• A couple of years doing QA or SDET work on a SaaS product you can talk about.
• Comfortable with Playwright. Cypress or Selenium is fine, we'll port it.
• Enough TypeScript that we'd be happy to merge your tests.
• You can read SQL and check whether the database did what the UI claimed it did.
• GitHub and CI experience. Nothing exotic required.
• You write clear bug reports. This matters more than people think.

Bonus points

• You've tested LLM-shaped things before (the "test passed, answer is wrong" problem).
• Some AWS.
• A bit of Python, enough to poke at a pytest suite.
• Load testing, security testing, or browser extension testing.

How we work

• Small team. Whoever joins gets a real say in how QA runs here.
• Trunk-based. Short branches. PRs reviewed quickly.
• Staging multiple times a week, prod most weeks.
• Mostly async. We don't book meetings for things that fit in a Slack message.