Bjorn Boonen

In addition to my work for various clients, I independently develop several long-term side projects.

These initiatives allow me to explore new technologies, deepen my expertise, and stay sharp by continuously experimenting and innovating.

Responsible for maintaining and enhancing the Bol.com checkout as part of a Kanban team, continuously driving improvements and scalability.

The assignment was to build a Proof of Concept (PoC) to demonstrate that a well-designed user experience (UX) can help reduce contact requests, leading to shorter waiting lists and improved customer satisfaction.

In addition, I played a key role in initiating the development of a Technical Roadmap for the various portals within CIZ.

At Greenchoice.nl, I worked on migrating .NET Razor templates to Nuxt 3. This involved designing and setting up a Proof of Concept (PoC) and defining the front-end architecture.

Together with a multidisciplinary team, I contributed to a renewed front-end architecture for the “Mijn Greenchoice” platform.

In collaboration with UX designers, we created a mobile-first design system using shared design tokens in Figma. This system became the foundation for a new Vue component library, enabling scalable, reusable, and accessible components and tools used both internally at Greenchoice and by external agencies.

I laid the groundwork for this component library and made significant contributions to the development of components that are used company-wide.

Additionally, I focused on improving the developer experience for both front-end and full-stack engineers.

Mentoring and supporting developers was also part of my role. I did this through code reviews (PRs), pair programming, and one-on-one sessions.

Contributed to setting up a Next.js Proof of Concept (PoC) for ANWB Insurance. I was responsible for designing and building the initial flow and configuration for the product wizard.

The project was successfully completed within the predefined three-month timeline. The goal was to demonstrate that a flow built with Next.js would be faster, more stable, and more flexible than the existing solution at the time.

At RH Marine, a large amount of front-end code had been developed in a short time, often at high speed. Due to the involvement of less experienced developers, the codebase lacked clear structure and direction.

To address this, I redefined the front-end architecture and introduced unit testing and TypeScript. In addition, I worked on various screens and contributed to the development of new components.

As part of a Scrum team, I made numerous improvements to the website and was ultimately responsible for the front end. I collaborated closely with the UX designer to refine existing components and design new pages from scratch. Additionally, I led the migration from Razor (.NET) templates to Next.js.

• Responsible for complete front end

• Guiding colleagues

• Prototyping

• Responsible for complete front-end

• Responsible for all (digital) expressions

• Building internal tools for data visualisation

• Supervising colleagues

• Prototyping

• Co-responsible for front end speurdersindekrant.nl

• Developed layout so that De Telegraaf layout also worked on Telegraaf.nl

• Convert design to working code in Escenic CMS

• Guiding colleagues with questions about front end-related tasks

• Creation of digital publications

• Designing pages

• Development of programs to scrape code from websites or insert xml-feeds

• Responsible for the layout of all Compare Group websites