QA Engineer

We're hiring a QA engineer, and there's a wrinkle worth saying out loud: you are also exactly who we build Rebase for. Every decision we make about what a bug report should contain is a guess about someone like you. We'd rather stop guessing.

What you'll do

• Own quality across the widget, the API and the marketing site — three codebases, one product
• Write and maintain the Playwright suites that gate every release
• Break things deliberately, then make the failure reproducible enough that a developer fixes it without asking you a single follow-up question
• Tell us where Rebase itself falls short. You'll have more standing to do that than anyone here

The stack you'd be testing

Three codebases, and you'd have a hand in all of them:

• The widget — Preact with signals, TypeScript, Vite. It runs inside a shadow root on other people's sites, so it has to survive whatever CSS and JS it lands next to
• The API — Laravel on PHP 8.4, Postgres, Redis-backed queues, Stripe via Cashier, Sentry
• The marketing site — Next.js and React
• The suites — Playwright end-to-end, Vitest with Testing Library for components, PHPUnit on the API. All of it runs in GitHub Actions

You don't need to have used every one of these. You do need to be the sort of person who'll happily open a Laravel test and a Preact component in the same afternoon.

What we're looking for

• You've done QA on a real product with real users, and have opinions about what makes a bug report good or useless
• You're comfortable in a browser's devtools — console, network, sources — and you read a stack trace without flinching
• You can write automation, and you know which tests are worth automating and which are not
• You can write clearly. Half this job is making a problem legible to someone who wasn't there

You don't need to have worked at a company our size, and you don't need a computer science degree.

How we hire

There's a question on the application form that you can only answer by spending a minute in our live demo. That's deliberate — we'd rather you saw the product before you decided you wanted to work on it.

After that: a 30-minute call, then a paid half-day working session on a real problem from our backlog. No take-home you do for free, and no whiteboard algorithms.

Working here

We're remote across the UK and Europe. We're small, so you'll have unusual influence over the product and unusual amounts of ownership. That cuts both ways — if you want a large team and a well-worn process, this isn't it yet.