Verken carrière kansen bij Interchemie

Your Russian opens the border. The scientist in you gets the medicine across. At Interchemie, you register veterinary medicines in the CIS countries, where a registration moves faster with someone who speaks the language. You learn the profession step by step, in a team that welcomes you and challenges you. You work in pharma: in the lab, in QA, in QC or in a pharmacy. You speak Russian. Ready for the next step? Read on.

You know what it takes to get a medicine right. In Regulatory Affairs at Interchemie, you take it one step further: you make sure it reaches the animals that need it. Your countries, your dossiers, from first registration to renewal. Every approval you get opens a market and gets veterinary medicines to animals that need them. You do this in a team that works entirely in English. Dutch is not required.

Directly in the workforce with prospects of permanent employment. Two shifts, no night work. Salary between €2,615, - and €3,166, - gross per month excluding shift allowance. Pension scheme with employer contribution up to 26%, 25 vacation days and 8.25% vacation bonus. Travel expenses reimbursement of €0.23 per km. Your team leader is on the floor next to you and is there to help you. You know what a production line requires. You run your own line; you are the point of contact and you fill in the logbooks because you want to...

Tired of working on just one small part of the regulatory process? At Interchemie, it’s different. As a Regulatory Affairs Specialist, you manage regulatory dossiers from A to Z and are involved in the entire lifecycle of a product, across international markets. Unlike many Regulatory Affairs positions in the Netherlands, this role does not require Dutch. The entire RA team works in English.

As a validation engineer, you are usually just one link in a long chain: you validate your part, someone else does the rest. At Interchemie, that’s different. Here, you get the complete process validation, from the production lines to the cleaning processes, and you build the validation documentation largely yourself. You figure out why a process does what it does, show whether it always gives the same result, and fix what’s not working. Does that sound like your challenge?