Control systems technician · developer · Security+

I troubleshoot what the runbook doesn't cover.

I work across software, infrastructure, networks, data, and hardware—then turn the fix into a tool or process the next person can use.

See the work View résumé
LinkedIn ↗GitHub ↗Email ↗

01 / Selected work

Work samples with a reason to exist.

Each project starts with an operational problem—not a tutorial prompt.

01

Flagship build

Python desktop + React web MVPVerified product case study

F.A.T.

Factory Acceptance Testing, rebuilt as a controlled project workflow.

A project-first product that replaces scattered QA forms with structured authoring, tablet inspections, role-aware access, PDF generation, backups, recovery, and a deployment model built for real teams.

ProjectQA buildInspectionFinal record
Desktop
Python, PyQt6, ReportLab
Web MVP
React, TypeScript, Node
Validation
50 / 50 release cycles passed
Read the full F.A.T. case study
02Systems recovery

Completed

Legacy control systems recovery

Rebuilt a failed Linux application environment, restored its PostgreSQL data, corrected permissions and network issues, and documented the recovery path for the next technician.Read case study →

Linux / PostgreSQL / recovery / documentation

03Support engineering

In development

Support automation lab

A practical toolkit for collecting system facts, checking network health, and packaging useful diagnostics before a support ticket changes hands.

PowerShell / Python / networking / support

02 / Working method

Useful when the answer is not in the SOP.

Difficult troubleshooting is daily work for me. The process stays grounded in evidence.

01

Trace the whole failure

Software, infrastructure, data, and hardware are one system when something stops working. I follow the evidence across those boundaries.

02

Build the practical fix

When a recurring problem needs more than a procedure, I build a small tool or automation that reduces repetition and risk.

03

Write down the path

I document what failed, what proved it, and how it was recovered so the answer remains useful after the incident is over.

Current field work

Control Systems Technician

Troubleshooting mixed Linux, PostgreSQL, control-system, network, and hardware issues; building tools for recurring work; repairing and deploying PCs; and documenting procedures while the work is completed.

03 / Capabilities

One operator. More than one layer.

Broad technical range, applied to support and operations rather than listed as decoration.

AreaWorking knowledgeApplied to
SystemsWindows, Linux / RHEL, macOS, VirtualBoxDeployment, repair, diagnostics
SoftwarePython, PowerShell, JavaScript / TypeScript, ReactTools, automation, interfaces
Network + securityCisco, TCP/IP, Wireshark, Nessus, SplunkAnalysis, hardening, support
Data + operationsPostgreSQL, SQL, Git, technical documentationRecovery, migration, repeatability

CertificationCompTIA Security+

TrainingUW–Madison Cybersecurity

Development5+ years with React

04 / Contact

Bring me the problem that keeps crossing team boundaries.

I'm targeting technical support, systems, application support, networking, and security-support opportunities.

Start a conversation Résumé ↗LinkedIn ↗GitHub ↗