Slashdot Mirror
Is Network Engineering a Viable Career?
An anonymous reader asks: "I'm fresh out of high school and interested in getting a job in networking. One option is a degree in networking, the alternative I've considered is just getting certificates (CCNA/P, A+, MCSA). A large factor in my decision is which route is most likely to land a secure and well-paid full time job. I'm located in Melbourne, Australia and I don't have any local contacts in the industry who can advise me, and so was hoping some other Australian (or international) readers could share their knowledge and experience with these issues."
I'd recommend you go to school.
Whether you go for networking or psychology is up to you, but the people you meet in college and the opportunity to interact with the faculty is not an opportunity you should pass up... Assuming it's an option for you without too many negative consequences.
Get a degree in Computer Science or Computer Engineering, whichever you find more interesting. Then go do the job you want to do. I've never even heard of a degree in "network engineering," and the last you want on your resume is something that makes a prospective employer say, "What the heck is that?"
Or if you don't want a 4-year degree then go the certs route. But understand that by skipping the degree you're skipping a lot of non-computer knowledge that you'll suffer for and limiting your future job prospects. Guys with certs only get no respect. More often than not, its because they don't deserve it.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
I've learned quite a few things in my days since college, and I've learned that what I thought I might want when I was younger has now changed drastically. Now, on to my point to assist you: I am currently clawing my way up the "Network-admin" ladder at my current place of employment, and I'm loving it. I would have to say though that before you can become a true network engineer (especially for a large company) you have to truly understand the business and get a feel for what direction you need to help it grow. I've done my share of PC admin, phone support, ACD server support and the like, and it's all helped to build my backround into a solid all-around good person to have around... and all of that background helps me in more ways than I can count when I go to troubleshoot a networking issue with something like Oracle etc.
:)
Once you get your degree (yup, go to college or some other form of post-high school training) then get your foot in the door somewhere doing something supporting the end devices first. It may seem like menial work, but you'll thank me for it 5 years from now....
Karnal
If you want to go into networking get your aaaociates in Network Admin. I got my associaties in Network Admin and my bachelers in Computer management and I make $50k a year right out of college for a public library. I say go for the associates in Network Admin
I am an aussie IT consultant currently working overseas.
I know the local market very well.
My email address is published.
Berny
Curiosity was framed; ignorance killed the cat. -- Author unknown
Get the degree. The contacts you make in University alone will make it all worthwhile. There are lots of resume bots that will reject you out of hand if you can't tick off the "degree" square on their form.
Certificates will help, but not too much. The A+ don't mean squat. A CCNA/CCIE and CISSP are the good ones to have.
Remember, the people that invented things like TCP/IP, Sun, Cisco and Microsoft all met at University. While some dropped out, they still attended and made contacts there. They don't call it BSD for nothing.
Charles
Network Integration Engineer
Learning HOW to think is more important than learning WHAT to think.
Get an electrician's license instead. You're still stringing wires, but the pay is better and it's often unionized.
Go find someone with a Fortran Cert from the 80's that has never gotten a degree. Then go find someone with a CS degree in the 80's, that used Fortran heavily in their classes. Both have probably changed their skill sets drastically over 20 years, but I bet I know which one has the better job...
What are we going to do tonight Brain?
Odds are, you just suck.
Hi,
I am in my early 30's and I am currently the most Senior Network Engineer for one of Canada's top 10 largest Financial Institutions (banks). My experience & advice differs signficantly from most people's apparent armchair advice in this slashdot thread. I seriously question how many of the user comments here are actually from "Network Egineers" as opposed to "Systems Administrators" which are often also titled "Network Administrators" but whose responsibilities are primarily managing server/software as opposed to managing switches, routers & firewalls.
In my 10 year career I've worked on over 5 different National and even International Networks (including Telco's & Cable companies), one of which I even designed from scratch, and specifically I've worked on some of Canada's largest networks (easily in the top 25 list). I'm stating this not for bragging rights, but simply to say that my advice comes from direct experience in the field.
Here's my advice to you:
1) Try before you buy - Above all else, you should choose this career path because you like the day to day work it involves. Money & fancy titles should be very secondary considerations. So if you are serious, by all means try it out, but possibly try to get some student co-op work or even some entry level work with a small company first, before you spend your parents life savings on a 4+ year education.
2) University Degree vs Certification - Believe it or not I have neither! Not a single cert (albeit I've taken over 10 different Cisco courses, a few Lucent courses, and even 2 or 3 Microsoft courses earlier in my career). Here in the West Coast of Canada experience is king!
2a)The problem with degrees & certifications: In my grade 12 highschool days (early 90's) there was no such thing as a "Network Engineer" degree. To this day, the local University only offers Computer Science and Computer Engineering bachelour degrees, albeit they did introduce about 5 years ago a 2 year diploma program for "Network Administrators + Security" (I forget the exact title, but it still wasn't purely network engineering). At the various jobs I've had, people who walk in off the street with zero experience just a bunch of fancy certifications or computer science/engineering degrees are often either rejected work or given only very entry level positions. Why might you ask?
Certifications: For the most part people who have lots of certs, have lots of theoretical knowledge but no PRACTICAL & REAL-WORLD experience. Try as they might, no certification test & simulation scenarios will ever perfectly simulate some company's network because they are all just so wildly different - so if you walk in off the street with a cert, you'll be expected to spend at least 1 or 2 years learning the network before you would be given any high level access & responsibility. On the plus side, one might argue that Certifications give you very specific training that can and often is key to understanding the niche job world that is network engineering. On the negative side many vendors (i.e. Cisco) still have courses that are 2, 3 & even 4 years outdated. I.e. The course material no longer reflects the actual products & services that urban city companies are purchasing & implementing. I.e. CCNA still teaches RIP, ISDN & Frame relay... all very much dead technologies here on the West Coast of Canada. Mid to Large companies are all running fiber optic links either switched or dynamically routed (OSPF) over ATM or MPLS Telco networks.
University Degrees: The problem with having a University degree is that graduates have almost no *** PRACTICAL *** knowledge of how basic computers or networks actually work. Ask a Masters Degree Computer Science graduate how to install a DVD drive in their PC and they will look at you with a "I don't have a clue" kind of look. Ask them to write a software driver for a DVD player and they will ask you "which language do you prefer I write that in?". Some of them can barely figure o
No trees were killed in the making of this post; however, many trillions of electrons were horribly inconvenienced.
The degree is worth it. I first went to a technical school. Then decided I wanted to get a two year degree from PSU in networking. After my third year I decided to go on for my 4 years in college from seeing various friends graduating and where they were ending up. I lost quite a few credits in the move (and am now graduating with 140+ credits), but I did finish it in time. If you are like me a four year degree will not teach you a whole lot of technical stuff.
Being that you read Slashdot and probably can network computers and run 5 OSes on your computer at once you probably have a strong base of technical knowledge. I would say I learned very little and really only filled in my technical skills, but what I learned is invaluable. I learned that there is more to IT then setting up a router or configuring a computer. I learned how to handle IT and make it useful to people. I learned how to handle business. I learned to manage a project. I learned to learn.
I had a job interview for a BIG company that pays amazingly well in DC who doesn't even interview people w/o bachelor's. My interview started with the interviewer telling me that he went to PSU and that he thinks people from my major are the best things sliced bread. I landed a nice job with great benefits. I plan on going to grad school now for information security, which this company will pay for. I went from two year to 4 year to 6 year. Learning in IT is never ending the quicker you learn that the better. Certs will help, but nothing beats a degree. Most people with degrees will probably have the same certs as you anyways as they are really easy to get with a base of learning like a degree.
My suggestion go for 4 years and make the best of it!
and get a computer science degree if you want to work in the computing and network arena. if programming isn't your bag, look into an information services degree(usually a masters). i've been doing IT for the last 15 years without a CS or MIS degree(bachelors of science, industrial design), and most of the folks i know professionally don't have computer/network specific degrees or certs... we all learned from the school of hard knocks. what did help was the college experience and the ability to explore, make friends, have fun, get laid a by hot college girls(or boys) and generally fuck around.
on a side note: since your from down unda, you should know that you country has a pretty interesting tech history... one of the first ATT system 6 unix non-PDP ports came out of wollongong university.
three can keep a secret, if two are dead - benjamin franklin
Am I the only one who thinks the title of this thread is stupid? Of COURSE network engineering is a "viable career." That wasn't even the question.
Getting TO THE QUESTION:
You are always, always, ALWAYS more employable and more promotable (not to mention more PAYABLE) with a bachelor's degree than without. It is ALWAYS worth getting a bachelor's degree. I might go so far as to say it's also always worth getting a master's degree too, as MSs are becoming the new BSs.
+++ATH0