Skip to résumé

Senior IT Engineer · Horizon3.ai

IT automation, built to be operated

I build the systems behind the work: client integrations, internal tools and the infrastructure that keeps them useful. My background combines FRII NOC leadership and hands-on escalation work with production application ownership through Technomancy IT. I connect services, make access boundaries explicit and stay responsible after launch.

U02

Service history

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Build and operate client systems from the initial need through deployment and ongoing support. Deliver access-controlled automation and connectors spanning Slack, Google Workspace, Atlassian and internal tools. Implement OAuth/OIDC, PKCE, SAML/SCIM and token workflows in client products, with tenant-aware identity, policy and observability across shared services. Clients call me directly when systems need attention.

Deep dive

My work connects application, data, infrastructure and support decisions. I have implemented selected identity and provisioning integrations in client products, including AWS IAM and Microsoft Entra ID, rather than treating access as an afterthought. I also integrate SaaS and AI tools through authenticated service boundaries and access-controlled connectors.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led the NOC and engineering escalations while building tooling for its operators and hosting/colocation customers. Ran hosted web services, developed in PHP and JavaScript, and handled billing-system development and replacement. Codified operational procedures, recovery checks and audit evidence; ran SOC 1 and SOC 2 audits. Migrated Hyper-V and ESXi workloads into Docker and Kubernetes alongside smaller server and firewall upgrades.

Deep dive

NOC first-line coverage remained in place during my later sole-systems-engineer period. My job included escalations, monitoring, recovery verification and auditor-readable procedures. The completed modernization included workload migrations and smaller server/firewall upgrades; a later full infrastructure replacement remained an unfunded plan.

Office Evolution · 2014-2015

Systems / Software Engineer

Built centralized applications connecting CRM, provisioning, onboarding and service operations across locations. Turned cross-department handoffs into explicit workflows rather than leaving teams to bridge them manually. Worked with the CEO and CIO and supported architecture across client environments, keeping operational needs connected to the systems being built.

Deep dive

The engineering challenge crossed departments as well as systems: CRM, provisioning and service operations needed a shared workflow. I supported architecture across locations and client environments and worked with leadership on the operational context.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered and supported business networks and endpoints in a managed-service environment, with on-call responsibility and direct communication with business owners and users. Built diagnostic tooling and handled remote monitoring, troubleshooting and antivirus services, connecting technical investigation with the people affected.

Deep dive

This was MSP work with customer networks, endpoints and direct user support, not networking alone. Diagnostic tooling and on-call troubleshooting had to produce answers that business owners and users could act on.

IBM · 2010-2012

Infrastructure and Systems Focal

Supported shared enterprise infrastructure, virtualization test labs and hosted desktops, coordinating changes and incidents across teams. Built automation for audit, backup and compliance work, bringing repeatable checks and operational discipline to shared systems.

Deep dive

Shared infrastructure meant coordinating work across teams rather than treating each system in isolation. Virtualization, hosted desktops and operational automation gave me an early grounding in repeatable checks, backups and enterprise change discipline.

U03

Systems and projects

Front Range Internet Inc. · 2015–2020

NOC and customer tooling

Built tooling for NOC/DevOps teams and hosting/colocation customers while owning engineering escalations. Combined hosted web-service development and billing replacement with the operational work of monitoring, recovery verification and documented procedures.

Deep dive

I built tooling for the people running the NOC and for hosting/colocation customers, alongside extensive Docker work and operational system connections. The useful test was whether operators could work with the system and investigate a problem, not whether a script existed.

Office Evolution · 2014–2015

Connected onboarding and service operations

Built shared applications linking CRM, provisioning, onboarding and service operations across locations. Made departmental handoffs explicit in the software so operational work could move through a connected process.

Deep dive

Centralized applications connected CRM, provisioning, onboarding and service operations. Making the handoffs explicit was part of the engineering, not an administrative task left for another department.

NuPrice · Technomancy client engagement · 2019–2021

Rules-driven commerce operations

Built and operated the full application, connecting marketplace and competitor data to user-defined repricing rules, automated price decisions, monitoring and analytics. Owned accounts, billing, embedded support and technical operations alongside the product.

Deep dive

This long-term Technomancy IT client engagement overlapped with my final FRII years. Marketplace data ingestion and configurable repricing connected to accounts, subscriptions, CMS, analytics and embedded support. I built and operated the application and stayed responsible for its technical operations.

ProofMark · completed client contribution · Client project

Identity-aware document workflows

Designed signing workflows across identity, document routing, audit history, verification and webhooks. Connected UI, APIs and PostgreSQL-backed data while keeping security-sensitive state and fallback paths explicit.

Deep dive

My completed client contribution focused on document/PDF fields, routing, encryption, embedded signing, identity, audit history and integrations. The project uses Next.js, React, tRPC, Drizzle, PostgreSQL and Rust. My work connected these parts into an explicit signing workflow within the AGPL/open-source product.

ProofMark ↗
U04

Inventory

  • Operational automation: TypeScript, Bash, PowerShell and practical Python scripting
  • SaaS integrations: APIs, authenticated connectors and tenant-aware shared services
  • Identity implementation: OAuth/OIDC, PKCE, SAML/SCIM, AWS IAM and Microsoft Entra ID
  • Production operations: AWS, Azure client environments, Docker, monitoring and recovery verification
  • Service ownership: NOC escalation, runbooks, onboarding workflows and cross-team handoffs
  • Infrastructure as code and delivery: Terraform, Git/GitHub, CI/CD and container release paths
U05

Cover note

I build automation with the operator and the next failure in mind. Horizon3.ai’s emphasis on owning integrations, documenting the handoff and verifying that systems actually work connects directly to my NOC, client-platform and service-workflow experience.

Read full cover letterClose cover letter

Hi Horizon3.ai team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still get excited when I can turn something complicated into something people can simply use.

Your Senior IT Engineer role caught my attention because it treats automation as something someone has to own, not just build and walk away from. The handoff, the alerts, the failed run and the person waiting for access are all part of the job. That is very familiar territory for me.

At FRII, I ran the NOC, built tooling for operators and hosting customers, and handled the escalations that came through when the first line could not resolve an issue. I also ran web services and handled billing-system development and replacement. After several years there, I became the sole systems engineer for about a year during the ownership transition. Keeping services working, documenting the process and helping the next person understand it mattered just as much as making the change.

At Office Evolution, I built applications connecting CRM, provisioning, onboarding and service operations across locations. Through Technomancy IT, I have carried that into client systems with authenticated integrations, tenant-aware access and ongoing support. NuPrice is a good example: I built and operated the application, its automated pricing decisions, billing and support, rather than handing off the interesting part and leaving someone else to keep it running.

TypeScript is my strongest application language, alongside systems scripting in Bash, PowerShell and Python. I would bring that engineering foundation to your automation stack while learning its particular tools. I also use AI extensively in my engineering work, but I still own the decisions and have to check that the result does what people need.

What I like about Horizon3.ai's find, fix and verify approach is that last step. A change is not finished just because it ran successfully; the workflow and the access it depends on still need to work. I would enjoy bringing that same care to the systems your own team relies on, making the complicated parts feel a little simpler.

Chad