
An opinionated reading list and learning path for RF and satellite communications engineering — filtered through 11 years of actually doing it.
Ian Cleary
There's a GitHub repo called How to learn modern electronics that lists hundreds of books across every electronics discipline. It's comprehensive. It's also overwhelming.
I've been an RF systems engineer for 11+ years at Viasat, working on Ka, Ku, V, and X-band satellite communications. This is my filtered version: the books, tools, and resources that actually matter if you want to do RF engineering for satellite communications. Not everything — the right things, in the right order.
Before you touch RF, you need circuit analysis and electromagnetics. There's no shortcut.
Fundamentals of Electric Circuits by Alexander & Sadiku is the standard. Read it. Work the problems. Don't skip AC analysis — phasors and impedance are the language of RF.
If you want free alternatives, James Fiore's DC and AC Electrical Circuit Analysis books are excellent and Creative Commons. The accompanying videos are surprisingly good.
This is where most people bail. Don't.
Electromagnetics Explained by Ron Schmitt is the gentlest on-ramp I've found. It's written for practicing engineers, not professors. It connects Maxwell's equations to things you actually care about: transmission lines, radiation, shielding.
After that, you'll eventually need Pozar. But not yet.
Practical Electronics for Inventors by Scherz & Monk is an underrated entry point. The RF chapters are brief but well-contextualized. It shows you where RF fits in the bigger electronics picture.
The ARRL Handbook is surprisingly deep. Yes, it's aimed at ham radio operators. But the chapters on transmitters, receivers, propagation, and antenna design are practical in a way that textbooks often aren't. The supplemental digital files are worth the price alone.
The Art of Electronics by Horowitz & Hill. Chapter 13 (RF) alone is worth the book. The companion x Chapters has additional RF material that's hard to find elsewhere. This is the book that teaches you intuition, not just equations.
Now Pozar.
Microwave Engineering by David Pozar is the industry bible. Every RF engineer I know has a copy within arm's reach. S-parameters, Smith charts, matching networks, filter design, amplifier stability — it's all here. Dense but correct.
RF Microelectronics by Behzad Razavi covers the IC side: mixers, oscillators, PLLs, receiver architectures. Essential if you work on transceiver design or need to understand what's inside the chips you're specifying.
Michael Steer's Microwave and RF Design series (5 volumes) is free under Creative Commons. The quality rivals paid textbooks. Start with Volume 1 (Radio Systems) for the big picture, then Volume 2 (Transmission Lines) and Volume 3 (Networks) for the math you need daily.
RF Circuit Design by Christopher Bowick is thin, practical, and gets you designing faster than any other book on this list. Good for when you need to build something, not just analyze it.
This is where things get specific to what I do.
A link budget is the single most important analysis in satellite communications. It answers: "Can this signal close?"
There's no single perfect book for this. You learn link budgets by doing them. But the theory comes from:
I've built my own tools for this in Rust: linkbudget handles the full chain from transmitter through propagation to receiver, including modulation, BER, coding gain, and sensitivity.
Cascaded gain, noise figure, IP3 — the Friis equation and its extensions are your daily bread.
I built gainlineup because I got tired of doing this in spreadsheets. It cascades gain, noise figure, P1dB, IP3, SFDR, dynamic range, and generates AM-AM compression curves.
Antenna Theory: Analysis and Design by Balanis is the definitive reference. Heavy on math, but you need it for phased arrays.
Practical Antenna Handbook by Carr & Hippisley is the hands-on complement.
For phased array work specifically:
You'll spend a lot of time staring at S-parameter data. Understanding what you're looking at matters.
I built touchstone for parsing and cascading S-parameter files. If you're doing any RF measurement work, you'll deal with Touchstone (.s2p) files constantly.
Modern satellite links are digital. You need to understand modulation, coding, and error rates.
Digital Communications by Proakis & Salehi is the classic. Dense but comprehensive.
Software Receiver Design by Johnson, Sethares & Klein takes a different approach — build a receiver in software, step by step. Excellent for developing intuition about what's happening to your signal.
The DVB-S2 standard (ETSI EN 302 307) is worth reading directly if you work on broadcast or broadband satellite. It's well-written for a standard and shows how modulation, coding, and framing fit together in a real system.
You'll need some DSP. Not as much as a signal processing engineer, but enough.
The Scientist & Engineer's Guide to Digital Signal Processing by Steven Smith is free online and is the best first book on DSP I've read. Clear writing, practical focus.
Understanding Digital Signal Processing by Richard Lyons is the standard second book. More rigorous, covers multirate and spectral analysis well.
The industry runs on licensed tools: ADS (Keysight), AWR (Cadence), HFSS (Ansys), MATLAB. They're expensive ($3K–$50K/seat) and powerful.
For personal work and open-source alternatives:
RF PCB layout is its own discipline.
Signal Integrity Issues and Printed Circuit Board Design by Douglas Brooks is the practical starting point.
High Speed Digital Design by Howard Johnson is technically about digital, but transmission line effects don't care what your signal looks like. Essential for anything above a few hundred MHz.
KiCad is free and increasingly capable for RF work. Dr. Peter Dalmaris's KiCad Like a Pro is a solid guide.
If I were starting over, here's the order:
That's roughly 18–24 months to go from "I know Ohm's law" to "I can design a satellite ground station receive chain." It's a lot. But RF engineering is a lot.
Spreadsheets are where RF analysis goes to die. They're fine for a quick sanity check. They're terrible for repeatable, version-controlled, unit-safe analysis. Write code instead.
The ITU recommendations are worth reading. They're the actual models used in practice. Academic textbooks simplify them. The real world doesn't.
Measure things. Theory is necessary but insufficient. The first time your amplifier oscillates at a frequency you didn't expect, you'll understand why RF engineers seem paranoid.
The system view matters more than any single discipline. An antenna engineer who doesn't understand link budgets, or a signal chain engineer who doesn't understand modulation, is only solving part of the problem. The best RF systems engineers see the whole picture.
That's the path. It's long, it's deep, and it never really ends. But the rabbit hole is worth it.
Ian Cleary is an RF Systems Engineer with 11+ years of experience in satellite communications. He publishes open-source RF analysis tools in Rust at crates.io.