@page What I Do
Bridging engineers, operations, and the people who need it to just work.
My work sits across software engineering, infrastructure, cloud architecture, DevOps, and enterprise architecture, with engineering leadership tying it together. Day to day, that means moving between developers writing the platform, operations teams running it, and stakeholders who need it explained without the jargon.
Part of the team recognised with Broadcom's Innovation Award for the private cloud IaaS platform I've worked on since its 2013 launch - industry recognition for continuous engineering on a single platform, not a one-off project.
How I architect
- Thinking at an enterprise-architecture level: standards, non-functional requirements, and the platform as a whole, not just the next delivery.
- Applying a TOGAF-formalised approach within the guardrails of our Unified Architecture Board.
- Proposing systems that solve problems stakeholders hadn't realised they had yet, built on years of pattern-recognition across the business.
- Diagnosing root cause over symptoms, so the engineers closest to a problem can find the right fix.
How I lead
- Enabling engineers rather than micromanaging them.
- Making complicated technology understandable to the people who rely on it.
- Building trust through competence and honesty, not confidence alone.
- Mentoring engineers and tech leads, having been mentored myself.
- Favouring automation over repetitive manual work.
- Choosing long-term maintainability over quick fixes.
- Staying calm during incidents, and leading by example when it matters most.
Technical areas
Where this is heading
Agentic development is already part of how I work: GitHub Copilot for architecture discovery and planning, and Copilot alongside Claude Code for the development itself, this site included. The next stage is scaling that beyond my own workflow, iterating on how these tools fit into a team's ways of working, and using them to accelerate delivery without cutting corners on architecture.