I troubleshoot the problems that make it past the obvious fixes.
I’m a Michigan-based technical support and operations professional with a background in managed hosting, web and CMS platforms, production troubleshooting, client escalations, and cross-functional technical delivery.
My strongest work starts when the system is unfamiliar or the first answer did not solve the problem: understand what the person is actually trying to accomplish, establish what is true, separate symptoms from causes, communicate clearly, and own the next step through resolution.
Recent independent work has taken that same support mindset into AI-assisted engineering, developer tooling, model evaluation, local systems, automation, and verification. I’m interested in making powerful systems more useful without pretending they are automatically trustworthy.
Candidate site · LinkedIn · GitHub
listen carefully
↓
establish reality
↓
isolate the cause
↓
make the smallest useful change
↓
verify the result
↓
close the loop
Support is still the foundation of how I think. The tools have gotten more sophisticated; that part has not changed.
| Work | What it shows |
|---|---|
| Invariant engineering system | Systems thinking around AI-assisted work: reusable engineering methods, bounded authority, execution evidence, verification, and explicit human acceptance across Arsenal, Loadout, and Kiln. |
| macadmin | Practical support automation with dry-run and protection gates, diagnostics, structured output, tests, and a bias toward safe operations. |
| cms-utils | Typed Python integration work, CMS inventory and migration planning, defensive HTTP, resumable checkpoints, deterministic artifacts, and 169 unit tests. |
| Clusterwise | Kubernetes learning built around observation, investigation, incident reasoning, communication, and evidence rather than memorizing commands. |
The point of these projects is not that I know every tool they touch. They show how I approach unfamiliar systems: learn the boundaries, make assumptions explicit, build against feedback, and prove what changed.
My earlier work spans more than a decade around technical support, managed WordPress and CMS platforms, web operations, Linux-hosted systems, application troubleshooting, APIs and integrations, DNS and SSL/TLS, performance, backups and recovery, client escalations, vendor coordination, and technical documentation.
At Liquid Web, Fusionary, Nolte, and Crown Bioscience, I worked across customers, developers, vendors, Marketing, IT, QA, and internal teams to diagnose problems, coordinate fixes, validate outcomes, and communicate technical impact clearly.
I’m a dad of four, a lifelong builder, and still a support person at heart.
The deeper I get into AI, the less interested I am in pretending the human disappears. Someone still has to decide what matters, recognize when an answer misses the point, know when to escalate, and take responsibility for what happens next.
Capability is not authority.
I like building systems around that boundary. I also like being the human inside it.
Technical Support Engineer · Application Support Engineer · Product Support · Platform Support · Implementation · Customer Success Engineering · Technical Account Management · developer-support and adjacent technical operations roles
Give me the product, the logs, the documentation, the strange edge case, or the customer problem nobody quite understands yet.
I’ll start figuring it out.