Senior QA Specialist

Job description

About us Rentman is a B2B SaaS scale-up building a smart, powerful operations management platform to support event and media production teams. Our users plan everything from small shoots to massive festivals in 70+ countries, and they all rely on Rentman to keep their gear, people, and timing perfectly in sync. We’re based in Utrecht (NL) with a second office in Toronto (CA), and our 100+ team members work in a culture that’s open, flat, and inclusive, where curiosity drives us, ownership matters, and everyone has the freedom to challenge ideas and make an impact. Check out our public roadmap to see what’s coming next! Mission of this role Thousands of rental companies run their business on Rentman, and many of them depend on it talking smoothly to the rest of their stack: accounting packages, webshops, calendars, and our public API. When an integration breaks, invoices don’t sync, bookings go missing, and customers notice fast. As Senior QA Specialist for the Integrations team, you make sure every release reaches those customers without regressions. You own the team’s test strategy and lead the move from manual release-day testing to an automated, shift-left suite. This is a role with real ownership: you shape how the team thinks about quality, and you grow the practice as our integrations platform grows. What you'll do Join refinement with the Integrations team and write Gherkin (Given/When/Then) acceptance specs that developers turn into tests Test new integrations and API changes end to end: our side, the partner’s side, and everything that can go wrong between them (auth, rate limits, partial syncs, retries, data mapping) Explore beyond the acceptance criteria to find edge cases, and file clear, reproducible bug reports in Jira Build and maintain automated tests in TypeScript, with API and contract tests alongside Playwright E2E tests, and review the tests developers write in pull requests Own the daily automated regression run in GitHub Actions: triage failures the same day and fix flaky tests at the root cause, including ones caused by unreliable third-party sandboxes Run release-day regression and the OWASP ZAP security scan, and give a clear go / no-go call Migrate the remaining legacy tests and decide what’s worth automating and what stays manual Coach developers so they own their tests, and organise QA days with the other product teams What we ar…