[papaf]

I actually did this switch 25 years ago for the same reasons. I studied Microelectronics in the UK and I was the first in my graduation year to get a job - 6 months later, by switching to software development (CPU and graphics card benchmarking).

It sort of worked out OK but I have regrets. I grew up wanting to be a hardware engineer but I'm not one.

If you switch to software development, I would recommend that you stay as low level as possible. I recently got back into embedded development and I became a lot happier because of it.

Good luck.

[HLRoku]

Thank you, I appreciate it. I was thinking that if I stay relatively low level or do arduino and FPGA work on the side, my EE fundamentals can transfer and mix with my software skills at any many jobs, such as embedded engineering or even wireless, as my current focus in EE is RF.

It just kind of sucks that in America it doesn't seem like there are any "true" hardware jobs, and the ones that are around pay extremely little or are VLSI software based. If I knew this in detail when I started EE I'd probably have hesitated upon entry.

[batou]

That's kind of scary as it's exactly what I did. Same course, same country, same time :)

I'd agree with the embedded side though. The business side is a shit sandwich I really wish I hadn't got into.

[HLRoku]

I'm honestly comforted to see this being a common thing among posters here. And I agree, as I look into my company's chain it just gets more business focused the higher you go, and that's not what I became an engineer to be.

When I make the switch, I'll be sure to not let my RF/EE background fade to the background, as I believe it can be a strong asset.

[batou]

It will be an asset. The most successful team in my company is built out of mechanical engineers, electrical engineers and mathematicians.