I build the systems and the teams that ship them. Twenty years in distributed systems and cloud, a decade of it inside Australian federal government constraints, most recently leading engineering at a startup building secure communications for enterprise and government — where security and compliance weren't a feature, they were the whole point. I treat security and compliance as design inputs, not paperwork, and I care as much about how a team decides as what it builds.
I've grown an engineering organisation from the ground up: technical architecture, people, and the processes and culture that let both scale sustainably. My day-to-day sits at the intersection of building product and building teams, and I'm most useful when I'm moving between the two — hands-on with architecture and technical strategy one moment, working through team structure, delivery and engineering culture the next.
My background is in distributed systems, cloud infrastructure and DevOps, and a significant part of my career has been spent with federal government clients in Canberra. Working inside strict compliance and security frameworks taught me to design for those constraints from the first decision rather than retrofitting them later, and that discipline tends to make everything else sharper too.
Breadth and depth aren't mutually exclusive. The best engineering leaders need both, and building that range in myself and the people around me is the work I find most rewarding.