* There are more programming jobs out there than hardware jobs. Hardware maintenance and design is rapidly becoming a commodity skill. Higher-end design, say something that involves multiple cities, sites, security and network priorities still commands good pay and progressional respect. If you’re in a hardware-based job (network admin) then you need to ask yourself “what’s next”. The days of fast networks, defacto standardization of IP and the Cisco juggernaut have made the network admin job almost too easy.
* Don’t study for the job you have, study for the one you want. A few certifications are good, too many are bad so if your’re studying to be a CCIE, then you need to have an idea of the job you’re trying to get before you start down that road. If you’re a CCIE at a company that has no need for that knowledge, then you’ll become a liability. You’re overqualified for your job, no possibility for career advancement and your boss will likely be wondering if you’re heading out the door to the next place.
* If you’re not willing to move to a “top tier” tech city, then don’t become a “top tier” geek. Some software companies will tolerate remote talent, but most want their teams working together, eating pizza and losing sleep within 10 feet of each other for weeks at a time.
In the next post, we’ll talk about the businesses end of your career.