Which?
When I first joined Which, I was in a team looking after the CMS system called Glide and I also extensively worked on a design system (using Storybook) to create a collection of flexible and reusable components that could be used across all the different areas of the business. The engineering team slowly adopted the squad model and I've been lucky to work in four different squads, acquisition, content experience & discovery, content experience (the previous squad was split into two as it was very large) and now I am a Product Engineer in the Which? Core squad.
Within the acquisition squad, I was the sole developer, we investigated how we could gain & retain users and introduced improvements to the sign-up journey. Within my current squad (we absorbed quite a few areas from the previous two squads I was in), we look after over thirty different domains such as Glide, the article templates, news, global navigation, saved/favorites (this is as new domain that we have been working on) and static tools. We also keep a keen eye on issues and performance monitoring by using several tools such as Airbrake, Calibre & Lighthouse to name a few. At Which I'm the go to person for static tools, I believe this is quite a achievement as the math required to give the correct calculations can be quite complex especially with the finance and mortgage tools.
Software, skills & technology used:
Most recent achievements:
Decreased average page size by 52% via code-splitting, using responsive imagery, removing redundant code, updating/removing npm packages etc
Provided all the responsive styling and tracking for the new global navigation menu (also decreased the bundle size by 40% (CSS) and 30% (JS)
Completely rebuilt most of the mortgage calculators, these receive traffic in the thousands and can reach well over a hundred thousand users after a government budget refresh
Interviewed and provided feedback to the engineering manager on multiple candidates
