Three industries, one problem. Built the function from nothing twice and stayed to run each: five years at a multi-site card processor, then nearly five years as a legal services nonprofit's sole IT professional. Today that scope is IT, security and DevOps for 300 employees and a 1,400+ site production fleet.
Card processing, legal services and marketing technology look nothing alike from the outside. From the inside they arrived the same way: growing fast, sitting on data that could not afford a bad day, and running without anybody who owned the technology end to end. Twice the function did not exist at all and had to be built from nothing, and both times the job carried on for years after the build.
Arrived at a multi-site card processor with no compliance program in place. Built and ran the company technology environment for five years inside a $500K-a-year estate.
Led the first PCI DSS Level 1 service provider certification and project managed the SOC 2 Type II obtained in 2016. Carried growth from 75 to 150 users and 6 to 8 operating sites.
First technology leader the organization ever had. Ran the entire IT function single-handed for 150 employees, 250 endpoints and 100 tickets a month.
Built its first security architecture and access controls, led a full on-premise to cloud migration, and cut operating cost from about $500K to $420K. Documented the environment to a standard that survived transition to an outside provider.
Own IT, security and DevOps for 300 employees, 354 managed endpoints and a 1,400+ site client hosting fleet at a $15M+ revenue company.
Hold final architecture authority for the fleet security and operations tooling layer, approve about $1M in annual technology spend, and lead four engineers across the US and India.
Every square below is one site in the production fleet. In one incident, 130 of them were hit at once. What follows is how that ran and what got built afterward so it did not run twice.
A malware outbreak hit 130 sites inside the fleet. Detection ran off a malware signature list built from our own incident forensics rather than vendor defaults, so the sweep matched what was actually running in the environment. Fleet malware remediation itself runs through one of three AI agents shipped into production.
Corporate IT, the security program and the DevOps layer, plus the budget that funds all three. Final architecture authority for the fleet security and operations tooling layer sits here too.
Owning the budget only matters if the number changes. Each of these was a call made, funded and measured afterward.
Based in Greater Pittsburgh, PA and working remotely. Open to IT, security, technology operations and DevOps leadership across industries where the data matters and the function needs building or rebuilding.