I build things. Work is one of the places I do it.

I'm Matt. I build infrastructure, automation, and internal platforms for complex IT environments. For fifteen years, I've done that from inside operations roles: first for a regional services business, now for a national food brokerage.

At the regional business, I built the IT environment from the ground up: networks, servers, identity, business applications, and everything employees used day to day. As the sole IT person, I handled the design, implementation, and ongoing support. When the business acquired two other companies, I brought them onto that foundation while preserving their separate brands.

At the national organization, I drove the consolidation of inherited IT environments onto shared platforms and standards across more than a thousand employees and over eighty locations. That covered identity, computers, networks, phones, security, support, and vendors, with each acquisition brought into the same model. I set the technical direction and built the infrastructure and automation behind it: Microsoft cloud and hybrid systems, centralized support and asset management, employee lifecycle automation, and integrations connecting HR, IT, and business applications. My work also included data pipelines, security assessments, and AI tools for IT operations. As IT Director, I stayed responsible for both the engineering and how those systems ran day to day.

Before IT, I spent a decade in the HVAC trade: dispatch and SLAs, new-build projects, and troubleshooting under time pressure with someone waiting on you. The systems changed; the way I work did not. I still hold the NC mechanical contractors license.

I'm always reading, following questions that interest me, and teaching myself new skills. My home lab, software projects, and workshop give me places to explore those ideas and put them into practice. The same curiosity shows up whether I'm exploring infrastructure, building a sauna or a smart mirror, or writing a piece of software.

Volleyball started as a pickup group with just enough people for two teams. I built it into a business with four seasons a year, 150–200 players a season, contractors, real operations, and the software I wrote to run it. It is still the social thing it began as, which is why I still run it.

The thread through all of it is the same: I like making systems work better together, whether they were designed to connect or need a bridge between them. It does not much matter whether those systems are two cloud tenants, a league and its scheduling software, or a pile of lumber and a plan. Give me a problem with real constraints and I'll go find out how it works. If you're not sure where to start, I'll find the place to begin.