Engineer — API and front end, continuously
TIMSAN — two years running one organisation's platform
Problem
A national student organisation needed a system that outlasts the executives who commissioned it — membership, events and communication that still work after everyone involved has handed over.
What I built
Most portfolios show launches. Launches are the easy part.
This is a platform for a national student organisation, and I have been maintaining it for over two years — through leadership changes, through a full front-end rebuild against the same API, through the ordinary accumulation of things that need fixing because real people use them.
The API has outlived its first front end, which is the useful test of whether the boundary was drawn in the right place. When the interface was rebuilt in 2026, the API largely did not have to change — the contract was about what the organisation needed to do, not about what the first set of screens happened to show.
There is no dramatic story here. That is the point: sustained, unexciting ownership of something that has to keep working is a different skill from shipping a first version, and it is harder to fake.
Result
Over two years of continuous ownership across the API and front end. The least glamorous entry here and, for anyone deciding whether to trust me with something that has to keep working, probably the most relevant.