Going Back to Engineering?
JoeLinux asks: "I am a Systems Engineer for a Big Engineering Company(tm). I've been in the position for four years after getting my undergrad in Electrical Engineering. I've finally come to the conclusion that I will never see any form of technical challenge despite the continued promise of such. The problem is that almost all engineers usually make the transition the other way (E.E. to Systems). Seeing as Systems is looked at as a possible gateway to the dark side (Management), is there any going back to 'real' engineering? Have any readers successfully made the transition? How do you justify what would typically be considered a step back?"
If you have saved some scratch during your gig as a System Engineer I would recommend going back to school for a year or so to get your masters degree. Most EEs that I know(anecdote alert!) anyway say that pretty much a masters is essential, if not at the very least a career booster. Plus it would get you back in contact with some interesting technology and give you a "fresh start" in the eyes of companies.
Monstar L
Our professor, along with a guest lecturer who runs the Career Management Offices (or something like that), both said that many jobs now are offering contracts that will "promise" to allow for engineers to stay in engineering and not get bumped to management, while also getting continued pay raises and promotions, so they aren't just getting stuck in engineering with no chance for advancement.
The problem that I've seen is that there is the opportunity to stay in engineering, but there aren't as many opportunities. There may be 2 or 3 technical/engineering spots in the upper management areas, but there are 10x as many "regular" spots. So, yes - you can get raises and promotions staying on a technical track, but not as much or as fast as on a more traditional management track.
Reading code is like reading the dictionary - you have to read half of it before you can go back and understand it.