Tech Support Forum banner
Status
Not open for further replies.

Careers In Networking - FAQ

Published 
235 views 20 replies 4 participants last post by  Masterchiefxx17 
#1 · (Edited by Moderator)
:stop: This page is under editor review! This is NOT the final copy! :stop:​

Edit post #2


We often get quite a few posts about networking and general IT careers, so I thought I would write a post that will hopefully answer most of your questions if you're looking to start out in IT. If it doesn't, or you have any other burning question then please feel free to ask, i'll be happy to help! Most of the info below is biased towards networking, but still useful for those in any entry level IT role.

If you're looking to start a career in networking, you've definitely picked the right choice. All other IT roles would be irrelevant without networks, and network engineers are the rock stars that build and maintain the only things that matter :)

Where Do I Start?

There are quite a number of roles available today in networking that just weren't there a few years ago. Now you can choose to specialise in security, cloud networks, service provider, storage, wireless, voice (ugh!), and so on. So which is the best starting option?

Routing & Switching. Period.

Security engineers may get paid a lot more than 'vanilla' network engineers and wireless guys get the girls :) but all those technologies rely on the routing and switching engineers bread and butter. You cannot be successful as a network engineer without understanding the fundamentals of how networks work. You may be able to build a complicated firewall configuration, but if you don't know why a host isn't responding to an ARP request then you're only going to be 50% as effective as the guy who knows how to do both. And there are a lot of guys (and girls) out there that know how and you'll be competing with them for the best jobs.

How Do I Learn About Networking?

First and foremost, networking is not a job where you can complete a certificate and never have to open another book ever again. Not if you want to be a successful network engineer anyway. Network technology is constantly evolving and staying up to date through self study is important so be prepared for a journey of life long learning. That sounds worse than it is, but if you're do something you enjoy, it's a breeze!

There are literally thousands (maybe millions!) of resources online that can help you learn about networking, and you'll find every one of those sites will aid you by explaining a technology in a way that no other resource does. There is no single definitive resource for network learning except maybe for reading RFC's which define the standards we use, but I wouldn't wish that study route on anyone!

Ask questions, and ask as many as you need to. There is no such thing as a stupid question. What's stupid is trying to do something you don't know how to do. That's applicable to all walks of life, but it's super important in networking, where an innocuous change could have disastrous consequences. Never be afraid to ask anything.

You can also use the certification guides from any of the major vendors and work towards an industry recognised certificate which will teach you 99% of what you need to know, which i'll go into further detail next.

What Certificate Should I Take, Do I Even Need One, Should I Take A University/College Degree?

Do you need a university/college degree?

This may be contentious, but from my own personal experience (and opinion), no. For me, a 4 year course is 4 years hands-on experience wasted. I do not have have any sort of computer related degree, but I have over 15 years of network experience and a hand full of certificates and it has NEVER held me back when applying for a role. I have also interviewed many candidates who have computer related degrees (and you do see this as a requirement on a lot of jobs nowadays) but if they don't know how to do the job I need them to, then they won't get the job. Degree or no degree.

All about Certificates:

You do not need a network certification to get started in networking. Certificates are great, but they really need to be backed up by experience. That's not to say you shouldn't start your certification study straight away, you should absolutely go for it, studying and getting hands-on with live equipment is the absolute best way to learn.

There are a lot of entry level network certificates out there, and some of the most popular ones include:

Cisco CCENT/CCNA
Comptia Network+

Which one is "the best"?

I would say that although the Network+ certificate is useful, the CCENT/CCNA is one of the most important network certificates you can aquire. The Network+ is very useful and does cover some topics that the CCENT/CCNA does not, but the CCENT/CCNA covers everything that the Network+ does and teaches you how to administer Cisco networks. You would be hard pressed to find any company in the world that does not use Cisco equipment in some capacity, and what the CCENT/CCNA lacks in comparison to the Network+ will be picked up as you learn anyway.

From an employment point of view I've never seen a job that required a Network+ (that's not a slight against those who hold it), most require a CCNA as a minimum for (slightly)/more experienced roles. And looking further forward in your career for a moment, most jobs are handled by non-technical recruitment consultants that don't understand the difference between BGP & EIGRP, they only know that the CCNA you hold ticks the boxes.

There is one caveat to the certification route. Demonstrable experience. On a technical interview, it doesn't matter to me whether you have certificates or not. If you can show me you know what you're doing, that's what counts. Although not required for entry level roles, don't think a lack of certificates will hold you back in the future if you know what you're doing.

For any role in IT, you need to have (in order of importance):

1. A good attitude.
1a. A willingness to learn. This is really important for entry level roles.
2. Personality. You don't need to be the life and soul of the party or a social hand grenade, you just need to be a guy or girl that I can work with. Show me it during the interview.
3. Experience. I don't need you to know how to configure a DMVPN for your first job, but if you know how ping works or how you configure the wireless on a home router, tell me! It all counts.
4. Certificates. Not important for entry level roles.
5. Your favourite sports team. This may or may not influence the entire interview process :)

