Covering a super fund's member portal
One month of cover became five
At a glance
A superannuation fund’s member portal team needed front-end cover. I joined for one month, and the fund extended the contract each month to five. I released two member journeys and built the platform’s first automated deployment pipeline.
The situation
The fund’s member portal team needed front-end cover. I joined for one month.
The fund extended the contract each month, to five months in total. For part of that time I also covered the Innovation Manager role.
The fund is APRA-regulated, so changes had to meet strict quality and release controls. Releases were manual and usually happened once a month.
What I did
- I released two member journeys, for withdrawals and pension sign-up, from design to production.
- I built the first automated deployment pipeline for the platform. It replaces the manual monthly release.
- I improved code quality. I added Prettier and Stylelint and upgraded the build tools. I found the Sass changes needed before Dart Sass 3.0, and wrote technical spikes.
- I helped hire a permanent front-end engineer and onboarded them in person.
The result
- Two member journeys went live.
- The platform ran with no unplanned outages during the cover period.
- The team has an automated deployment pipeline and a permanent front-end engineer.
Stack
React and TypeScript, with Sass for styles. Figma for design handover. Azure DevOps for code, pipelines and work tracking.
Need something similar?
Tell me about your project and when you need someone.