Skip to content

RF hardware engineer/Space & defense/Denver, CO

RF hardware engineer.
AI-native builder ofeverything else.

I lead RF architecture and front-end design for space and defense hardware: link budgets, L- to Ku-band front ends, phased arrays and flight test. Outside the lab, AI agents are my engineering team. With them I ship RF test benches, a mains-switching PCB, software products and the infrastructure they run on.

Key specifications

RF hardware for space and defense7+yrs
Engineering hours saved by one tool I built1,500hrs
Builds shipped with AI agents, below11
Parts on a mains PCB, brief to routed in 3 days288
Fig. 1 · Receive chain, cascaded
REFCR1U1FL1U2MX1U3CASCADE
G, dB−0.4+18.0−1.8+15.0−7.0+20.0+43.8
NF, dB0.40.91.82.57.53.01.42
NF to here0.401.301.331.391.411.42
01RF engineering

The day job: RF systems for space and defense.

A1

System architecture

Link budgets, architecture trades and RF architecture for high-stakes proposals, and presenting the design to customers as the technical authority.

A2

Front-end design

L- through Ku-band front ends, from HFSS, Microwave Office and ADS simulation through procurement and flight test.

A3

Phased arrays

Digital beamforming boards, a 1:16 distribution network at 35 dB gain and 40 A, and bare-metal T/R switch firmware.

A4

Test and process

SCPI test automation, standardized design reviews and "test like you fly" protocols that cut non-conformances.

Before engineering, nine years in operations and supply-chain planning. It's why I weigh trades in schedule and dollars as well as dB.

Full resume →
02Built with AI

Software, hardware and everything in between.

Each build was designed and shipped with AI agents, mostly Claude Code, under the same discipline I use on flight hardware. Every page says what the agents did and how the work was checked.

03Method

Flight-hardware discipline, applied to AI agents.

The habits that keep flight hardware out of trouble (written requirements, gated reviews, traceable decisions, test like you fly) are what turn AI agents from fast into fast and right.

  1. 1

    Brief

    Requirements, constraints and what "done" means, written before any code or copper.

  2. 2

    Phase gates

    Architecture, parts, schematic, layout. Agents stop at every gate; I approve or send them back.

  3. 3

    Decision log

    Every non-obvious call recorded with the alternatives and the evidence, so no session starts blind.

  4. 4

    Independent review

    Separate agents audit the work: ERC and DRC, mains stress, security, datasheets, math from first principles.

Read the method →
04Try it

RF Workbench

Draw a signal chain and get a live cascade of gain, noise figure, IP3, P1dB and sensitivity at every stage. Load Touchstone files and compare parts on rectangular or Smith axes. Runs entirely in the browser.

Block diagramsCascadeS-parametersSmith chartOpen the workbench →