Slashdot Mirror
The Best Colleges for Network Engineering?
viperstyx asks: "Ive come to that time in my life where I have to choose what colleges im going to apply to for my undergraduate degree. I'm very interested in Computer Science but I'm not sure if I want to major in Comp Sci, but I do have a high interest in networks. I hope to work on things like Internet2, or in a large business environment after college. I was hoping to find a college with a major, along the lines of Network Engineering, but I have yet to find one." What colleges have the best programs to prepare prospective networking engineers for the future?
RIT? I like the EE program, and a lot of CS students I know like it here.
Study CS in undergrad. Wait until Graduate School to specialize.
Badass Resumes
I really don't feel you have to focus on exclusivity to Network Engineering. I feel that most schools with programs in Network Engineering are not the most recognizable. I suggest you focus on a CS degree or a computer engineering degree. If you perform well in either of these fields you should be able to land almost any job in the industry. Recruiters look at your college record and see what kind of person you are based on your grades, difficulty of classes, and experience gained. The actual information learned is rather insignificant to the kind of person you are.
They have the entire range of Cisco certification classes.
You also may want to consider something in telecommunications as that covers a lot of networking as well.
And then you can still apply for work outside of IT.
I suggest you go with the college/CompSci degree, then spend another 6 months to a year in a certification-type place getting things like A+, Network+, Cisco basic certs, and some linux/unix sysadmin basic certs (the latter cause most linux/unix sysadmins know networking a lot better than most MCSE types since they are network-centric OSs from the get-go). And depending on where you go to college, many colleges let you take tests for *life experience*, so if you got some network-related certs while in college, you might be able to have them credited and not spend as much time.
I think college, in fact, is overrated in a lot of ways, putting yourself 60K in debt is not worth it. I'd recommend a cheap state school if possible, or community college for the first two years of college. Keep in mind, a lot of people change their minds after two years in college, and decide they want to do something else (or may just not like the field).
Moreover, I think technology is becoming extremely competitive. Better to try a field like nursing or maybe look for something in biotech.
In any case, if you want to do something in technology, be prepared to study hard and keep learning, tech is one of those fields requiring constant reeducation to maintain an edge.
Disclosure: I am a CS professor (in comp bio, not networking), and my department (WUSTL) is well-known for networking-related research.
If you want to get into stuff like protocol design, routing architecture and algorithms, and the other "guts" of designing and building high-speed networks, consider a CS or Computer Engineering degree. Besides the obvious courses in networking per se, you will have the opportunity to study algorithms relevant to the area (e.g. minimum spanning tree, network flows, suffix trees and other fast string matching methods for routing tables); hardware design (for building gigabit-and-up routers and other cool network gear); and design of large software systems, including the principles behind distributed systems like the DNS and peer-to-peer networks.
Depending on where you go and what your interests are, you can also bone up on the underlying math (e.g. queueing theory for protocol design) and maybe even some physics/EE (signal propagation, etc).
Yes, you can probably work your way to a strong practical knowledge of how to build a network, and getting your hands dirty is essential to success. However, the point of a CS degree is (1) breadth in computing fundamentals, which I hope I've persuaded you are relevant to networking, and (2) quickly getting up to speed on how to *think* about networks, independent of any particular protocol or hardware standard.
Oh, and speaking of getting hands dirty... if you go to the right place, you might be able to get on board a networking-related research project!
I did exactly what he said. I got my hands on the higher end cisco routers/switches by working at Portland State University (located in Oregon) for $8 an hour. And used that knowledge to get a CCNA. Then used that CCNA and experience to get a job making good money without a college degree.
I got to work underneath a very bright person (lead network engineer), who in my humble opinion provided me with a lot more useful information than a lot of the teachers did when I was a student there. I got to work with a large campus lan that used VLAN's, 802.11b (when it was $700 for a cisco base station), and even Internet2.
Basically, I highly recommend getting a job at a University in the NOC or IT operations, as what the jobs lack in pay is made up with copious amounts of resources and experience.
Firstly, congratulations on wanting to go with a real degree before jumping into the networking field. Its the way to go if you want to have any future beyond "button pushing lackey". Your entry level CCNA job has already been shipped to India, shoot higher.
There may not be a specific "Network Engineer" degree at all universities, what you want is to study Electical Engineering, add in some Mathematics (queue theory, statistics), and top it off with Physics (optics, particle physics). All of these elements are required to actually understand what is going on with networks. Specific topics to concentrate on include circuit design, transmission lines, antennas, material science, compiler design, signal processing, queue theory, and statistics, lots of statistics.
If you want to be the guy who actually writes new RFCs to be used by everybody else, gets hired by companies like Cisco to create new routers or protocols, and be the chief designer on world spanning networks, ignore the certificates for now. Concentrate on getting the background information necessary to understand all the aspects of network design, like speed of light limitations, electrical characteristics of transmission lines, radio circuits and complex mathematics. Picking up a cisco certificate will then take a week of your time when you are ready to join the workforce, and you'll know not just the HOW, but the WHY.
There are a ton of CCIEs on the market today, those without university degrees are flipping burgers or repairing PCs. The interesting work, such as creating optical switches or ultra efficient routers, can only be done by people with advanced degrees. The cert holders sit in the NOC at 3 AM, working their way through a never ending stream of trouble tickets, wishing they had a real degree to get a real job.
That said, from my experiences with US university grads, I'd recommend UC Berkeley, Purdue, CalTech, or UoWashington.
the AC
who just let his CCIE expire, because its worthless in todays job market
Hemos is like...sci-fi fans;he thinks technology is cool, but he hasn't bothered to understand the science it's based on
One of the best things about going to a school like Harvard or Stanford is that many of your classmates are wealthy and connected. During your program at school you will have many opportunities to form networks with fellow students, their parents, and alumni who later in life will be able to get you a job.
Not a very well known school, but it's a campus of both Indiana University and Purdue. I suggest checking out the Informatics major. IUPUI also has a part in Internet2. I'm not sure of the details, as my area is bioinformatics, but there's something under the library :o).
Otherwise, you may also be interested in Purdue's CPT program. They offer a Network Engineering Degree. Purdue is perhaps the best engineering/tech university in the midwest, maybe even east of the Mississippi. In fact, maybe even east of California. And unlike IU, their football team doesn't entirely suck.
Plus, Indianapolis has lots of things going for it for someone in the industry. Plenty of large companies that need tech workers (the headquarters of Lilly and Conseco and Thompson Consumer Electronics North America and Simon Property Group - the world's largest mall owner) as well as many regionally strong tech companies.
Yes, I'm a little biased, but for good reason.