Portfolio
Networks designed and rebuilt, server estates brought under control, satellite links commissioned, tunnels made to work over networks that fight back, and software written to fill the gaps. Client names are withheld; the engineering is described in full.
Each one is written the same way — the problem as it arrived, the judgement calls behind what I did, and what changed as a result. Where a diagram explains the shape of a network faster than a paragraph, there is a diagram.
Remote administration usually costs either a management port published to the internet or a hosted control plane that can change its terms, and the networks you work from fight the tunnel either way.
Production mail, DNS and web have to be reachable from the internet without anything in the building being directly reachable, trusted by large receivers, and recoverable after the machine they run on is gone.
Remote terminals commissioned once and then expected to run unattended, on a path with permanent latency, scarce space segment, weather in the topology and no second route to fail over to.
A multi-site voice platform where the dial plan, not the technology, was what would age badly, and where the call quality complaints traced to the data network rather than to anything anyone calls voice.
A decade of site-by-site growth in three vendors: static routes layered over partial dynamic routing, overlapping address space in two regions, and a core whose second path had been repurposed and never restored.