This article also needs a huge (in the US) disclaimer on it as Europe, especially, has had a boom in automotive components and vehicle telemetry in recent years and obviously a lot of consumer devices and handset stuff comes out of China now.
cue rimshot
You make less money, often half. You need to commute to work. Work prospects are narrower and heavily military biased. You get exposed to harmful materials/chemicals. Hardware development is slow, tedious, and punishing compared to software. Having a home lab requires far far more than a laptop. Information is much more sparse so being around knowledgeable others is often critical.
The industry is packed with grey beards, I'm often the youngest guy by 20 years in customer meetings.
Maybe things will change now that we're in a period of uncertainty, but I see hardware as being a thing for the second world and unlikely to stage a big comeback.
Not an EE myself but honestly baffled how the author got that impression with the huge expansion of RF engineering in the consumer space - particularly with 3/4/5G/LTE networks and 802.1x. Maybe this is just an artifact of working on building weapons (i.e. defense) and being in the US?
Apart from that I wonder how much of the resurgence can be traced back to more active conflicts around the world? There is a booming Drone and EW development within the military sector which could be what drives it?
At least you don't hate your job, I hope? The recent maturation of AI revealed how many people in software seemingly loathe their own profession.
The product work is higher level system packaging, such as antennas and application-level manipulation of the whole RF block. But since so much is digital now, that is more software/computer architecture work rather than RF. The COTS RF circuit itself may have standardized serial or even packet interfaces to the rest of the product.
Yes. I think American society will struggle to produce enough competent electrical engineers outside of the university system.
> there's going to be some big reorganization to reflect the fact that you can now learn just as well OUTSIDE of a university context
In my experience, very few people like learning the math needed to be competent at RF. It’s hard and exhausting and without a human connection most people are going to bounce. This isn’t like software where if you get it 80% right something still occurs.
I’ve worked with homeschoolers too, and unless they’re the small fraction of people for whom math comes naturally, they’re not going to study it on their own. But that’s exactly the audience one has to reach to grow the EE supply.
Mostly, expensive tools became more accessible like TinySA, LiteVNA64 and NanoVNA.
For the amateur Ham hobby, it has been a bit of a golden age with <$50 rtl-sdr SDR kits. =3
My criticism still stands. If I know what I am searching for, it's easy to find. But often enough have I seen authors use terms which can have multiple meanings and I would need to look at their definitions in parallel of the context of the article, just to understand what it's even about. No thanks, I'll just pick the next HN post instead.
14 Apr, 2026
I've worked in the aerospace industry for the past 8 years, and for most of that time I felt like I could confidently say that RF engineering felt like it was a quiet, non evolving field. The advice I heard early on, and that I watched a lot of other people follow, was to go into software. Machine learning, cloud infrastructure, web development. That's where the growth was, that's where the money was, and honestly, that's where most new graduates went (myself included at the time). I studied Information Systems in college, not electrical engineering. RF was nowhere on my radar.
But aerospace has a way of pulling you into hardware whether you planned on it or not. I started my career at NASA, building telemetry platforms, ETL pipelines, and spacecraft visualization tools. Pure software work. Then I moved to a private aerospace company. Much smaller than NASA (approx 130 employees at the time I joined), and it required me to wear a ton of hats to work on ground systems. That's where things shifted. When you're responsible for ground station services, even when most of it now is software defined you can't stay in the software lane entirely. I found myself doing link budget analysis, troubleshooting RF anomalies, and developing a working understanding of the RF hardware chain that I never expected to need.
That experience is part of why I've been paying attention to what's happening in RF more broadly. I've been feeling a shift over the past several years — more demand, fewer people, and more urgency from the companies I talk to. RF engineering is not only alive, it's rebounding in a significant way. I wanted to dig into whether my gut feeling here is actually backed by data, or if I'm just seeing what I want to see from inside the aerospace bubble.
To be fair to the people who called RF a shrinking field, they weren't wrong, at least for a stretch. After the dot-com bust in the early 2000s, the telecom industry consolidated hard. Companies merged, manufacturing moved offshore, and a lot of RF design work either disappeared or got absorbed into a handful of large defense contractors. The broader electrical engineering job market stagnated. Electronic Design has documented this trend not just for RF, but across EE as a whole. I feel confident that if the field as a whole is shrinking, then the subfield of RF was also in decline.
And then software exploded. The engineers who might've gone into EE or RF design a generation earlier went down the software "FAANG" route instead. University enrollment in RF specific coursework drifted down. Though I'll be honest, hard numbers on this are annoyingly hard to find so this is more of my gut assumption. What we do know is that today, companies openly describe the difficulty of recruiting RF engineers, pointing to a generation that chose software over EE.
But here's the thing that gets missed in the narrative: it never actually went away. The defense sector has been keeping it alive this entire time. Raytheon, Lockheed Martin, Northrop Grumman, these companies never stopped hiring people who understand beam patterns, power amplifiers, and antenna design. The majority of RF engineering job postings have historically come from aerospace and defense. RF didn't die. It just receded from the civilian sector while quietly remaining essential to national security and defense.
The resurgence didn't come from one place. It's coming from several industries all hitting the same wall at roughly the same time; a shortage of engineers who can work at the hardware level.
This is the one I see most directly in my work, and it feels the most dramatic. In 2015, roughly 260 spacecraft were launched into space globally. By 2024, that number hit approximately 2,695. A 10x increase in under a decade. The overwhelming majority of that growth came from commercial constellations, with SpaceX's Starlink deploying over 1,500 satellites in 2023 alone.
Every single one of those satellites needs RF hardware. Starlink operates in Ku-band for user links and Ka-band for gateways, with V-band planned for Starlink V2. Kuiper and OneWeb follow similar architectures in Ka-band. Each spacecraft carries transceivers, antennas, filters, and amplifiers — and each ground station that talks to them needs the same. The amount of RF hardware per spacecraft adds up fast, and the launch cadence isn't slowing down.
The money tells the same story. The global space economy hit a record $613 billion in 2024, with commercial making up roughly 78% of that. The space based RF market alone was valued at $18.6 billion and is projected to nearly double by 2033.
And it's not just commercial. On the defense side, the Space Development Agency is building the Proliferated Warfighter Space Architecture — a LEO constellation targeting 500+ satellites. Only a few dozen are on orbit today, but nearly $35 billion has been committed through 2029. Even with the growing push toward optical links, these spacecraft still carry RF communications hardware and telemetry payloads, and that is unlikely to change anytime soon.
I think 5G's impact on RF demand is genuinely understated. A typical 4G base station has 2 or 4 transmit-receive chains. A 5G MIMO radio integrates anywhere from 64 to 256. That's an 8x to 16x increase in the power amplifiers, low-noise amplifiers, and antenna switches needed per installation. Multiply that across 642 operators and 374 commercial launches, and you start to see why the RF component market is pushing toward $50 billion with no signs of stoppage.
The design challenges make it worse. Millimeter wave frequencies introduce path loss that demands arrays with manufacturing tolerances at the millimeter scale. Additionally, thermal management, ex. dissipating 300+ watts from tower-mounted hardware with passive cooling, isn't something you can solve reliably in software.
It's early, but 6G isn't vaporware. 3GPP has been actively working on 6G study items since 2024, with first specifications targeted for late 2028 and commercial deployments expected around 2030. The EU, South Korea, and major telecom players like Ericsson, Nokia, and Samsung are all investing heavily into this research.
The RF challenges are genuinely new territory. Sub-terahertz frequencies and integrated sensing and communication (ISAC), which 3GPP officially scoped into 6G in the middle of last year, push well beyond what current design tools can handle. Worth noting though — the original vision for sub-THz has already been scaled back from outdoor cellular to mostly short-range indoor use cases like data centers and factories. But even with a narrower scope, all of this research eventually has to become hardware, and the people who know how to do that are already stretched thin.
Space and cellular seem to dominate the conversation, but there are quieter contributors that I think are what make this feeling more durable rather than cyclical.
Automotive radar is a sneaky one. The EU now mandates automatic emergency braking in all new vehicles and, while the regulation is technically sensor-agnostic, most implementations rely on radar. Every new car with adaptive cruise control or collision avoidance has RF hardware running on board. That market alone is projected to hit $7+ billion this year. Then there's Wi-Fi 7, operating across three bands simultaneously, and the ever expanding IoT landscape with over 21 billion connected devices as of 2025. Anything that communicates wirelessly needs RF work behind it, and that list just keeps growing.
What makes this an interesting pattern, is that the supply side is genuinely broken. IEEE survey data shows 73% of EE employers can't fill positions within six months, up from 45% five years ago. EE Times has reported specifically on the RF talent gap and its growing demand.
And it's not just direct competition for RF roles either. RF and semiconductor careers often pull from the same shrinking pool of EE graduates, and right now the semiconductor side is in a hiring frenzy of its own. The CHIPS Act has poured billions into domestic fab expansion, AI chip demand is exploding, and the semiconductor industry is projecting a 67,000 worker shortfall by 2030. All of that competes directly with RF employers for the same talent. When everyone is fighting over the same small group of EE grads, RF companies, which tend to be smaller and less visible than the big chip fabs, often lose out.
Salaries reinforce this. Average RF engineer comp is pushing past $130K, with top-end design positions listing above $200K.
The real signal to me is what companies are doing about it. Mini-Circuits and Keysight are investing directly in university partnerships because they can't wait for the academic pipeline to refresh itself. Baylor launched a new Graduate Certificate in Microwave/RF Engineering in 2024, one of the few new programs I've seen pop up, but I imagine it won't be the last. When industry starts building its own talent pipeline, that tells me the shortage isn't a blip.
I don't want to oversell this. I don't think RF is going to become a field with an insane growth pattern. The BLS projects 7% growth for EE broadly, faster than average sure, but not a hockey stick. The demand is real, it's coming from multiple directions at once, and the supply is genuinely constrained.
My own path is a small version of this story. I came in as a software engineer and had to learn RF on the job because there wasn't someone else to hand it off to. I say this as someone who made that transition, you absolutely can learn enough RF to be effective in your role, and I'd encourage anyone in aerospace or wireless to do it (honestly it's a fun niche to get into anyway). But there's a difference between understanding link budgets and SDR anomalies versus designing a phased array from scratch. The latter takes years of dedicated focus. The underlying physics (electromagnetics, thermodynamics, materials science, manufacturing tolerances) don't reduce to algorithms. You have to build intuition for it, and that's not something you can shortcut.
I may one day expand on learning this stuff on the job and on the fly, but I do want to shoutout PySDR. It's a free resource built exactly for software engineers. It uses Python as the bridge between hardware and software concepts, and starts with no RF knowledge assumptions from the beginning and doesn't spend a ton of time over explaining the math.
The people who stuck with RF through the lean years are now some of the most sought-after engineers I've come across. And for anyone trying to figure out where to focus, either as a primary discipline or as a secondary skill set like it was for me, I think RF is worth a serious look right now.
Who Am I?
Anthony Templeton is a software engineer passionate about high-performance computing and aerospace applications. You can connect with me on LinkedIn or check out more of my work on GitHub.