I've always had a role that allows me to bridge the gap between disciplines. At uni, I chose to study artificial intelligence (AI) because its curriculum was the most flexible, spanning IT, linguistics and neuroscience. I've been involved in everything from requirements engineering and modelling, solution/software architecture, product/portfolio management, supporting sales and business development relations with academia and even producing a podcast. In my spare time, I also like to listen to podcasts (let's exchange recommendations!). I love to get my teeth into new subject matter, and have done previous projects in mortgages, insurance, government, and more. Coming up with new solutions, original insights and sharing knowledge are powerful motivators to me.Business engineering is not a clearly defined term, but to me, it's a clear vision of empowering knowledge workers and policy makers to be maximally involved in the creation of the software and business processes that shape their working lives. We've all seen departments that have an elaborate web of manual processes and Excel sheets to work around IT systems that are not flexible or intelligent enough. If you want to change that, and if you want to enable organizations to truly digitise, lower failure costs and leverage compliance-by-design, we should have coffee.