About

I started in field operations, keeping service-provider networks running under pressure — the kind of work where a wrong command at 2 a.m. becomes someone else's outage. Fourteen-plus years later, that instinct for what breaks and why still shapes how I design and change networks.

Somewhere along the way, manually repeating the same provisioning steps stopped being acceptable. I moved toward automation not as a trend to adopt but as a way to make large, complex changes — fabric builds, migrations, validation — repeatable and provably correct instead of dependent on one engineer's memory.

Today, as a Senior Network Consulting Engineer, I work with clients who need that same combination: deep protocol knowledge — BGP, MPLS, EVPN, Segment Routing — to design and implement the network itself, paired with the software engineering discipline to turn that knowledge into infrastructure-as-code, tested pipelines, and runbooks a team can actually operate.