Nineteen years of technical ownership of the core network for a consolidated city-county government — 220-plus locations, 1,100-plus network devices, two data centers, and every service in this record riding on top of it.
The title on the door changed over that period. What did not change was that the core was led here: its architecture, its standards, the platform decisions and the escalation that arrives when something on it is not behaving.
The go-to
Across the whole tenure, and regardless of the role held at the time, this was the person the organization came to when a system misbehaved and nobody could say why. Not only the network — any of the systems.
That is worth recording because it is the part a title conceals. An org chart showing Chief Technology Officer implies somebody who stopped touching equipment years earlier, and the reality was the opposite: the escalation path for a hard problem ended here for nineteen years. Architecture written by someone who has not troubleshot the estate in a decade drifts from what the estate actually does, and the way to prevent that is to keep taking the call.
Outcome
One core, one design language, and one person accountable for it across two decades of platform change.