x. University/college degree. If you have one, more power to you. However (and remember i'm speaking from personal experience) this has never been relevant any any interview i've sat or held.

How Long Will It Take?

It all depends on your aptitude. There is no set time to pass any exam, do it at your own pace and make sure you understand the content enough to do your job well, not just to pass the exam.

Ok I'm All Set, What Type Of Job Should I Go For?

This question always makes me smile. I think Richard Branson said “If somebody offers you an amazing opportunity but you are not sure you can do it, say yes – then learn how to do it later!”. If you think you can do the job you're applying for and can pass a technical interview based on the job requirments,I say go for it! But then again, I like a little bit of crazy on my team :)

If you know next to nothing about networking or IT in general, or perhaps lack a little bit of confidence, you'll be best served looking for roles that don't require experience.

It can sometimes be difficult to get into entry level networking roles so if you're not immediately successful when applying, keep your chin up! It happens to the best of us, and sometimes still does! My view is that a company that doesn't recognise a good attitude, and passion isn't worth working for anyway. Good bosses recognise these attributes and a good boss translates as a good place to work.

As mentioned, I'm happy to answer any questions on anything that isn't covered so feel free to ask!

Best of luck!


© 2016 techsupportforum.com



 
See less See more
1
#2 · (Edited by Moderator)
:stop: This page is under editor review! This is NOT the final copy! :stop:​

Edit post #2



Before editing this post, please make sure that you are the only person viewing this thread, as anyone else viewing the thread may already be editing the post.





We often get quite a few posts about networking and general IT careers, so I thought I would write a post that will hopefully answer most of your questions if you're looking to start out in IT. If it doesn't, or you have any other burning question then please feel free to ask, i'll be happy to help! Most of the info below is biased towards networking, but still useful for those in any entry level IT role.

If you're looking to start a career in networking, you've definitely picked the right choice. All other IT roles would be irrelevant without networks, and network engineers are the rock stars that build and maintain the only things that matter :smile:

Where Do I Start?

There is quite a number of roles available today in networking, roles that just weren't there a few years ago. Now you can choose to specialise in security, cloud networks, service provider, storage, wireless, voice (ugh!), and so on. So which is the best starting option? Routing & Switching, period.

Security engineers may get paid a lot more than 'vanilla' network engineers and wireless guys get the girls :smile: but all those technologies rely on the routing and switching engineers' bread and butter. You cannot be successful as a network engineer without understanding the fundamentals of how networks work. You may be able to build a complicated firewall configuration, but if you don't know why a host isn't responding to an ARP request then you're only going to be 50% as effective as the guy who knows how to do both. And there is a lot of guys (and girls) out there that know how and you'll be competing with them for the best jobs.

How Do I Learn About Networking?

First and foremost, networking is not a job where you can complete a certificate and never have to open another book ever again. Not if you want to be a successful network engineer anyway. Network technology is constantly evolving and staying up-to-date through self-study is important so be prepared for a journey of life-long learning. That sounds worse than it is, but if you're doing something you enjoy, it's a breeze!

There are literally thousands (maybe millions!) of resources online that can help you learn about networking, and you'll find every one of those sites will aid you by explaining a technology in a way that no other resource does. There is no single definitive resource for network learning except maybe for reading Requests for Comments (RFCs), which define the standards we use, but I wouldn't wish that study route on anyone!

Ask questions, and ask as many as you need to. There is no such thing as a stupid question. What's stupid is trying to do something you don't know how to do. That's applicable to all walks of life, but it's super important in networking, where an innocuous change could have disastrous consequences. Never be afraid to ask anything.

You can also use the certification guides from any of the major vendors and work towards an industry recognised certificate, which will teach you 99% of what you need to know, which I'll go into in more detail next.

What Certificate Should I Take, Do I Even Need One, Should I Take A University/College Degree?

Do you need a university/college degree?

This may be contentious, but from my own personal experience (and opinion), no. For me, a 4-year course is 4 years hands-on experience wasted. I do not have any sort of computer related degree, but I have over 15 years of network experience and a handful of certificates and it has NEVER held me back when applying for a role. I have also interviewed many candidates who have computer related degrees (and you do see this as a requirement for a lot of jobs nowadays) but if they don't know how to do the job needed of them, then they won't get the job, degree or no degree.

All about Certificates


You do not need a network certification to get started in networking. Certificates are great, but they really need to be backed up by experience. That's not to say you shouldn't start your certification study straight away, you should absolutely go for it, studying and getting hands-on with live equipment is the absolute best way to learn.

There are many entry-level network certificates out there, and some of the most popular ones are Cisco CCENT/CCNA and Comptia Network+.

Which one is "the best"?

I would say that although the Network+ certificate is useful, the CCENT/CCNA is one of the most important network certificates you can acquire. The Network+ is very useful and does cover some topics that the CCENT/CCNA does not, but the CCENT/CCNA covers everything that the Network+ does and teaches you how to administer Cisco networks. You would be hard pressed to find any company in the world that does not use Cisco equipment in some capacity, and what the CCENT/CCNA lacks in comparison to the Network+ will be picked up as you learn anyway.

From an employment point of view I've never seen a job that required a Network+ (that's not a slight against those who hold it), most require a CCNA as a minimum for even slightly more experienced roles. And looking further forward in your career for a moment, most jobs are handled by non-technical recruitment consultants that don't understand the difference between BGP & EIGRP, they only know that the CCNA you hold ticks the boxes.

