Monday, August 10, 2009

Career Advice From a Networking Veteran

It’s hard to believe I’m a veteran of computer networking, but the facts are indisputable:

X

Performed an IGRP to EIGRP Conversion on a Production Network

X

Significant Work on a Token-Ring Network (Not an Ethernet Conversion!)

X

Passed CCIE Lab When it Was Two Days Long

X

Holding Shares of CSCO With $60+ Per Share Cost Basis

(Sadly, the Cisco shares are in my son’s account. I guess I’ll owe him a few dollars out of my bank account when he’s ready to spend the money to make up for that decision!)

While I don’t feel too old, I must have enough life experience to ‘give back’ to the next generation of Networkers. So here’s my attempt to help out.


Early Career

If I could make only one recommendation to early career network engineers, it would be to get certified. CCNA, CCNP, whatever.. The job market is too crowded to not have some sort of credentials attached to your resume. I’ve been on both sides of the hiring game. Without some sort of certification, you need an extremely strong social network to get your foot into most doors. There are too many HR-provided ‘resume filters’ in place now.

One of my most recent hires came to us without any certifications. In almost all circumstances I would have dismissed the resume quickly. Fortunately for us, the candidate and I had worked at the same consulting firm a decade ago. Although I didn’t know him personally, I was able to reach out to a former colleague, who contacted the candidate’s former manager. After an excellent recommendation, I was willing to put my trust in the candidate’s resume and after a series of positive interviews, we made a great hire. If it were not for the common former employer, I doubt we would have had the confidence to make the job offer. Our organization would have been worse off for it, but the costs associated with making a bad hire are such that I needed to be extremely confident to make an offer. My assumption is that if you are in your early career, you haven’t had time to build the necessary social network to overcome the lack of a certification.

A second recommendation is to immerse yourself in the subject matter. Create a structured study plan and execute it. When I began working in this industry in 1997, I knew very little about networking. I was put into a ‘sink or swim’ situation, as the two engineers who previously managed the company’s network had both left with little notice. I started in June of 1997, and went to the ICRC and ACRC at Chesapeake Computer Consultants within the first two months. With those courses as a base, I decided on a study plan of reading the (then current) IOS 11.2 Configuration Guides from beginning to end. There weren’t a lot of study materials available at the time, so I made the best of the situation. As a college student finishing up my Senior year, I would print thick sections of the documentation and bring it to my classes to read. I don’t know that this is the best study method today, given the abundance of targeted study materials available from Cisco Press and others, but it worked for me at the time. I ultimately passed the CCIE lab using this method. For a current example of a structured study plan, I suggest you follow Aragoen Celtdra’s Route My World blog. I used a similar method when I pursued the CCDE written and practical exams.

Mid Career and Later

The studying and reading only intensifies once you achieve your CCIE certification. If only someone had mentioned this to me in 1998! Like all successful CCIE candidates, I was on top of the world after passing the lab. I was sure I was an expert my field; after all, that’s what the ‘E’ stood for! I decided to interview for a position with Chesapeake Computer Consultants. That’s when I found out how much I didn’t know! While I did ultimately received a job offer, I was astounded by the depth of the technical interviews. It was at that time that I realized my chosen profession required constant study to maintain relevance. The CCIE recertification process reinforces this, and that’s why I don’t have any issues with sitting for a written exam every two years.

My recommendation is to constantly seek positions which challenge you, and hesitate before trading opportunity for money. I spent over three years in a lucrative contracting position, but during this time I didn’t learn very much. I sort of missed the MPLS revolution, and I’ve been catching up ever since. I even took the easy way out on my CCIE recertification by repeatedly taking the CCIE WAN Switching exam, which didn’t appear to change at all from 2000 until 2003. Money is an important thing in life, so while I would never advise someone to turn it down, I would highly recommend weighing a slight increase in current dollars to the impact a position will have over your career. I didn’t do irreparable harm to my career, but I certainly set myself back a bit by narrowly focusing on older technology. On the plus side, I worked with an incredible set of people and built wonderful relationships that eventually delivered me to my current position.

