Overview
Matthias Beyens is CTO and co-founder of auditq, a role he has held since September 2025, and is based in Antwerp. Since February 2025 he has also worked as a fractional CTO at Constantly BV. His stated areas of expertise are Python, project management, team management, cloud computing IaaS and technological innovation.
Before that he spent nearly three years at The Janssen Pharmaceutical Companies of Johnson & Johnson, joining as a senior data scientist in April 2022 and serving as principal data scientist from June 2024 until March 2025. He was at BISC Global from October 2018 to April 2022, first as a senior bioinformatics consultant and latterly as development team leader.
Beyens studied at the University of Antwerp, completing a bachelor's degree in biomedical sciences in 2012 and a master's degree in the same field in 2014. From October 2014 to December 2020 he carried out doctoral research as a bioinformatician and biomedician at the university's Center of Medical Genetics, obtaining a PhD in medicine and health sciences. Earlier, in 2013, he worked as a student researcher at the Laboratory of Human Anatomy and Embryology and as a student employee at the Center of Medical Genetics.
Career history
In the news
- What have we gotten ourselves into." 🥸 I thought that most often while pushing code to production during a live client session. Which is exactly as bad an idea as it sounds. I'm not proud of it. I'm telling you anyway, because year one of a company is mostly the parts that don't make the highlight reel, and because it's genuinely behind us: we have a stable platform now. For software that sits between a client and an audit they can't afford to fail, that took twelve months to earn and it's the thing I'd put above any feature we
- Van reactief naar voorspellend kwaliteitsbeheer. Iets wat tot een paar jaar geleden vooral was weggelegd voor grote multinationals, maar vandaag binnen het bereik ligt van elk voedingsbedrijf. Matthias Beyens licht op 27 oktober een tipje van de sluier. Inschrijven kan via de link in de comments.
- Register even if you can't attend live and the recording comes to your inbox.
- 89.5% of the sun disappeared over Antwerp last night. My wife and I watched it in shifts, well... the youngest was crying, so we took turns going outside ("om de beurt"). Neither of us saw all of it. Very on brand for this stage of life, and for this stage of the company. Because building AuditQ feels exactly like that. Weeks of slow movement, and then the moment arrives and you get 90 while the whole team went for 100. Our features could be at 90 right now. Not the full picture we sketched a months ago. And our clients love what is
- We didn't plan for this tbh! 🤓 When we started AuditQ, my architecture assumptions were comfortably European: a handful of standards, a few languages, one regulatory mindset. Then signups started arriving from places we'd never marketed in. That forces good engineering questions fast. How do you build a system that reasons about FSSC 22000 and BRC and a local sectoral guide without hardcoding any of them? How do you keep an AI layer trustworthy when the source documents look completely different per region? We're figuring it out
- Same findings, every audit, regardless of size or sector. When a pattern repeats that consistently, it's no longer noise, it's exactly the load AI should carry, while the judgement stays with people. Proud of what the AuditQ built here, with a foreword from Aldin Hilbrands at Foundation FSSC. Worth a read 👇
Related profiles
This page shows public professional information only, each fact cited. Is this you? send a correction, or ask for removal within 24 hours, no questions asked.