SDR Communications Engineer

Summary: We’re building a software-defined-radio demonstrator for a two-way wireless data link that stays alive under interference/jamming: it detects interference, finds a clean channel on its own, and reconnects automatically — all in software on the radio. We have a complete written build spec (shared under NDA). We need an experienced SDR engineer to implement it on a 3-node bench (2 link nodes + 1 interferer) and deliver working code plus measured results. Scope (bench demonstration): • A real software modem (e.g., DBPSK/GFSK) passing data between two SDRs full-duplex, with packet framing, frequency/timing-offset recovery, and CRC. • A frequency-agile recovery protocol: detect interference, scan the band, re-establish the link on a clean channel via a shared, deterministic channel-selection scheme. • An interferer node (one SDR) with wideband, swept, and simple reactive modes. • A live dashboard (spectrum waterfall, link status, recovery latency) + CSV logging. • A 100-trial run producing a clean data package (recovery-time distribution, success rate by interferer type) against defined pass/fail criteria. Required: demonstrated experience building working SDR links (not receive-only) — modulation, packet sync, carrier/timing-offset recovery; GNU Radio and/or DSP libraries (liquid-dsp); Python + C/C++; hands-on with Pluto/USRP/LimeSDR/HackRF; FFT-based spectrum sensing; rigorous about measurement (distributions, percentiles, repeatability). Nice to have: FPGA/Zynq or embedded DSP; FHSS / anti-jam / wireless-resilience background; PX4/ArduPilot/MAVLink (possible follow-on flight phase). Logistics: milestone-based, tied to defined acceptance gates; ~2–3 months. Hardware: [pick one — we ship you a bench kit / you must already own the SDRs]. NDA before we share the full spec; IP assigned to us.