Subscriptions Service

Holland & Barrett
Tech used: React, Express, Next.js, Rest APIs, TypeScript, Redux, Node.js, Jest, Cypress



I joined Holland & Barrett during the early stages of a digital transformation process in 2020. As part of this transition, we were rebuilding the customer-facing front-end using React-based micro-frontends, that communicate with a mix of new and legacy backend services.
Up until this point, Holland & Barrett have used a third-party provider for their subscriptions service. When I joined the team I had been tasked to reimagine the front-end for subscriptions and worked within a cross-functional squad of back-end engineers and a UX designer to rebuild this service end-to-end.
This case study is protected, please get in contact with me to read the full case study.