There is one caveat to the certification route. Demonstrable experience. On a technical interview, it doesn't matter to me whether you have certificates or not. If you can show me you know what you're doing, that's what counts. Although not required for entry level roles, don't think a lack of certificates will hold you back in the future if you know what you're doing.

For any role in IT, you need to have (in order of importance):

1. A good attitude

2. A willingness to learn. This is really important for entry level roles.

3. Personality. You don't need to be the life and soul of the party or a social hand grenade, you just need to be a guy or girl that I can work with. Show me it during the interview.

4. Experience. I don't need you to know how to configure a DMVPN for your first job, but if you know how ping works or how you configure the wireless on a home router, tell me! It all counts.

5. Certificates. Not important for entry level roles.

6. Your favourite sports team. This may or may not influence the entire interview process :smile:

7. University/college degree. If you have one, more power to you. However (and remember I'm speaking from personal experience) this has never been relevant to any interview I've sat or held.

How Long Will It Take?

It all depends on your aptitude. There is no set time to pass any exam, do it at your own pace and make sure you understand the content enough to do your job well, not just to pass the exam.

OK, I'm All Set, What Type Of Job Should I Go For?

This question always makes me smile. I think Richard Branson said, “If somebody offers you an amazing opportunity but you are not sure you can do it, say yes – then learn how to do it later!”. If you think you can do the job you're applying for and can pass a technical interview based on the job requirements,I say go for it! But then again, I like a little bit of crazy on my team :smile:

If you know next to nothing about networking or IT in general or perhaps lack a little bit of confidence, you'll be best served by looking for roles that don't require experience.

It can sometimes be difficult to get into entry level networking roles so if you're not immediately successful when applying, keep your chin up. It happens to the best of us, and sometimes still does. My view is that a company that doesn't recognise a good attitude and passion isn't worth working for anyway. Good bosses recognise these attributes and a good boss translates as a good place to work.

As mentioned, I'm happy to answer any questions on anything that isn't covered so feel free to ask!

Best of luck!


© 2016 techsupportforum.com





 
#3 ·
Hi Mitch, and welcome to the Articles section.

You probably won't have editing permissions here so, when you want to make changes, accept or refuse changes/suggestions, etc., use the quote button, make your changes and remove the quote tags before posting. If you prefer, and theres not much editing to do, you may prefer to simply quote sections of the Article. That way might be better actually as then, all changes can be applied to post #2.

Editing

When editing, to help make it clear to authors what changes you've made, indicate suggested removals using strikethrough and suggested replacements in red.

Comments contained within the edit should be made in Green. We, (the editors) tend to each use our own colour to distinguish between different editors comments. This won't apply to you if you're making comments in a seperate post.

E.g.

One of the problems inherent challenges with trying to write and writing an exhaustive guide to Facebook is that its features are constantly changing. Try to make your sentences flow.
Formatting

For consistency, articles should be formatted in the following way.

  • Section Headings are colored Purple with bold formatting.
  • Subsection headings are colored Purple with italic formatting.
  • Article and Tutorial links, as well as download links, are colored Sienna with bold formatting.
  • Links to articles or threads at TSF are colored Blue with bold formatting.
These guidelines for formatting are just that, guidelines. It may not be as simple in all cases, especially lengthy articles where there are multiple sections.

Here are two examples of well formatted articles. There are minor differences to the formatting, but the style is the same and the formatting is neat and clean.

Is your PC running slow…?
PC Safety and Security – What Do I Need?

One of us will be along presently to start :3-smash: hacking away at your article. :lol:
 
#6 ·
Hi all.

Routing & Switching. Period. It's not usual to emphasise Period when used in this way

I'm trying to emphasize the importance of the routing & switching track, without the linguistic ability to do so, so would be happy for any suggestions on how to make it better :) More than happy with the other changes!

I thought about adding a hands on section if that would be a useful addition?
 
#12 ·
Looks good, great work guys!

Except.......@John, did you pass this?

There is quite a number of roles available today in networking
I did a brief search and there seems to be some debate about this, mostly about whether the sentence contains an 'uncountable noun'.

I don't care! It doesn't look right, doesn't sound right, it should be 'There are'. :popcorn:
 
#15 ·
Looks good, great work guys!

Except.......@John, did you pass this?



I did a brief search and there seems to be some debate about this, mostly about whether the sentence contains an 'uncountable noun'.

I don't care! It doesn't look right, doesn't sound right, it should be 'There are'. :popcorn:
My bad. It must have been late at night. :facepalm:
 
#18 ·
If it was simply overlooked, thats easily fixed. I thought we was going to have a debate because of how many I've seen that would have agreed with it being written that way.
It's one of those things that are open to debate, unlike your 'we was'. :grin:
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top