Live data from Hacker News

The quiet resurgence of RF engineering

atempleton.bearblog.dev

11–20 of 160 posts

Re: The quiet resurgence of RF engineering

#11
post #3

> 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. 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…

Also ignoring the massive new market that has been automotive radars which, as a market, have totally eclipsed weapons

Re: The quiet resurgence of RF engineering

#12

I'm one of the young(er) few who stuck with hardware out of passion rather than follow the comfortable allure of software that all my peers did. 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 fa…

These all sound like factors that make hardware a better long-term prospect to build a career around. Basically every single thing you just mentioned makes the field more resistant to automation.

Re: The quiet resurgence of RF engineering

#13

I agree broadly with the author but I think they miss the fact that American EE supply is not going to grow at e.g., 7% year over year. The infra for training new EEs, that is, the technical university, is losing the societial investment and public policy that made it possible.

Do you really think that the university is going to be the bottleneck? I have to imagine that sometime in the next decade, 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. Credentials are going to become less important, standardized testing and examination far more.

Re: The quiet resurgence of RF engineering

#15

I'm one of the young(er) few who stuck with hardware out of passion rather than follow the comfortable allure of software that all my peers did. 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 fa…

These all sound like factors that make hardware a better long-term prospect to build a career around. Basically every single thing you just mentioned makes the field more resistant to automation.

There are far too many Asian electronic engineers for NA or EU based craftsmen to gain easy living. You have to make a viral product and find a way to satiate the demand, to find similar success to software & AI bros.

Re: The quiet resurgence of RF engineering

#16
Author here :) glad this sparked some discussion. A few folks raised the geographic scope and consumer RF side, which are fair things to flag. I tried to cover automotive, 5G, and IoT in the piece, though looking back at this, I could've framed the opening more clearly, as it was more a gut feeling specific to my US aerospace / defense experience rather than a universal claim. That context should've been clearer from the start. Still learning/new to writing more publicly so knowing where the framing didn't land is super helpful for me going forward

Re: The quiet resurgence of RF engineering

#17

I'm one of the young(er) few who stuck with hardware out of passion rather than follow the comfortable allure of software that all my peers did. 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 fa…

These all sound like factors that make hardware a better long-term prospect to build a career around. Basically every single thing you just mentioned makes the field more resistant to automation.

Except for "You make less money, often half.", which is a hell of a pill to swallow. As someone ~10 years into my software career, I'm pretty confident that even if I got laid off tomorrow and never found work as an engineer again, I'd still be better off now than if I had stuck with ME or EE as I originally planned.

Re: The quiet resurgence of RF engineering

#18

I'm one of the young(er) few who stuck with hardware out of passion rather than follow the comfortable allure of software that all my peers did. 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 fa…

I kinda want to join such a company as a software guy, but I really can’t take a 50% pay cut. This is really sad! Have always wanted to work at places that can grow very solid engineering cultures.

Re: The quiet resurgence of RF engineering

#19
post #3

> 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. 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…

Even in defense, the advancements being made in fields like radar are incredible.

Re: The quiet resurgence of RF engineering

#20

I'm one of the young(er) few who stuck with hardware out of passion rather than follow the comfortable allure of software that all my peers did. 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 fa…

I started my career in embedded at an RF company. Back then, I was 20 years junior to the next oldest guy and he was 20 years junior to the rest of the engineers. It was an incredible place to start, learning from some crusty old veterans who were pushing into retirement age. I ultimately left because the pay wasn't there. I've often thought I'd love to go back, even if it meant a decrease in pay, because the environment was so rich with learning and experimenting.
Post reply on HN