Skip to content

Planned and implemented new infrastructure functionality for internal and external systems, building solutions durable enough to still run years later with minimal change.

Infrastructure Engineer

Situation. As the organisation grew, its internal and external systems kept needing new capabilities bolted on. The easy way to do that is whatever’s quickest today; the trouble with the easy way is you’re back fixing it in six months.

Task. Planning and building infrastructure functionality that would actually last was the task — not just work now, but keep working.

Action. New infrastructure functionality was planned and implemented across the internal and external systems, designed to be durable — the kind of thing you build once, properly, so it keeps running for years with minimal touching rather than needing constant attention. That’s a deliberate choice each time: spend a bit more thought up front so you’re not signing yourself up to babysit it forever.

Result. The systems stayed functional and effective long after they were built, running for years with barely any change. That longevity is the real measure of infrastructure work — anyone can make something that works today; making something that’s still quietly working years later is the harder and more useful thing.