Skip to résumé

Senior DevOps Engineer · PulteMortgage

Senior DevOps EngineerPulteMortgage

I build automation the person on call can trust. At FRII, that meant making infrastructure changes supportable by the NOC. In client work today, it means checking that a release actually serves traffic and that a backup actually restores.

U02

Service history

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Build, deploy and support production systems for clients, including Microsoft Azure environments; own incident escalation and ongoing support. Automate deployment and database recovery checks; integrate APIs and SaaS workflows with access controls and service identities. Built a commerce automation app in the Microsoft Power Platform ecosystem on an approximately eight-month client contract.

Deep dive

I work with clients from discovery through production support. Azure work spans multiple client engagements and Microsoft systems setup and support; AWS is where I have the most hands-on cloud depth. For app and SaaS integrations I work across API authentication, tenant-aware access controls and workload identity. On a separate client contract lasting about eight months, I built a commerce automation app in the Microsoft Power Platform ecosystem.

Front Range Internet Inc. · 2015–2020

Senior Systems Engineer / Datacenter Architect

Led NOC operations and engineering escalations; built monitoring and operator tooling for NOC staff and hosting and colocation customers. Migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes and carried out targeted server and firewall upgrades. Ran SOC 1 and SOC 2 audits and documented infrastructure controls, recovery checks and procedures for operators.

Deep dive

When unresolved issues came through the NOC, I took the systems escalation and translated what we learned into procedures that operators could use. During the ownership transition I took sole systems-engineering responsibility for about a year with the NOC continuing first-line coverage. I helped develop a full infrastructure replacement plan that was not funded; the workload migrations and smaller upgrades did ship.

Office Evolution · 2014–2015

Systems / Software Engineer

Built CRM, provisioning and onboarding tools across locations, replacing manual network setup with Node.js automation. Designed a Linux routing system with separate office VLANs, individual Wi-Fi accounts and per-office bandwidth and access settings.

Deep dive

Individual Wi-Fi accounts mapped to the right customer network. I automated parts of router and firewall setup for new locations and gave front-desk staff a separate interface for Wi-Fi password resets and troubleshooting. Routing, access and bandwidth rules stayed separate for each customer office.

PlumChoice / Everon · 2012–2014

Network & Systems Engineer

Supported managed-service client networks and endpoints, building diagnostics for recurring issues and handling on-call escalation.

Deep dive

Managed-service work covered customer networks, endpoint troubleshooting and antivirus services. I was on call for clients and built tooling around recurring diagnostics rather than solving the same issues from scratch.

IBM · 2010–2012

Infrastructure and Systems Focal

Automated backup, auditing and compliance tasks with scripts and managed virtualization test labs and hosted desktops. Built an internal backup tool used by executives and other staff to reduce licensing costs.

Deep dive

I coordinated incidents, changes and access across shared enterprise environments. I used Perl, Bash, VBA and PHP for internal tooling, including a backup tool that became a practical alternative to buying additional software licenses.

U03

Systems and projects

Office Evolution · employment · 2014–2015

Automating office onboarding

Built a Linux routing system that mapped individual Wi-Fi accounts to the right office VLAN. I set bandwidth and access by office and automated parts of router and firewall setup with Node.js.

Deep dive

The manual work was not just creating accounts: each office needed its own network and service rules. The Linux routing system kept those settings separate. I made network setup repeatable and gave front-desk staff a separate way to reset Wi-Fi passwords and troubleshoot.

Technomancy IT · practice platform

Deployments and backup recovery checks

Built a Git-tagged release workflow that applies SQL migrations and verifies both container health and the public HTTP endpoint. Wrote a separate PostgreSQL backup check that restores into a disposable instance and checks the recovered tables.

Deep dive

I separate a successful deploy command from a service that actually responds. The restore check likewise goes beyond confirming the backup file exists: it verifies the backup checksum, restores the database into a separate instance, then checks table counts.

Technomancy support platform overview ↗
U04

Inventory

  • Microsoft Azure, AWS and Windows Server
  • Docker, Kubernetes, Hyper-V and VMware ESXi
  • GitHub Actions, Bash and deployment automation
  • Power Platform (commerce automation), REST API integration and service access controls
  • Monitoring, recovery verification and operational escalation
U05

Cover note

I build automation the person on call can trust. At FRII, that meant making infrastructure changes supportable by the NOC. In client work today, it means checking that a release actually serves traffic and that a backup actually restores.

Read full cover letterClose cover letter

Hi PulteMortgage team,

What caught my eye about this role is that it puts infrastructure and the workflows people depend on in the same job. Your home-financing process moves from an online application to a dedicated loan team. I’d like to help build the automation that makes handoffs like those easier to operate, especially when a step fails and someone needs to know what happened.

At Front Range Internet Inc., I ran the NOC and handled systems escalations. I moved workloads from Hyper-V and VMware ESXi into Docker and Kubernetes while the team still had to support customers on the existing infrastructure. I built tooling for NOC operators and hosting customers and ran our SOC 1 and SOC 2 audits, so I got used to making the controls and recovery steps clear enough for someone else to verify.

A different kind of workflow automation came up at Office Evolution. I gave each customer office its own network and automated parts of the setup. I built a separate tool so front-desk staff could reset Wi-Fi passwords and troubleshoot without waiting for IT. At Technomancy IT, I bring the same approach to software deployments and recovery. For our support platform, a release checks container health and the public endpoint separately. I also built a backup check that actually restores PostgreSQL into a disposable instance and checks the recovered tables.

Most of my automation work is code-driven, but I’ve also built a commerce automation app in the Microsoft Power Platform ecosystem on an approximately eight-month client contract. I’ve worked in Azure and supported Microsoft environments across other client engagements. I’d bring that experience to PulteMortgage, along with a habit that has served me well on call: build the check and the handoff while you build the automation, not after the first incident.

Thanks, Chad Koslovsky