Skip to résumé

Senior Infrastructure Engineer · Atom Computing

Infrastructure that engineers can build on

Systems engineer and hands-on builder with experience across an ISP, enterprise infrastructure and long-term client environments. I connect Linux operations, container delivery and repeatable automation with the monitoring, recovery work and direct support needed after a system goes live.

U02

Service history

Technomancy IT LLC · 2015-Present

Founder / Product Engineer / Systems Lead

Own application and infrastructure delivery for client systems, including container-based releases, access controls, SQL migrations, health checks and ongoing support. Build practical deployment and restore-verification tooling around the services I operate.

Deep dive

Through Technomancy IT, I take client work from an incomplete need through implementation, deployment and the support it needs afterward. I build and operate tenant-aware services, authenticated integrations and access controls, alongside the practical work of keeping infrastructure and client systems running. Clients call me directly when they need IT help.

The platform connects application delivery with its operating environment. Documented tooling uses versioned container images, SQL migrations, container health and public HTTP checks, with separate restore verification in a disposable PostgreSQL instance. These are implemented workflow capabilities, not a promise of zero downtime or a claim that every release ran every possible check.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led the NOC and systems work across a multiyear ISP tenure, including lead-engineer responsibility during a company purchase and a later year as sole systems engineer. Migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, upgraded servers and firewalls, and codified infrastructure with Terraform and Ansible. Ran SOC 1 and SOC 2 audits; handled escalations, monitoring, recovery verification and operating procedures.

Deep dive

I worked at FRII for years before the company purchase, and was a lead engineer during that transition. After the senior engineer above me was let go, I was entrusted with sole systems-engineering responsibility for about a year. The NOC continued first-line coverage and escalated unresolved issues to me; I was on call throughout that later period.

I migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, upgraded servers and firewalls, and used Terraform and Ansible for repeatable infrastructure work. I ran the SOC 1 and SOC 2 audits, bringing technical controls, operating procedures and auditor-readable evidence together. The work also included monitoring, infrastructure readiness and recovery verification.

Office Evolution · 2014-2015

Systems / Software Engineer

Built centralized SQL- and MongoDB-backed systems connecting provisioning, onboarding, CRM and service operations across locations.

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 and supported networks and systems across managed-service clients, with remote monitoring, diagnostic tooling and on-call response. Worked directly with business owners and end users, including endpoint support and antivirus services.

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

Operated shared enterprise infrastructure, hosted desktops and virtualization labs; automated audit and backup workflows and coordinated incidents and production changes.

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

Own technical practice and platform

Technomancy IT | Delivery and recovery tooling

Built versioned container-delivery tooling with migration, health and HTTP checks, plus a separate disposable-database restore-verification workflow.

Deep dive

Technomancy IT is both my technical practice and the client-operations platform supporting it. The platform joins support, customer records, scheduling, billing and infrastructure context, while tenant-aware services keep access boundaries clear.

The deployment tooling derives image tags from Git, builds a Linux container image, transfers it for deployment, applies SQL migrations, records image identity and checks container health and public HTTP responses. A separate restore-verification script checks a backup checksum, restores it to a disposable PostgreSQL instance and checks table counts. This is practical release and recovery tooling, not a claim of measured uptime or universal enforcement.

Technomancy IT overview ↗

Technomancy IT client in Wray

Excell Services | Legacy infrastructure modernization

Modernized servers, employee computers and networks, and connected a satellite location with VPN, Windows Server and Active Directory.

Deep dive

Excell Services in Wray was my largest client while I lived and operated Technomancy IT there. I replaced or rebuilt legacy servers and employee computers, upgraded network infrastructure and helped launch a satellite location. VPN connectivity, Windows Server and Active Directory gave corporate users the access they needed.

I stayed responsible for hands-on IT support and also investigated wasted network costs, securing a one-time $15,000 refund from CenturyLink. This was a client engagement through Technomancy IT, not direct employment by Excell, and the satellite location does not imply satellite-internet engineering.

U04

Inventory

  • Linux servers, Windows environments and virtualization
  • Docker, Kubernetes, Terraform and Ansible
  • AWS and Azure infrastructure; networks and access controls
  • CI/CD, GitHub Actions, Python and shell automation
  • Monitoring, recovery verification and on-call operations
U05

Cover note

I call myself a technomancer. Technology has felt like magic to me since I was a kid.

Read full cover letterClose cover letter

Hi Atom Computing team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid. I still love figuring out how the pieces work, but the part I take the most pride in is making a complicated system dependable enough that someone else can get on with their work.

Your infrastructure role brings those two interests together. The quantum computer is a very different kind of machine from the environments I have operated, but the responsibility underneath is familiar: give engineers a reliable place to build, make changes repeatable and understand what happened when something stops behaving. Working alongside engineers and physicists in Boulder sounds like an interesting place to put that experience to use.

At Front Range Internet, I spent years in systems and infrastructure work before the company purchase, and I was a lead engineer during that transition. After that transition, I was entrusted with sole systems-engineering responsibility for about a year. Our NOC handled the first calls and escalated unresolved issues to me. I had earned that trust through the earlier work, and I stayed on call through that period.

The work included upgrading servers and firewalls, moving workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, and making infrastructure work repeatable with Terraform and Ansible. Monitoring, recovery verification and clear operating procedures mattered because I was responsible for the environment after a change, not just the migration itself. I also ran FRII’s SOC 1 and SOC 2 audits, connecting the technical controls with evidence other people could actually follow.

Through Technomancy IT, I have kept building the software and the operating systems around it. My delivery tooling connects versioned container images, SQL migrations, health checks and public HTTP checks. A separate restore-verification workflow checks a backup and restores it into a disposable PostgreSQL instance. I like that kind of practical automation: it makes the next deployment or recovery less dependent on somebody remembering every step.

Linux, containers, infrastructure automation and hands-on systems work are familiar ground for me. I also bring the perspective of building applications myself, so I care about the developer’s path from a change to a running service. I would bring that foundation while learning the specifics of your hardware and scientific environment, rather than pretending that general infrastructure experience is the same as quantum-computing experience.

I’m based in Milliken, and being in Boulder three days a week works for me. I would enjoy helping your team spend more time on the difficult problems you are there to solve, with the systems around them feeling a little more like magic.

Chad