Systems reasoning
I follow evidence across technical and operational boundaries until the problem makes sense as a whole.
Field experience / systems depth
A career spent connecting systems—and understanding why they fail.
More than twenty years across IT infrastructure, custom software, network and AV deployment, field service, connected products, satellite manufacturing support, and operational workflow improvement.
How I think about systems
The technology is only one part of the answer.
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.
Requirements translation
I turn observations and stakeholder needs into clear behavior, tradeoffs, failure cases, and acceptance criteria.
Validation & handoff
I use diagnostics, tests, documentation, and direct feedback to establish whether the result actually works and can be supported.
Technical foundations
I learned the modern stack by working through the generations that built it.
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.
From XT and 8086 machines to Xeon, x86-64, ARM, and embedded systems
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.
Processor and platform progressionXT and 8086 · 486 and math coprocessors · Pentium · Xeon · x86-64 · ARM and other RISC-based systems
Storage progressionMFM · IDE/PATA · SCSI · SAS · SATA and 10K Raptor drives · early PCIe solid-state storage · M.2 solid-state devices
Configuration to integration
CONFIG.SYS and AUTOEXEC.BAT · memory, IRQ, I/O, DMA, and drivers · firmware, peripherals, virtualization, and system integrationEarly Microsoft Word/VBA beta experience
I 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.
My first paid systems work
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.
In-person Windows Registry guest lecture
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.
Eight-server Windows infrastructure
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 studyTechnical and digital-media support
I provided discreet computer, networking, photography, video capture, editing, and digital-content workflow support for hospitality, entertainment, modeling, and independent online-creator clients.
Formal experience
Different industries. The same systems mindset.
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.
Aug 2025 — Present
Kirkland, Washington
Kirkland, Washington
Amazon
Technician III · Amazon Low Earth Orbit (LEO)
- Support technical operations in a regulated satellite-manufacturing environment through cross-domain troubleshooting, documentation, validation, and workflow improvement.
- Translate observed operational needs into bounded requirements and acceptance criteria, then direct structured AI-assisted development while retaining technical review and final acceptance.
- Work across equipment, software, data, workflow, and documentation boundaries to isolate problems and support reliable execution.
Dec 2022 — Dec 2024
Kent, Washington
Kent, Washington
Lunyar LLC
Master Technician
- Completed residential and commercial work spanning AV, networking, appliances, electrical interfaces, plumbing-connected systems, and structural constraints.
- Coordinated scheduling and dispatch for three field teams and served as the customer communication and field-escalation point for complex issues.
- Traced manufacturer defects, prior-installation failures, and cross-trade interactions to define practical repair plans and completion criteria.
Jan 2008 — Mar 2020
Everett, Washington
Everett, Washington
Everett Yacht Club
Assistant Manager · Primarily weekend work
- Supported venue and event operations for gatherings of up to approximately 150 guests through customer and vendor coordination, scheduling, and day-of execution.
- Maintained event AV, office computers, network infrastructure, domain and DNS administration, organizational email, website hosting, digital contracts, shared files, retention, backup, and recovery.
- Troubleshot and repaired commercial kitchen, bar, and facility equipment.
Jan 2013 — Dec 2014
Tacoma, Washington
Tacoma, Washington
Washington State PTA
IT Administrator · Hourly/on-call
- Administered approximately 10–25 central-office endpoints plus cabling, managed network equipment, routers, VPN connectivity, security controls, web hosting, and the website/application stack.
- Maintained forms, queries, reports, and VBA in an Access-based line-of-business application using shared organizational data sources; the database administrator retained ownership of the underlying structure and bulk-email operations.
- Built and supported temporary registration and payment systems, workstations, networking, and printers at statewide conferences.
- Developed and maintained the online membership-payment workflow, integrating the PTA-hosted application with a third-party merchant processor through a secured API and supporting the processor’s security-certification process. Only limited transaction and reconciliation references were retained after authorization.
Jan 2008 — Dec 2011
Seattle, Washington
Seattle, Washington
360 System Solutions
Senior Technician
- Developed and supported a Visual Basic distributed transaction application with protected local store-and-forward files, offline transaction continuity, end-of-day central synchronization, centrally managed configuration, and custom peripheral drivers.
- Connected a corporate office, call center, and several retail locations over routed site-to-site VPNs; each store operated three to five registers and a commercial LED sign.
- Built a shared Windows fax service that accepted requests from multiple Access workstations supporting call-center dispatch and collection pickup.
- Deployed and supported the combined networking, servers, endpoints, telephony, registers, peripherals, signage integration, and field technology.
Jan 2002 — Dec 2012
Seattle, Washington
Seattle, Washington
NVL Laboratories, Inc.
IT Administrator
- Completed a Mac-to-PC platform migration across three locations and approximately 25–50 endpoints using Windows XP, Windows Small Business Server, and site-to-site VPN connectivity.
- Developed Windows applications, tray utilities, and service processes primarily in Visual Basic using Visual Studio, with selected C# components.
- Built the PDF-to-FileMaker association workflow and client-facing retrieval portal; used Word VBA specifically to populate standardized reports and produce final PDFs.
- Maintained local tape backup and a separately located off-site backup, and authored user guides, system-administration documentation, recovery instructions, and troubleshooting procedures.
Forward-deployed AI solutions
I use AI to extend engineering capacity—not to replace engineering judgment.
My recent work follows a forward-deployed pattern: understand the workflow, identify the failure conditions, define the requirements, direct AI-assisted implementation, and decide whether the result is ready based on evidence.
- 01
Learn the environment
Begin with the actual users, tools, constraints, and operating conditions rather than a generic AI solution.
- 02
Give structured direction
Break the problem into bounded tasks, interfaces, decisions, failure cases, and acceptance criteria.
- 03
Keep human ownership
Retain responsibility for architecture, judgment, technical review, privacy, safety, and final acceptance.
- 04
Correct from evidence
Use diagnostics, tests, and operating feedback to challenge assumptions and improve the result iteratively.