at least if you're interested in actual electronics and development.
There's a simple reason for this advice:
Nowadays, this job is all about (in descending order of importance) business, money, bureaucracy, policies, compliance, standards, ..., customer, knowledge, skills, electronics.
When I started my career in the electronics business about 25 years ago, my work was about developing a working system, consisting of analogue electronics, analog to digital conversion, a digital microprocessor system, power supply for the whole stuff, making firmware to get it running, doing the layout, assembling the first prototypes myself, testing the stuff and continuously improving the system according to the needs of the customers. There were good times and bad times, of course, business was sometimes good and sometimes bad, the boss managed to bring the small company through bad times and we all (about 10 employees) enjoyed the good times.
Today, I have a job in a larger company (maybe 400 ... 600 employees here and half of them doing real work, the others are managers
). Some fourty to sixty developers around here. The stuff I have to deal with now is: Comply to corporate policies, take care to fill forms formally correct, for a single project I had to deliver a number of proposals that basically did the same thing but in a slightly different way to enable managers to (not) make decisions based on the estimated component cost of each proposal, sitting around and waiting for them bring up some requirements for the new product, transforming their poor quality requirements into formally correct requirements, throwing away these results because the managers decided otherwise, beeing forced to repeat some integration testing done four years ago just because the new applicable standards requires to use calibrated equipment that was calibrated by an accredited lab, not just calibrated as the former standard required, and so on.
I've done some "real" electronics development there, but on a specialized area, mostly subcircuit level (admittedly on a non-trivial level), not a whole product as before. I've got a good knowledge on a rather wide field of electronics, mainly because I refuse to stop learning, experimenting and designing stuff for my own, but it's not required to do my job. Once you are established in your special field, that's your job forever here. If there's appearing a new field of development, the company prefers to hire a new person over asking their employees (OK, that's the way I got my current job for a new field back then, but I didn't know about this practice then).
Looking around, and talking to friends that are also working in comparable jobs, apparently this is the situation nearly everywhere, so just changing the job / company doesn't look too promising.