Skip to résumé

Cloud Systems Administrator I/II/III · Adams County

Keep services running. Make the next fix easier.

Systems engineer and hands-on IT practice owner with enterprise infrastructure experience at IBM, NOC leadership at FRII and ongoing client operations. I work across Windows Server, Linux, virtualization and cloud services, connecting access, deployment and recovery to the people relying on them. AWS is my deepest cloud background; I also bring over five years of Azure client work.

U02

Service history

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client systems from initial setup through production support and on-call troubleshooting. Implement Microsoft Entra ID, AWS IAM, SAML/SCIM and application authentication workflows with explicit access boundaries. Modernize client environments and build repeatable deployment and recovery tooling. Bring application, data and infrastructure context together instead of handing a cross-system problem back to another team.

Deep dive

My practice combines production software and client IT responsibility. Identity work includes OAuth/OIDC, PKCE, token exchange, workload identities and secrets. For Excell Services LLC in Wray, I implemented Windows Server, Active Directory and VPN connectivity as part of legacy-server, endpoint and network modernization. AWS is my most hands-on cloud; Azure work spans more than five years across client engagements. My Intune exposure is limited.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led the NOC, monitoring, recovery verification and engineering escalations across hosted infrastructure. After years at FRII, held sole systems-engineering responsibility for about a year during its ownership transition, with NOC first-line coverage continuing. Migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, performed smaller server/firewall upgrades and ran SOC 1 and SOC 2 audits. Built tools and procedures for operators and hosting customers.

Deep dive

NOC first-line support continued during my later sole-engineer period; that year was only part of my 2015–2020 tenure. I maintained aging servers, including component repairs, alongside smaller upgrades and workload migrations. A later full server-replacement plan was not funded or implemented. Audit ownership meant translating controls into evidence and SOPs, not simply listing a standard.

Office Evolution · 2014-2015

Systems / Software Engineer

Supported architecture across locations and client environments, building centralized applications for CRM, provisioning, onboarding and service operations. Worked with the CEO and CIO and turned cross-department handoffs into explicit shared workflows, connecting business needs to technical implementation.

Deep dive

Centralized CRM, provisioning, onboarding and service applications linked departments and locations. I supported the architecture behind those handoffs and worked directly with the CEO and CIO on the operational needs.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered and supported networks, systems and endpoints across managed-service clients, including remote monitoring, on-call diagnosis and antivirus services. Built diagnostic and support tools for recurring issues and communicated directly with business owners and end users through troubleshooting and recovery.

Deep dive

Everon was broad managed-service work with direct customer responsibility. Monitoring and repeatable diagnostics supported network and endpoint troubleshooting, and I was part of on-call support. Network & Systems Engineer describes that scope; the employer-used title was Network Engineer.

IBM · 2010-2012

Infrastructure and Systems Focal

Served as infrastructure focal for shared enterprise services, coordinating access, change, incidents and escalations across application, infrastructure, vendor and business teams. Automated audit, backup and compliance workflows; managed virtualization test labs and hosted desktops, with the coordination required when many teams depend on the same systems.

Deep dive

Shared enterprise infrastructure meant coordinating tenancy, access, changes and incidents across teams. My work included virtualization test labs, hosted desktops and automation around audit, backup and compliance workflows. I carried that habit of repeatable operations into later systems and client work.

U03

Systems and projects

Front Range Internet Inc. · 2015–2020

Modernizing without losing operations

Migrated hosted workloads from Hyper-V and VMware ESXi into Docker and Kubernetes while maintaining infrastructure operations. Smaller server and firewall upgrades, NOC tooling and recovery verification connected modernization to the day-to-day work of supporting customers.

Deep dive

The environment included aging hardware that sometimes needed component-level repair. I ran engineering escalations and built tools for NOC teams and hosting/colocation customers. The later full hardware replacement remained an unfunded plan, separate from completed migrations and smaller upgrades.

Excell Services LLC · Technomancy IT client

Giving a legacy business reliable access

