About
Independent infrastructure engineering, based in Pittsburgh
Fifteen years of building, securing and repairing the enterprise infrastructure businesses run on.
Background
I work as an independent infrastructure engineer from the Coraopolis area, serving businesses across Greater Pittsburgh. My focus is the core systems that a company cannot operate without: directory services, mail, servers, virtualization hosts, Linux services, networks and the endpoints that connect to them.
Across more than fifteen years I have worked on both sides of the discipline. I have planned and executed migrations in structured enterprise environments, and I have spent plenty of time in server rooms replacing failed hardware and tracing cabling. Both matter. Good design that nobody can maintain is not useful, and field work without an architectural plan just moves problems around.
My core expertise is Microsoft infrastructure, but very few real networks are a single platform. I also build and maintain the Linux systems that support modern enterprise environments — reverse proxies, VPN gateways, mail relays, DNS, web services and virtualization hosts. Being comfortable on both sides means I can engineer a complete environment instead of handing off at the boundary.
Working independently means clients deal with me directly. There is no dispatcher, no tiered escalation path, and no handover between technicians who have never seen the environment. For small and mid-sized organisations that generally produces faster resolution and much better continuity.
Selected work
- Compromised Exchange environment recovered to full service. Contained the incident, rebuilt trust in the mail platform, closed the access path that allowed it, and returned the organisation to normal operation with mail history intact.
- 200+ mailbox migration with zero downtime. Planned and staged the cutover so users continued sending and receiving throughout, with no loss of calendar or contact data.
- Active Directory and Group Policy consolidation. Replaced accumulated ad-hoc policy with a documented, intentional structure that is straightforward to audit.
- Virtualization consolidation. Migrated ageing physical servers onto properly sized VMware and Hyper-V hosts, reducing hardware footprint and simplifying recovery.
- Segmented networks with secure remote access. Meraki-based deployments with VLAN separation and WireGuard or OpenVPN access for staff and vendors.
- Linux edge and application services. HAProxy reverse proxies, WireGuard gateways, Postfix relays and DNS running on hardened Linux hosts alongside existing Windows infrastructure.
How I work
Most engagements start with a short conversation about what is currently breaking or what you are trying to change. From there I will usually want to look at the environment before recommending anything, because infrastructure advice given without seeing the actual configuration tends to be wrong.
I document what I build. That means when I hand something over, or when you bring in someone else later, the configuration is written down rather than living only in one person’s memory. Engagements can be project-based, retained for ongoing maintenance, or purely as-needed.
Availability
Available onsite across Pittsburgh and the surrounding region, or remotely for work that does not require physical presence. Scheduled maintenance outside business hours is normal and expected for anything that affects production systems.