Integration architecture at Pon.Bike, data synchronization at Urban Arrow, and product development at ProCC. Explore the work and my role in each team.
Discuss your challengeFrom SAP integrations to mobile apps for greenhouse workers: a selection of the systems I’ve built and the teams I’ve helped lead.
Pon.Bike
Led the data integration team connecting SAP, HubSpot, and internal services. Designed and built a TypeScript microservice architecture to replace parts of an existing monolith, plus a custom gRPC code generator for the team. My role covered technical decisions, code quality, and mentoring.
Urban Arrow
Built the integration between Exact accounting software and HubSpot CRM. Implemented data transformations and business rules for synchronization, with monitoring and error handling to support day-to-day operation. Also worked on API improvements and smaller integration tasks.
ProCC
Led five developers building labor and time registration software for greenhouse horticulture. Worked across PHP and .NET backends, Vue and React web apps, and React Native mobile apps. Built a Deno-based Docker Management Panel for isolated client environments, introduced CI/CD pipelines, and helped move parts of the platform to microservices.
Smidswater
Built client applications in close collaboration with the people using them. Projects included an Electron calculation tool for insurance intermediaries at Nationale Nederlanden and a map-based application displaying air quality data for Airbus Nederland.
Monalyse
Worked in a four-developer team on a media monitoring and brand analysis product. My main focus was a TypeScript drag-and-drop email editor: a browser-based tool for composing, styling, and previewing HTML emails with reusable content blocks.
Schuttelaar & Partners
Started as an intern and grew into a developer role, building client websites, internal tools, and marketing campaigns alongside senior developers. This was the foundation of my full-stack development and client collaboration experience.
Building software professionally since 2013
Lines of code, hours worked, and meeting counts are poor indicators of success. I look at customer value, reliability, developer productivity, and whether the team can sustain the result.
Translate business priorities into architecture and a sequence of decisions the team can understand and execute.
Move comfortably between system design, implementation, reviews, debugging, automation, and production operation.
Use reviews, tooling, documentation, and technical discussion to improve the team’s overall capability—not only today’s feature.
Reduce accidental complexity, clarify ownership, and create systems that remain understandable as requirements evolve.
Technology serves the business. The goal is never to use the newest framework; it is to solve the problem with technology that is reliable, understandable, and appropriate for the context.
Start a conversation