Interesting to think those were the kind of jobs, and CISCO the kind of company, that once gave Silicon Valley its name. Makes you wonder how the market for software engineers, even adaptable always-learning hack-through-the-night-for-fun engineers, might look in 20 or 30 years.
[1] Read "(low-level networking systems) engineers", not "low-level (networking systems engineers )"
In my profession (banking), staff levels have been going pretty much consistently down since the financial crisis, as banks shrink or retreat from certain activities. But these are mostly bright, educated, business savvy people, who end up doing something else. For many it is a blessing in disguise, an opportunity (albeit in a brutal way) to move away from a shrinking industry to become their own boss or to work on the next big thing.
Imagine what a guy makes that's been at Cisco for 15 years? Now imagine what you can pay a recent graduate or H1B.
There must reach a stage in development where you're considered "too old" (sadly) or haven't kept up with the latest and greatest in trends.
What do you do then?? Project manage? Do all developers move into project management?
I see this mildly where I work where older developers are greatly valued (they're good!) but haven't kept up to date, eg. a lot of C++ is here, but nobody here (and I mean nobody) has any understanding of C++11, C++14 changes and are stuck in the C++98 ways. They even call C++11 "C++0x" still. This is different to the "learn the next fad" approach, as C++98/2003 deserve to go away.
MFC anyone?
With the push to Universal Apps (that nobody appears to be heeding), what is Microsoft's recommended toolkit for C++ in Windows now eh?
Here we are with > 2 million lines of C++, entirely MFC and COM.
Just imagine how much knowledge and experience these guys have and is effectively being lost by them being out of the workforce.