cbcam

Thankfully I didn't need very deep EE/radio knowledge to get up to speed in my role. It's sufficient to be able to read an EE paper and extract out the end result. For example: one of our hardware guys wants me to simulate a phased-array antenna. They hand me a paper that derives the gain calculation based on the geometry of the array. I don't need to understand the derivations as long as I can translate the result into modelling software.

On the software/networking side of things the biggest change is working with protocols other than http.

I work in RF comms. Most of my work is in network simulation from the transport layer all the way down to the physical layer to prove out radio performance before expensive flight testing. I also work on error correction schemes as the networks I develop may be lossy compared to the internet at large.

I used to work in web dev, but I enjoy my current work a lot more. Most of my web role was just taking mockups from the UX team and translating them into code which felt mindless. Now I get handed a system and am asked to squeeze as much performance out of it as possible which I find much more interesting.