In my long and storied IT career (haha!), I have seen many rounds of Reductions in Force (RIFs) and layoffs. When a company sells a division, spins off a business, or shows less-than-positive revenue, we invariably see some people, deserving or not, get their walking papers. I have to be completely candid and say that it sucks when there are layoffs. In some cases, especially now (in the worst economic climate in 50 years), there is nothing you can do about losing your position. You may be the best of the best, but sometimes it is just your turn.
There are a lot of things you can do to make yourself valuable to your current employer and desirable as an employee should you happen to be laid-off. Fear and uncertainty can paralyze you and render you ineffective. Guess what? Being ineffective is really bad, and can end up making you a prime candidate for dismissal. Or, you can take that fear/uncertainty/doubt, turn it into motivation, and commit to constantly learning and improving.
A good friend and mentor of mine had an email signature that I probably scoffed at when I first saw it years ago. It read: ‘Success is a journey, not a destination’. Regardless of who said it, I think it is a really relevant bit of wisdom these days.
To succeed, I have to keep getting better; to get better, I have to keep learning.
But how, you ask, might you do that? Thanks for asking! Here are some things I find important to combat uncertainty.
- Set professional certification goals for yourself. Ever heard the term ‘paper CCNP’ or ‘paper MCSE’? Yeah, me too. Certifications never guarantee you a job, and if you are not really an expert at the subject matter and claim to be, you will be exposed in short order. On the other hand, if you are a hard worker, have good references AND relevant certifications, you just might get a foot in the door. If you are not worried about losing your job, I believe it’s still vitally important to have cert goals to work toward. Certifications are a benchmark of your ability to learn material and pass a test, but certifications also show that you are willing to make an effort on your own time to acquire new knowledge and skills, to make an investment in yourself. I also strongly believe that you have to set cert goals for yourself; if your boss is setting the goal for you to become CCNA-certified, that is external to you and I feel you are not as likely to follow through and succeed.
- Learn a programming or scripting language. This is very specific, but I can’t stress enough how important it is to show your current or future employers that you are versatile and can use your knowledge to innovate and automate. Being an expert in Cisco IOS or Juniper JUNOS is really great, but knowing how to write a SHELL or PERL script to take care of some routine function shows you value efficiency and are more versatile than the guy that memorizes router commands. It has been my experience that knowing scripting and programming is a desirable skill and sought after.
- Cross train. Anybody out there old enough to remember Bo Jackson? He was the spokes-athlete for Nike’s cross training shoes in the late 1980s. He was both a pro American Footballer and pro Baseball player. His versatility was lauded. You can follow his example in your job and work closely with the folks that you support. Do you work with Linux or Windows admins? Learn about operating systems and processes. Build your own servers (VMWare and other similar systems are great for this), learn to find your way around, read the MAN pages. This kind of cross training will not only help you with learning about Cisco IOS (guess what? It’s an OS!!), but also with troubleshooting and debugging problems. Be a specialist in networking, but learn enough about the other stuff to be valuable as well.
- Learn the Theory. It’s a drag to read RFCs in most cases, but I recommend it. Learning the theory and principles behind what we do in production networks is one of the best ways to add value. If your employer changed tomorrow from Cisco to HP networking gear, would your learning curve be steep? If you have only concentrated on Cisco-specific commands, then yes, probably very. If you know the theory behind a protocol, you can more easily discern what commands, regardless of vendor, you need to use to achieve a certain result.
- READ A LOT. Most people are not readers of books these days, and many argue that the material in books is more often than not outdated and irrelevant. In some cases, that is true. Some are timeless, ‘classics’ of networking if you will, and should be read and re-read. If books are not your thing, find and follow reputable blogs. Take their content and do your own research. [I have to include a shameless, unsolicited plug: Safari Books Online is such a great investment in learning. You have access to literally thousands of books and videos. Check it out, it’s worthwhile.]
- Don’t Ignore Layer 8. Layer 8 you ask? The political layer usually, although in this case, I use Layer 8 to mean the Business Coping Skills Layer. Learn about project management and business processes related to your work. Project management is a really great skill, and in most cases, you can continue to be a technical contributor as well. Any situation in which you can lead others and add value to projects is a good idea.
So there is my take on making yourself relevant and valuable. It is by no means comprehensive, and if your employer is laying people off, it may not be possible, in spite of your efforts, to stay employed there. Be prepared, be knowledgeable, work hard, and always have a plan for when the unpleasant happens.
8 Responses
really helpful. thank u
Dear Jake,
I want to thank you for your excellent article of July 29 entitled, 'Networking Careers and Investing in Yourself.' I found the article to be extremely enlightening and highly applicable to my professional situation.
As a long-time network engineer with almost 20 years experience in IT (12 of those years consisting of hands-on networking experience), I nevertheless must admit to myself that my out-dated certifications (e.g. MCSE in Windows NT 4) place me into the *paper MCSE* bucket. Why? Because the various technologies that spawned Windows NT 4 MCSEs are antiquated and rarely used anymore Networking technologies have evolved tremendously since the day I sat down in a Prometric testing center, subnetting IP addresses and trying to pass that crazy TCP/IP 4 exam. (LOL)
As you point out so clearly in your article, Jake: "…certifications also show that you are willing to make an effort on your own time to acquire new knowledge and skills." The critical word in that sentence is *new*. Clearly, if I am to *stay frosty* (or even qualified) in an increasingly-competitive IT job market, I need to get on-the-ball and upgrade my network-related certs in order to reflect my mastery of cutting-edge networking technologies. It's not enough that I work with the latest-and-greatest – I must be able to prove my expertise to potential employers by achieving the corresponding certifications. After all: How many employers are looking for Windows NT 4/Cisco 2500 Series router experts? I'll tell you how many…ZERO!
Notwithstanding, I'm confident that through hard work and dedication, I can update my certs and remain competitive as a network engineer, no matter how old I am. So to all of you young *bucks & does* out there who tend to write-off us old-timers (you know who you are!): You might do well to keep one eye open when you're sleeping behind the racks in the data center, because some of us older guys and girls who were setting-up networks since before you were born can still play-the-game with the best of you – believe that! As long as we keep our certs up-to-date, and all else being equal, not only can we hang with the best of you , but our qualifications will always slightly outweigh yours, due to additional experience we possess. That's right, youngsters – experience can only be achieved through time-in-grade – you cannot get it by memorizing *Transcenders* or by browsing through *brain dumps*! (LOL)
As the saying goes: Old network engineers never die – they just upgrade their backbones to fiber. : )
Thanks again for a great article, Jake. You have given me a fresh perspective on how best to manage my network engineering career in the 21st century. : )
Buster Fussy
Washington D.C.
Thanks for reading this post, Buster, and thanks for taking the time to respond! As I get older, and my coworkers get younger, I know that learning is always going to be key for my success, and experience trumps reading those brain dumps every time.
I really appreciate your feedback.
Jake
Stellar article. I came into the IT world from the construction trade where being versatile and multi-skilled was a must if you wanted to consistently get jobs. I would ask to help with jobs that involved skills I wanted to learn, even if that was just to do cleanup. I would learn so much and also make great contacts for future work. I have applied this same process in my IT career and it has paid off in great opportunities and growth.
Hi Tim, thanks for reading!
Your point about doing pretty much whatever it takes to get the job done is an important one for sure. Having a reputation as a hard worker who is versatile can usually help you get the job when compared to the candidate with slightly more experience that is not as willing to go the extra mile.
Great ideas! I was let go last year after my department was outsourced and had to learn many of these lessons the hard way. I would expand on your "Layer 8" advice to include learning about the business side of whatever your company does, and get to know people outside of IT. Project Management is a great way to accomplish this.
Thanks for reading, Derek! I'm glad you like the humor.
I love it! Layer 8! ROFL, excellent posting. I recently wrote a message to someone regarding getting started in IT, and this will make a great follow up message.