Modernized legacy servers, employee computers and networks for a Wray business. Implemented Windows Server, Active Directory and VPN connectivity, including support for a satellite location, so corporate users had the access they needed.

Deep dive

Excell was a substantial client of my Technomancy IT practice, not a separate employer. The work combined server and endpoint replacement, network upgrades and continuing support. I also identified wasted network costs and secured a one-time $15,000 CenturyLink refund.

Technomancy IT · own practice

Delivery with a recovery path

Built deployment tooling with Git-derived image tags, SQL migrations, container-health and public-HTTP checks. A separate backup-verification script checks a checksum and restores PostgreSQL into a disposable instance to inspect table counts, making recovery something the tooling can exercise.

Deep dive

The support platform joins tickets, CRM, billing and infrastructure context using tenant-aware services. Its deployment script records image identity and status and retains prior images within a bounded cleanup scope.

Platform overview ↗

ProofMark · completed client contribution

Keeping identity and workflow connected

Designed document signing across identity, routing, verification and audit history. Explicit security-sensitive state and fallback paths connect the user workflow to its APIs and data, experience useful when diagnosing problems that cross service boundaries.

Deep dive

My completed client contribution includes document/PDF fields, encryption, webhooks and embedded signing in an AGPL/open-source product. It joins UI, APIs, PostgreSQL data and verification workflows.

ProofMark website ↗
U04

Inventory

  • Windows Server, Linux, Active Directory and Microsoft Entra ID
  • Azure client administration, AWS IAM and hybrid infrastructure
  • VMware ESXi, Hyper-V, Docker and Kubernetes
  • PowerShell, Bash, monitoring, backup and recovery
  • Access hardening and audit support; CompTIA A+ and Network+ (earned)
U05

Cover note

I like making complicated systems dependable for the people who use them. Adams County’s mix of cloud services, hands-on infrastructure and public service feels like a natural place to bring that experience.

Read full cover letterClose cover letter

Hi Adams County ITi team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, but the part I care about most now is making it dependable for someone else. A working account, a recovered service or a tool that saves the support team another manual step can make a real difference to their day.

Your Cloud Systems Administrator role brings together the work I have spent years doing: keeping infrastructure running, understanding the access and application layers around it, and helping the next person resolve a problem. I like that your ITi department connects platforms, service operations and security instead of treating them as unrelated responsibilities. In county work, those handoffs ultimately affect people trying to get help or use a public service.

At FRII, I led the NOC and handled infrastructure monitoring, recovery verification and engineering escalations. I had already worked there for years when the ownership transition left me with sole systems-engineering responsibility for about a year, with the NOC continuing first-line coverage. Alongside that operational work, I migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, built tools for operators and hosting customers, and ran the SOC 1 and SOC 2 audits. Keeping an aging environment useful taught me to distinguish what needed replacing from what needed a careful repair, a better procedure or a clearer diagnosis.

Through Technomancy IT, I take that responsibility into client environments. For Excell Services LLC in Wray, I modernized legacy servers, networks and employee computers and implemented Windows Server, Active Directory and VPN access. My cloud experience is deepest in AWS, and I have also worked with Azure across client engagements for more than five years. Identity work includes Microsoft Entra ID, AWS IAM and application access flows, so I am comfortable investigating problems that do not stay neatly within one system.

I also build the tools that make operational work more repeatable. My practice’s deployment tooling records image identity, applies database migrations and checks container and public-service health; separate recovery tooling can restore a backup into a disposable PostgreSQL instance for verification. That mindset goes back to automating backup and audit workflows at IBM. I want a change to be understandable and a recovery path to be more than a hopeful note in a document.

I am self-taught, and I still learn by taking systems apart, asking questions and testing what I think is happening. AI has become another useful tool in that process, especially for investigation and automation, but the responsibility to understand and check the result stays with me. I would bring that curiosity alongside the experience to know when a measured change is better than a clever one.

I am based in Milliken and comfortable with your hybrid schedule and on-call work. I would welcome the chance to help keep your teams’ systems dependable, and make the complicated parts feel a little simpler for the people relying on them.

Chad