Conner B.

I design radar and software defined radio systems end to end, from the DSP math through FPGA firmware to the RF hardware it runs on. My day job is technical lead for passive radar and non-kinetic effects at a defense contractor, where I run a small team modernizing ground based air surveillance radars. I also run an independent RF/FPGA design practice, and I take selected freelance work here. Radar signal processing. Detection and tracking chains, MTI, STAP, CA and OS CFAR, clutter modeling, waveform and ambiguity design, link and detection budgets. Monostatic, bistatic, passive, and forward scatter geometries. SDR and multi-channel coherent acquisition. KrakenSDR, bladeRF, USRP, RTL arrays, and Xilinx RFSoC (ZCU111, ZCU216, RFSoC 4x2). Phase coherent sync, calibration, and direction finding pipelines that survive real interference, not just a clean bench. FPGA and embedded. Verilog and VHDL, Vivado and Vitis, CASPER toolflow, hardware/software partitioning, Zynq and RFSoC integration, and the unglamorous part: getting data off the board reliably at rate. Algorithms and modeling. Python (NumPy, SciPy, GNU Radio) and MATLAB for algorithm development and verification, CUDA when it has to be fast, and ML models for RF spectrum classification. Antennas and RF hardware. AESA and phased array design, currently fabricating a 14 element X-band slotted waveguide array. Front end component selection, VNA and spectrum analyzer bench work, CAD and 3D printed enclosures. Typical engagements: Architecture and feasibility reviews before you commit to hardware Prototype to product, for example taking a Pi plus multi-SDR breadboard to a real embedded design Algorithm development with verification you can actually trust Gap reviews and second opinions on an existing detection chain Ongoing fractional principal engineer support I write plainly, I will tell you early if something does not close against physics, and I would rather scope a job down honestly than oversell it. US person, based in Florida, comfortable with defense adjacent work. If you have a hard RF problem and you are not sure it is solvable, that is usually the conversation I am most interested in.