Systems reasoning
I follow evidence across technical and operational boundaries until the problem makes sense as a whole.
Field experience / systems depth
More than twenty years across IT infrastructure, custom software, network and AV deployment, field service, connected products, satellite manufacturing support, operational workflow improvement, and AI-directed engineering.
How I think about systems
I look at the people, process, hardware, software, and operating environment together. That broader view helps me find dependencies and failure conditions that disappear when each layer is examined alone.
I follow evidence across technical and operational boundaries until the problem makes sense as a whole.
I turn observations and stakeholder needs into clear behavior, tradeoffs, failure cases, and acceptance criteria.
I direct bounded AI-assisted work, challenge assumptions, and use diagnostics, runtime tests, documentation, and feedback to establish whether the result works and can be supported.
Formal experience
Several earlier roles overlapped because they were part-time, weekend, hourly, or as-needed. Current employer work is described at a high level to protect regulated and confidential details.
Technician III · Amazon Low Earth Orbit (LEO)
Master Technician
Assistant Manager · Primarily weekend work
IT Administrator · Hourly/on-call
Senior Technician
IT Administrator
Technical foundations
I started with systems that exposed every layer. As the technology changed, the habit remained: understand enough of the full path to configure it, integrate it, diagnose it, and explain it.
My hands-on experience spans DOS-era systems, 486 platforms with math-coprocessor configurations, Pentium-era desktops and workstations, Xeon-based servers, and later x86-64, ARM, and other RISC-based platforms. Each generation changed the tools, but not the need to understand how processor, storage, operating system, drivers, network, peripherals, and workload affect one another.
CONFIG.SYS and AUTOEXEC.BAT · memory, IRQ, I/O, DMA, and drivers · firmware, peripherals, virtualization, and system integrationI learned VBA with guidance from a Microsoft engineer, tested a pre-release Word automation environment, identified behavior and documentation errors, and submitted annotated documentation for review. That experience made Visual Basic my preferred language for many years.
I temporarily maintained approximately 12 DOS workstations for my former middle school, including a WordPerfect 5.0-to-5.1 upgrade and peer networking over 10BASE2 thinnet. The work required BNC T-connectors, bus termination, manual drivers, and IRQ, I/O, and DMA configuration. The district later added internal support as its computer deployment expanded.
I was invited to explain Registry architecture and troubleshooting, including GUID and CLSID relationships, shell and special-folder identification, value tracing, startup entries, services, installed programs, and expected versus unexpected entries.
I operated eight physical servers, including a two-host Hyper-V pair and one dedicated storage server, for client services and a separate technical lab spanning Windows services, centralized RAID storage, hosting, remote backup, and routed access.
Read the case studyBeginning in 2013, I provided private-client contract work in computer systems, networking, photography, video capture, editing, and digital-content workflows for hospitality, entertainment, modeling, and independent online-creator environments.
Capabilities and technologies
The strongest fit is work that requires movement between the field problem, technical structure, failure behavior, and a supportable handoff.
Separate AI systems space
The AI Systems Lab shows how the same field-first systems practice extends into local model research, agent infrastructure, AI-assisted product work, deployment, and evaluation.
Open the AI Systems LabI map the actual workflow, constraints, authority, failure conditions, and measurable outcome before selecting the solution.
I define contracts and architecture boundaries, direct specialist agents, review tradeoffs, and correct plausible but wrong assumptions.
I separate source, tests, executable, installation, network, and live evidence, then advance work only when the relevant layer supports it.