QA Engineer

About Shiftbase

At Shiftbase, we build workforce software that helps people get work done. Thousands of teams across Europe use our platform every day to plan shifts, track time, and manage leave, with less admin in the way.

Our engineering team is 18 people from a mix of backgrounds. The culture is open. Anyone can push back on an idea regardless of title.

Why this role exists now

We develop AI-assisted, with Claude Code as our primary tool, and a growing share of our code starts that way. Human review and engineers owning what they ship keep it safe. Testing is the piece that hasn't caught up, and that makes it the most interesting engineering problem here right now. Nobody has a settled playbook for quality in AI-assisted development, and you'd help write ours.

This year the whole team moves to continuous deployment, releasing automatically on every change that passes our checks. That only works if the tests are trustworthy. Our web end-to-end coverage is solid and already replaced manual web regression. Mobile still rides on a multi-day manual regression, only engineers can author tests, and we haven't mapped the gaps.

About the role

You're the engineer who makes our test automation good enough to release on. You build, stabilise, and extend the suites, with mobile as your first big target, and you help the people around you get better at testing while you do it.

You work alongside our QA engineers and partner with the development teams driving the wider move to continuous deployment. Each QA engineer works with dedicated development teams.

Year one, in order

• First, kill the manual mobile regression. It costs us multiple hours on every mobile release and it's the biggest blocker to continuous deployment. This is your first big deliverable.

• Then, make the end-to-end suite a trusted merge gate. Stable, fast, and with a false-failure rate low enough that nobody argues with a red build.

• Along the way, put test authoring in more hands. You build the setup and do the pairing so QA testers write their end-to-end tests with AI and developers keep tests as part of their normal flow.

What you'll do

• Build out mobile test automation and retire the manual regression as a release gate

• Map where coverage is strong and where it's thin, then close the gaps that matter most for shipping safely.

• Make the framework and tooling approachable enough that QA testers and developers author tests themselves, then pair with them until they do.

• Track flakiness, coverage, escaped defects, and cycle time so we can see whether the suite is getting more trustworthy.

• Feed what you learn into the testing workflow for continuous deployment.

How we work

Backend in PHP, frontend in Angular, a web app and a mobile app. End-to-end tests run in Playwright & Maestro. We develop AI-assisted with Claude Code. CI already runs linters, unit tests, end-to-end tests, and SonarQube, and we're hardening these into enforced merge gates.

Must-haves

• You've made a suite trustworthy at scale. You built or stabilised end-to-end and integration suites that a team relied on to gate merges or releases, and you know the work that took.

• You work in the codebase as a peer. You read and write code alongside developers and reason about APIs, data, and integration points, not only the UI.

• You make others better. You pair, review, and explain well enough that people around you level up, without needing a title to be heard.

• Ideally you've built mobile test automation before. If not, show us you've stood up automation on an unfamiliar platform and made it stick, fast.

Nice-to-haves

• You've been part of a team's move to frequent or fully automated releases

• Experience working alongside AI-assisted development

• Familiarity with a complex, regulated domain (ours covers scheduling, time tracking, leave, and labour law across countries)

This might be your dream job if…

✅ You want to take a strong test suite the last mile to continuous deployment

✅ You get energy from getting developers to own quality, not from being the gatekeeper

✅ You like working in the codebase yourself, not only writing test plans

✅ You believe automated testing should let a team move faster, not slow it down

This probably isn't your dream job if…

⛔️ You prefer manual testing and writing test cases over building automation

⛔️ You want to be the last line of defence catching bugs by hand

⛔️ You'd rather work in isolation from developers than embed quality into how they work

⛔️ You need the tooling and process handed to you fully decided

You'll need the right to work in the Netherlands. We can sponsor visas for this role, and you'll need to be at our Zoetermeer office on hybrid days. We are not open to relocators.