QA (automation) engineer - end to end

** Whilst we welcome candidates from all over the world, we can only proceed to interview candidates who are currently living within reasonable commuting distance to de Lier. If you are not already living in the Netherlands, we cannot unfortunately consider you.** About Priva In the middle of Het Westland, where innovation in food and flowers has been thriving for decades, Priva builds technology that keeps greenhouses growing and buildings breathing. We create intelligent control systems that help customers operate sustainable, reliable environments. Why this role matters Our platform capabilities span multiple services and teams. Individual components can pass their own tests while a customer journey still fails at an interface, in shared data, during deployment or under realistic operating conditions. This role closes that gap. • Establish a coherent end-to-end quality approach across the platform capabilities owned by Teams Mobius and Rangers. • Unify and improve existing integration and system-level test approaches instead of creating another isolated test suite. • Give product teams practical tooling and guidance so their components can participate in complete platform journeys. • Turn production risks, incidents and cross-team dependencies into repeatable tests and stronger release evidence. Your teams You will work across Team Mobius and Team Rangers. Mobius owns data-platform capabilities, including master and historical data services. Rangers owns cloud services including remote data communication. You will collaborate closely with engineers, QA colleagues, Product, architects, application teams and support specialists. What you'll do • Create and maintain a platform-level end-to-end test strategy covering critical customer and operational journeys across services. • Map system boundaries, dependencies, data flows and failure modes, then translate the highest risks into executable test scenarios. • Build and maintain automated tests that exercise real service interfaces and representative environments. • Bring existing team-level test frameworks and suites into a coherent approach, reusing what works and removing unnecessary duplication. • Define test data, environment, identity and dependency-management patterns that make cross-service tests repeatable and diagnosable. • Integrate smoke, regression and end-to-end suites into CI/CD pipelines with useful reporting and clear ownership of failures. • Coordinate cross-team test preparation for changes that affect multiple services, consumers or production environments. • Use telemetry, logs, traces and test evidence to diagnose failures and distinguish product defects from environment or data issues. • Assess release risk, communicate residual risk clearly and help teams make evidence-based release decisions. • Coach engineers and QA colleagues in testability, system-level thinking and effective automation.