Patrick van Marsbergen

• Kotlin
• Vert.x
• Vue
• TailwindCSS
• Go
• Kubernetes

To provide a modern and scalable hosting for my clients, I've started building Galley in the summer of 2025. Galley is a platform for hosting applications. It's built on top of Kubernetes and provides a simple and intuitive user interface for developers.

For this project, the frontend is build with Vue.js and the backend with Vert.x. The frontend is rendered via the Vert.x Web static handler. The backend is written in Kotlin and uses the Kubernetes API to manage the cluster. I've also started some Go development for a CLI application matching the platform.

• Kotlin
• Vert.x
• Vue
• TailwindCSS
• Gitlab CI
• Docker

The City of Amsterdam took over waste collection from the GAD when the Weesp district became part of the municipality. However, Amsterdam’s Waste Guide is hard to navigate and doesn’t let you add pick-up dates to your calendar. So I took matters into my own hands and built a website that does exactly that.

For this project, I used Vue.js for the first time, rendered via Vert.x Web’s static handler. From the Vert.x backend, I consume several REST APIs provided by the City of Amsterdam.

• Node.js
• React
• Python
• AI
• Github
• Google Cloud

For KLEILOKAAL, my wife's ceramics studio, I designed the brand identity and regularly create new print materials. From posters to cardboard boxes. I do this with various design software. Additionally, I continuously improve her website and the booking module for courses and workshops.

KLEILOKAAL is my wife's ceramics studio. For KLEILOKAAL I designed the brand identity and regularly create new print materials. From posters to cardboard boxes. I do this with Figma and Adobe programs like Illustrator and Indesign.

Additionally, I continuously work on the (further) development of the booking platform with queue system for courses and workshops. This platform is tightly integrated with Shopify as CRM and for handling payments. The platform is developed in Kotlin with Vert.x, uses PostgresDB as database and is deployed via Gitlab CI to Digital Ocean.

• Figma
• Adobe Indesign & Illustrator
• Kotlin / Vert.x
• SSR with Pebble Templates
• Postgres
• Gitlab CI
• Digital Ocean

At Infowijs I started as lead developer with the challenge of taking the system from a simple proof of concept to a stable and scalable platform. I introduced a new way of working, allowing the team to collaborate more efficiently, even remotely. This led to more engagement and better results.

Additionally, I expanded the development team, hired new people and guided them in their work and growth. Through good collaboration and knowledge sharing, we continuously improved the quality of the product and responded faster to market changes.

Together we replaced the old technical system with a modern platform, making everything work better and faster. Finally, I ensured, together with external partners, that costs remained low, while the system stably processed more than 1 million messages per day.

At Infowijs I started as Lead Developer, with the first major challenge being designing a scalable architecture to get the organization out of a constraining MVP phase. Additionally, I implemented a fundamental transformation to a remote agile working method, based on the scrum methodology. This allowed us to collaborate more efficiently and the engagement of the entire team grew, despite the physical distance.

In the following years I focused on expanding the in-house development team. I hired, onboarded and guided new developers, stimulating both their technical knowledge and their personal development. Thanks to this focus on mentorship and knowledge sharing, we succeeded as a team in continuously improving the quality of the product and responding faster and faster to changing market demands.

At Infowijs I introduced, among other things, Kotlin, Vert.x and Postgres to replace the old PHP/MySQL platform. The new microservice platform (running on AWS ECS) connected the new microclients (in React and React Native), where clients and authentication integrated seamlessly with each other.

In my role as Tech lead, I also had intensive collaboration in recent years with external partners, keeping costs structurally low. I am proud of achieving an Infrastructure Cost Ratio (ICR) of ~4.5% despite intensive use of AWS. When I left, 'Hoy' was stably processing over 1 million messages per day – without downtime.

• Kotlin / Vert.x
• PHP
• MySQL
• Postgres
• Mongo
• Redis
• Gitlab CI
• AWS
• React & React Native