About Us:
Validaide B.V. is a SaaS company based in the Netherlands serving global pharmaceutical manufacturers and forwarders. Our platform is the world’s global platform for the digitization of so-called Lane Risk Assessments which help our customers ensure compliance with Good Distribution Practice (GDP). Validaide is also a data-sharing platform used by over 1600 logistics companies globally (e.g. Lufthansa, Qatar) to define and share information about their pharma handling capabilities. Validaide is developed in PHP using the Symfony framework with a MySQL database. The organization embraces the Agile mindset and way of working and with regards to software development we have embedded compliance activities into our Agile process to meet customer requirements in that area.
Job Summary:
We are looking for a full-time skilled Test Automation Engineer to join our team, with expertise in Functional Acceptance Testing (FAT) using Behat and PHP. This role focuses on designing, implementing, and managing automated and performant tests to ensure robust validation of software functionality, compliance, and security.
As the Validaide platform is used in a GxP environment, the software and our processes must comply with regulations such as GAMP, FDA 21 CFR Part 11 and EU GMP Annex 11. You will be expected to familiarise yourself with those regulations and ensure compliance. Furthermore you will be involved in developing a User Requirements Specifications (URS) and related Traceability Matrix (TM) to ensure traceability and coverage. You will be expected to obtain a deep understanding of the Validaide software. You will join a team currently consisting of one full-time Test Automation Engineer and a Test Automation Trainee.
We’re a 20-person company, and our agile development team currently consist of seven members with varying levels of experience, including a dedicated test automation engineer. Our mindset towards development is this: we want to optimize our development speed whilst maintaining software quality and reliability. We achieve this with the following mantras: “good over perfect”, “don’t introduce a technology unless it is really needed”, “pragmatic DRY”, “don’t DIY if there are fantastic tools that DIFY (e.g. rector)”, “sometimes you got to write stuff down, dummy (Wiki, e-QMS)”, “integration/smoke tests over unit tests”, “be a {boy/girl/other}scout“, “Bug? Write a test!”, and many more!
A Typical Day:
On a typical day we start with the Daily Standup at 9. On Tuesday’s we do this physically with a mug of coffee or tea in our hands when we are all in the office in Utrecht. During the DS, you bring up a set of 15 automated tests in our test suite that keep on failing randomly. Once we completed our round, you move into a detailed refinement session with our Product Owner and some selected team members. While we refine, you identify a list of tests that need updating or creating for several stories, as well as highlight the need for an update to our software validation plan. After lunch in the office canteen, you move to the priority of the day, which is to analyse and fix those intermittent failures. You do this by partnering with a developer and analysing the cause for the failures. By working together, you quickly identify the issue and stabilize the test suite. The rest of the day is focused on writing new Behat tests for a new feature, and in alignment with your colleagues decide to introduce one new manual test to the release validation activities which is too much work to automate now.
Key Responsibilities:
Qualifications:
Nice-to-have:
What We Offer: