Network Architect · Sioux Falls, SD

Hi, I’m
Chase.

I work across hardware, networks, platforms, automation, and AI—because the hardest infrastructure problems do not stay in one layer.

Routing · Switching · VXLAN · SD-WANCisco · Palo-Alto · ArubaAutomation · Agentic Design · AI-assisted NetOps

Get in touch Explore experience

chase@spydercolo:~profile-loader

>Loading 10+ years of experience

Career timeline

From implementation
to architecture.

A hands-on progression through physical infrastructure, operations, engineering, automation, and technical leadership.

Network ArchitectSONIFI Solutions · Oct 2025 — Present

Enterprise architecture, technical leadership, and escalation across a large hospitality technology estate.

Network Engineer IISONIFI Solutions · Oct 2024 — Oct 2025

Remote hospitality deployment, cutover, validation, and troubleshooting.

Senior Network EngineerWindsor Sales · Feb 2019 — Oct 2024

End-to-end infrastructure design and operations across a multi-site enterprise.

Network Operations EngineerApogee Enterprises · Feb 2017 — Feb 2019

Network operations and design work for 24/7 manufacturing environments.

Network Infrastructure TechnicianMetaBank, now Pathward · May 2016 — Feb 2017

Physical infrastructure support and early workflow automation in financial services.

Network Administrator InternWorkplace IT Management · Apr 2015 — Apr 2016

General infrastructure support across a 140+ client MSP.

Architecture principles

How I approach
complex systems.

Technology matters, but dependable infrastructure comes from the decisions that connect it: design, state, ownership, and control.

Design for operational reality

Topology, failure domains, access paths, and ownership are considered before a platform is considered complete.

Make state explicit

Source of truth, governed configuration, observability, and change evidence turn complexity into something operators can trust.

Use automation with boundaries

Automation and AI can accelerate good operators, but authority, approval, and verification remain intentional.

Troubleshoot across layers

Network incidents rarely remain network-only. I trace behavior across RF, routing, identity, DHCP, platforms, and applications to find the actual failure boundary.

Featured work

Systems and investigations.

Independent platform

Platform at a glance

448: vCPUs
~510 TB: available storage
40 / 100 Gb: core fabric
1.92 TB: memory

SpyderColo

A routed, virtualized, observable platform for infrastructure engineering, private inference, and controlled agent tooling.

Explore the architecture

Platform migration

Rebuilding private AI inference for production serving

What changed when shared chat and agent workloads needed a better serving, scheduling, and observability layer.

Read article

System design

Frontier: local execution with frontier review

How bounded contracts and verified evidence connect local coding work to architectural judgment.