A more controversial suggestion is to strongly consider changing employers as you work your way up the salary ladder. I have seen first hand that it is extremely difficult for an employer to keep up with high performing employees. Most corporate salary structures are not designed to cope with the rapid increase in value delivered by such employees. I found it necessary to leave my corporate employer after achieving my CCIE certification for this reason. I ultimately decided that although it would be difficult to leave, it was unfair to my wife and child to work for less than market value. This was perhaps the most difficult professional decision I’ve made thus far, but in retrospect, it was clearly correct. This is less true in the consulting world, where it is easier to judge an employee’s value. Under most circumstances, bill rates are a strong proxy for value. Consultants can easily demonstrate their value by increasing the revenue delivered to their employer. For a fun example of this, take a look at this Game Theory view of salary negotiation: http://mindyourdecisions.com/blog/2009/08/04/how-to-negotiate-a-pay-raise-with-game-theory/.

Summary

So, to recap, get certified, study methodically and regularly, chase money and opportunity in your early career, but go for balance.. don’t overvalue either. Also, make sure you build lasting relationships along the way. It ultimately makes everything you do more meaningful, and adds a fun social component to trade shows and seminars. My favorite part of Cisco Live is catching up with friends and former colleagues. If you see me in Las Vegas at Cisco Live 2010, please introduce yourself!

6 comments:

Jason Harry said...

Thanks for the insight. I'm currently persuing a networking career also. Planning on going for my CCNP and CCDA next yr.

Keep posting advise like this. Very helpful.

Jeremy Filliben said...

Jason,

Thank you for the feedback. I'm planning to do another post soon comparing Corporate and Consulting jobs. They're quite different in terms of opportunity and experience, in ways that aren't necessarily obvious.

Jeremy

David said...

I'm definitely with you on the "immerse yourself in the subject matter" advice for someone starting out. My CCIE study plan back in the mid-1990's was to read the entire doc set and force myself to understand not just what every command and option did, but why someone might think they needed it. In some ways that seems harder today because of the sheer size of IOS, but the lab was much broader in those days, and that brought its own challenges. I really struggled with some of the SNA stuff that was outside my normal experience, for example.

One place we might differ is on the need to change companies as you move up the salary ladder. This might be because I live in the consulting world, where pay-for-performance is the norm.

I'd agree that changing employers should be considered, and yes, it's hard for companies to deal with high-performers, but when the atmosphere is a good one, it's a mistake to be in a rush to chase the money. I'd advise someone to prove their value with their quality of work, detail-orientation, work ethic, and ability to see the bigger picture and apply soft skills -- and not to assume that their certification can make up for lacking any of these. Certs are a plus, not the end-all goal. Also, don't assume that you can't get the salary you need where you are ... be honest about what you're looking for, and if it makes sense it may well be an option. No employer wants to lose a high performer. I've gotten raises of over 50% without changing jobs more than once in my consulting life as I went from a tech to a good engineer to a CCIE.

One other tip: if you aspire to write any books, it's a lot easier before you have kids, and establishes some level of instant credibility beyond what a certification can.

Anonymous said...

Now, that's an inciteful post!!!!!
I started out my career pretty much the same way. I worked towards getting some certs in the early days.....MCP, N+ and CCNA while still in University.

Now more than ever before, I realise that I don;t know ENOUGH.....yes I'm a CCIE, but believe me, I know I don't know enough ;-) :-)

I've started to go thru Cisco SRNDs and Admin guides all over again!
I guess the learning NEVER stops!!!! :D :D :D

PS: Plan to be in Vegas for next Cisco Live.....so would look out for you.

Pete said...

Thanks for the advice. Hope you post more about your experiences as a networking veteran. Your blog will serve as a guide to us who are in our quest for the Cisco Certifications.

Jeremy Filliben said...

David,

Those are great points, especially about writing books. In 2000 I sat down to write "Optical Networking Fundamentals" for Cisco Press. After three chapters, I had to give up. Quality of life issues got in the way. I still regret not finishing.

I agree it may be possible to find a company that can grow your compensation to meet your personal growth, but they are rare in my experience. If you find that you work for such a company, don't leave!

I may be oversimplifying things with my advice. My point of view, especially with regards to being willing to change employers, is that high-potential/high-achieving engineers are chronically underpaid in their early careers. Most companies can't keep pace with individuals in this phase of their careers.

You are absolutely right about the non-tech skills. We've all known CCIE-level and better engineers who weren't worth anything near market value because their soft skills were, umm, lacking polish. It seems in some cases, you either have those skills or you don't. If I were building a development plan for a junior engineer, I would have them focus their study efforts on the technical skills. Soft skills can/should be learned via life experience, especially if you have the right role models and/or mentors.

Thank you for the feedback!

Jeremy