Skip to résumé

Senior Manager IT Infrastructure · Trexon

Infrastructure leadershipClear ownership, dependable systems

Infrastructure and systems leader combining NOC responsibility, multiyear production operations and direct client ownership. Led engineering through organizational change, ran SOC audits and modernized servers, networks and access while keeping support, recovery and business costs in view.

U02

Service history

Technomancy IT LLC · 2015-Present

Founder / Product Engineer / Systems Lead

Own client IT from infrastructure design through deployment and direct support. Coordinate specialist contributions and connect technical decisions with business workflows and operating costs.

Deep dive

My technical practice connects client needs with the infrastructure, applications and support required to keep their businesses working. I choose and operate the delivery approach, bring in specialists where additional craft is useful, and stay available when clients need help.

That ownership crosses networks, access, equipment, software and operational tooling. It calls for understanding the practical consequences of a change and explaining technical choices to the people using and paying for the system. Tenant-aware shared services and authenticated integrations keep client boundaries clear.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led the NOC and infrastructure operations through a multiyear tenure and company purchase; later held sole systems-engineering responsibility for about a year. Modernized workloads and server/firewall infrastructure, and ran SOC 1/SOC 2 audits.

Deep dive

My FRII tenure ran from 2015 to 2020. I ran the NOC, was a lead engineer during the company purchase and later took sole systems-engineering responsibility for approximately a year after the senior engineer above me left. The NOC remained in place for first-line calls and escalated unresolved problems to me; the later sole-engineer period was not my entire tenure.

I migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, upgraded server and firewall infrastructure and worked with monitoring and recovery verification. I ran the SOC 1 and SOC 2 audits, connecting technical controls with documented operating procedures and auditor-readable evidence, and collaborated with the CEO and CIO. These were SOC responsibilities, not a claim of CMMC implementation or certification.

Office Evolution · 2014-2015

Systems / Software Engineer

Connected onboarding, provisioning, CRM and service operations across locations through shared applications. Worked with the CEO and CIO to make cross-department handoffs explicit.

Deep dive

At Office Evolution, I built internal tools that connected CRM, network provisioning, employee onboarding and service operations across locations. SQL and MongoDB supported the applications behind those workflows.

Much of the work was making handoffs between departments explicit in a shared system, so operational work could move through connected applications instead of separate departmental processes. I worked with the CEO and CIO alongside the systems and software engineering work.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered networks, systems and endpoints for managed-service clients. Built diagnostic tooling, provided on-call coverage and worked directly with business owners and end users.

Deep dive

Managed-service work meant moving between different businesses and technical environments while staying close to the people affected by a problem. I built diagnostic and support tooling around recurring issues, provided on-call coverage and sold antivirus services alongside the network and endpoint work.

I worked directly with business owners and end users, connecting the technical investigation with a clear explanation of what needed attention.

IBM · 2010-2012

Infrastructure and Systems Focal

Supported shared enterprise infrastructure and coordinated changes across application, infrastructure and vendor teams. Automated audit/backup workflows and managed virtualization labs.

Deep dive

Shared infrastructure meant a change or incident could cross application teams, infrastructure teams, vendors and business stakeholders. I coordinated that work while operating hosted desktop platforms and virtualization test labs.

I automated audit, backup and compliance workflows, combining hands-on systems work with the repeatable processes needed to support a shared environment.

U03

Systems and projects

Technomancy IT client, Wray, Colorado

Excell Services | Legacy infrastructure and branch connectivity

Replaced or rebuilt legacy servers and employee computers, upgraded networks, and connected a satellite location with VPN, Windows Server and Active Directory. Investigated wasted network costs and secured a one-time $15,000 CenturyLink refund.

Deep dive

Excell Services in Wray was a major Technomancy IT client with a legacy environment that needed more than isolated repairs. I replaced or rebuilt servers and employee computers, upgraded network infrastructure and helped launch a satellite location. VPN connectivity, Windows Server and Active Directory gave corporate users the network access they needed.

I also investigated wasted network costs and secured a one-time $15,000 refund from CenturyLink. The work combined equipment troubleshooting, user access and following through on the service costs around the infrastructure.

Own technical practice and operating platform

Technomancy | Repeatable delivery and recovery

Built deployment tooling around versioned images, migrations, health checks and deployment records, plus a backup restore-verification workflow using a disposable PostgreSQL instance.

Deep dive

Technomancy IT brings support, customer records, billing and infrastructure context together for my technical practice. The product and its operational tooling reflect the same responsibility: deliver the system and stay responsible for supporting it.

The deployment tooling derives image tags from Git, builds and transfers container images, applies migrations, records deployment status and checks container health and public HTTP responses. A separate restore-verification script checks a backup checksum, restores into a disposable PostgreSQL instance and checks table counts. These are implemented workflow capabilities, not a claim that every release or scheduled restore test passed.

Technomancy product overview ↗
U04

Inventory

  • Infrastructure leadership, NOC coverage and incident escalation
  • Networks, VPNs, Windows Server, Active Directory and Microsoft 365
  • Azure/AWS, virtualization and Docker/Kubernetes modernization
  • Recovery verification, operating procedures and SOC 1/SOC 2 audits
  • Vendor troubleshooting, client communication and technical cost review
U05

Cover note

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still love figuring out how to make complicated systems work for people.

Read full cover letterClose cover letter

Hi Trexon team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still love figuring out how to make complicated systems work for people. These days, some of the most satisfying work is the part nobody should have to think about: being able to sign in, reach another location, recover a file and get help from someone who understands the environment.

Your posting caught my attention because it describes infrastructure leadership as making the team and the environment dependable. Across seven businesses, that means knowing what needs attention, making sensible commitments and giving people a clear way to get work done. I have spent much of my career connecting that practical responsibility with hands-on systems engineering.

FRII is the strongest example. I worked there from 2015 to 2020, ran the NOC and was a lead engineer through a company purchase. I had already spent years proving myself there before I was trusted with sole systems-engineering responsibility for about a year after the senior engineer above me left. The NOC continued to handle first-line calls and escalated unresolved issues to me. That experience reinforced how much clear coverage, operating procedures and communication matter when people are depending on the team.

Alongside that responsibility, I migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, upgraded server and firewall infrastructure, and worked on monitoring and recovery verification. I also ran the SOC 1 and SOC 2 audits, turning the technical controls into evidence and procedures people could actually use. I worked with the CEO and CIO through that engineering work. Trexon's focus on sustaining controls as part of normal operations, especially during its integration with Amphenol, feels familiar. My audit background is in SOC work; I would bring that discipline while working carefully with your technical lead and implementation partner on the specific CMMC requirements.

Through Technomancy IT, I have stayed close to the client side of those decisions. Excell Services in Wray was my largest client while I lived and operated there. I modernized legacy servers, employee computers and networks, helped bring a satellite location online, and implemented VPN, Windows Server and Active Directory connectivity for corporate users. Investigating the surrounding network costs also led to a one-time $15,000 refund from CenturyLink. It was a reminder that being responsible for infrastructure includes understanding what the business is paying for.

At Office Evolution, I built shared systems connecting onboarding, provisioning and service operations across locations, working with the CEO and CIO. Earlier managed-services and enterprise work taught me to communicate with everyone from a business owner to application and infrastructure teams. I like making the next step clear, whether that means a technical change, a better procedure or bringing the right people into the problem.

Longmont is local to me. I'd welcome a conversation about where your infrastructure team needs the most support and how I could help make delivery and day-to-day operations more predictable. When people can trust the systems around them and get on with their work, the complicated parts start to feel simple. That's the kind of magic I want to keep building.

Chad