Making the Jump From Sysadmin to Network Administrator?

termdex asks: "I've been looking to move from systems administration to network administration for the last couple years but for some set of reasons networking seems to be an impregnable area of work. My experience has been like the often clichèd 'chicken and egg' scenario. Most employers aren't interested in candiates that lack serious network admin experience (ie: 80/20 network/other), but it would seem difficult to get that level of experience if you're currently a sysadmin. What advice can Slashdot readers offer as what works best in making lateral career moves? What experiences can you relate that shows difficulty or success?"

Comments

Re:But..

[pretzel_logic]

interesting point...

I created our CRM, admin the offsite Linux servers, sysadmin the macs and pcs. Handle the network. troubleshoot anything that gets plugged in to the wall. I make all the clients web sites, admin the databases, and write then CRM's.

I go offsite and set up LANs, do customer support for network and operations. I handle buying and purchasing bids for multiple companies, and do sales when I am needed for consultation at the conference table.

my title is 'tech guy' I have no degree and no certs. only skills and proof of skills. I am over qualified to work for large companies but under qualified at the same time. Its just one of those things, my advice is this:

do what makes you happy and follow your dreams.

dont lie on a resume. it will only backfire. dont list buzz words. instead make a list of things you have done.

Go work for a small company

[bill_mcgonigle]

You're stuck because you're in a big company where they actually have different people for network and admin jobs - that's your problem. Go work for a small company, where everybody wears at least 5 hats. If you really want to, you can go back to the corporate arena after a few years with any of those 5 job titles on your resume. I bet you won't want to, though.

Find a "bridge" position in a Corporate IT shop

[bofus]

If you're trying to move from a "pure" OS position directly into an "IP routing and switching only" type of job, you'll probably find it difficult. Especially in today's job market.

I run a corporate Network support group that handles LAN/WAN technology, and my staff of 8 is mostly people who have started out as sysadmins and developed their networking skills along the way. The value this background brings is that their general OS and application knowlege allows them to troubleshoot beyond typical "Layer 2/3" problems. It also provides a more open interaction with our sys admins, who do not have routing and switching expertise. We do have several router geeks who focus on our IP routing and LAN/WAN switching infrastructure, but it's the folks with the mix of general OS and specific networking skills that keeps our DBA, progammer, and system administration customers happy.

If you're trying to get into a ISP or Telco NOC, you'll probably have a tough time, without demonstrable routing and telecom experience. OTOH, if you can find a corporate IT shop that supports a variety of technologies (WAN/LAN, Security/Firewalls, Internet, Data Center, etc), you can exploit you sysadmin knowlege in a networking environment. Make sure your resume highlights your relevant networking experience.

Some of my best overall Network Engineers came to me as Unix or Windows admins with a general understanding of networking, and a strong desire to learn more. We're not shy about providing training, and after 6-12 months we end up with very effective engineers who play nice with others. :-)

Good Luck!