Open to remote roles · Southern Oregon
Technical Support, Linux Systems & Infrastructure Operations
I solve difficult problems across hardware, software, networks, and self-hosted systems. My background combines remote technical support with hands-on repair, so I am comfortable tracing failures from symptoms to verified fixes.
Recent professional experience
Professional employment comes first here because troubleshooting is more than a technology list: it is diagnosis, judgment, communication, and follow-through.
Professional employment
Supported field appliance technicians remotely by helping isolate faults, interpret symptoms, evaluate repair options, and move difficult service calls toward an appropriate next step. Communicated technical information through phone, case-management, collaboration, and office tools.
Selected evidence
Each case study separates the problem, constraints, role, approach, verification, and trade-offs rather than relying on a technology badge.
Open source · Mail security utility
Deterministic authenticated email aliases with HMAC-based tags, stateless verification, compatibility handling, explicit security limits, and a public regression suite.
Open source · Focused automation
A compact shell utility for turning a predictable key-naming and addressing convention into generated SSH configuration, with an honest boundary around its assumptions.
Personal infrastructure · Owner/operator
A sanitized view of hands-on Linux operations across virtualization, segmented networking, monitoring, backups, secure access, GPU workloads, and recovery planning.
Skills by function
Skills are grouped by the work they support and labeled by professional, open-source, or personal-infrastructure evidence on the dedicated page.
Diagnose
Fault isolation, symptom interpretation, repair decisions, escalation context, customer communication, and technical documentation.
Operate
Linux, systemd, virtualization, containers, storage, service health, backups, and recovery-oriented changes.
Trace
DNS, VLANs, routing, VPNs, firewalls, reverse proxies, TLS, and least-privilege administrative paths.
Reduce repeat work
Shell, Python, APIs, tests, structured data, GPU workloads, model routing, and operational runbooks.
About the approach
Diagnosing physical systems taught me that guessing costs time and parts. I apply the same disciplined process to software and infrastructure: understand the symptom, isolate the failure, make the smallest defensible change, verify the result, and preserve a recovery path.
