When u become network engineer??

yuddhidhtir

Just wondering what are the qualification and certification required to be called an Network Engineer

ccnaomkar

from what i have read

i think network engineer must be mid level positon or level 2 engineer

for becoming level 2 engineer u should have some experience

minimum requirenment is that u should have ccna

because ccna is very basic certification

after ccna u can pursue ccnp

but it is more inclined towards cisco gear so u can pursue if ur going to work with cisco gear in ur job
as there are lot of competition between cisco,juniper and alcatel in india

Tackle

My title is Network Engineer.

But that's all it is, just a title.

We only have a handful of dell power connect switches and a firewall. The ISP handles the router.

I could not even explain the basics of Cisco. (Though I'm not too shabby at subnetting.)

chrisone

Network engineer sounds to me like 3 to 4 years experience in the following.

1. Routing and switching
2. Security concepts
3. VOIP concepts (but not having to be a VOIP engineer, just know how VOIP works)
4. Wifi Basics
5. Good TCP/IP protocol understanding
6. Network Design concepts

Cert wise, i would say CCNP minimum, some security cert/s.

networker050184

Whenever someone hires you and bestows the title upon you. There aren't any requirements really. Some places call everyone an engineer.

chrisone

true , just like the title network administrator is given to many server guys and they do nothing with the network.

onesaint

Its like that in Aerospace. There are some positions that pay more than others, but they loose the title of "Engineer." People really gun for that title.

chrisone

it looks good on the resume , better than the words "entry"

shodown

There are "network engineers" and there are "network engineers" Don't get caught up in the title. Many Sr Network Engineers send me tickets everyday cause they can't get things working.

Hypntick

My title is network engineer. The most network related thing I touch is our firewalls. Other than that it's an amalgamation of system admin work, backups, desktop support, help desk and everything in between. Heck in almost 4 months i've checked 1 switch port and it wasn't even on a Cisco.

onesaint

Hypntick wrote: »

My title is network engineer. The most network related thing I touch is our firewalls. Other than that it's an amalgamation of system admin work, backups, desktop support, help desk and everything in between. Heck in almost 4 months i've checked 1 switch port and it wasn't even on a Cisco.

This sounds like a SA role in an SMB. I just came across a job posting for a network admin that was asking for things like bakc up experience and WSUS.
I think when they think "Network Admin," or "Engineer" non technical managers are thinking someone that will administer all the devices and users within a network and not just the network devices themselves.

Monkerz

My job title is Network Engineer II. It was required to have CCNA and 2 to 4 years experience. I am finding that CCNP should have been a requirement for the position. My CCNP studies have helped me dearly in my day to day tasks.

I deal almost entirely with routing and switching. I travel 40% of the year redesigning the data network and/or retrofitting our branch offices with Shoretel. I have just now began to take on some VoIP responsibilities. I deal a lot with circuit outages, installs and upgrades. I handle all distro and access layer issues. If I cannot fix it I escalate to my Sr. Engineer, but that is happening less and less.

Our Sr. Network Engineer is responsible for our Data Center's redundant core, fiber nodes and our many OC circuits. He is also responsible for me, which is a job in itself.

Tackle

Hypntick wrote: »

My title is network engineer. The most network related thing I touch is our firewalls. Other than that it's an amalgamation of system admin work, backups, desktop support, help desk and everything in between. Heck in almost 4 months i've checked 1 switch port and it wasn't even on a Cisco.

Sounds exactly like my job! "Network Engineer" but end up doing everything except lots of Switch/Router work!....It'll look good on the resume, but lets hope they don't think I'm great with networking or CCIE
It is a small business (Less than 100 employees).

Nobylspoon

My job title is "Resident Engineer" however, my cousin is an Aeronautical Engineer who possesses a Master's in Engineering. I am still working on my Bachelor's, lol.

The term "engineer" is thrown around to mean just about anything these days. I remember reading about the MCSE being a huge debate in Canada because they are more strict on the term's meaning and did not agree that someone taking a couple of MS exams should earn the same title as someone who has put in 6+ years of education in the field of Engineering.

That being said, when I was told my title could either be "FTE" or "Resident Engineer" it was a no-brainer which one to use for my resume ;P

Hypntick

onesaint wrote: »

This sounds like a SA role in an SMB. I just came across a job posting for a network admin that was asking for things like bakc up experience and WSUS.
I think when they think "Network Admin," or "Engineer" non technical managers are thinking someone that will administer all the devices and users within a network and not just the network devices themselves.

Yep I work for a MSP, 7 of us providing support for 175+ clients with between 3 to 300 users. I think we're called that because our non-tech clients respond to it better. I'm not gonna argue with it, should I ever decide to leave it's gonna look nice on my resume.

onesaint

Hypntick wrote: »

Yep I work for a MSP, 7 of us providing support for 175+ clients with between 3 to 300 users. I think we're called that because our non-tech clients respond to it better. I'm not gonna argue with it, should I ever decide to leave it's gonna look nice on my resume.

Agreed. The Engineering title carries a nice weight to it. Sounds like you guys have got your hands full there!

Bl8ckr0uter

networker050184 wrote: »

Whenever someone hires you and bestows the title upon you. There aren't any requirements really. Some places call everyone an engineer.

This...

shodown wrote: »

There are "network engineers" and there are "network engineers" Don't get caught up in the title. Many Sr Network Engineers send me tickets everyday cause they can't get things working.

and this.

My title is network engineer (just finished my first week yah!). They wanted a CCNP/CCIP and CCSP, but they took a CCNA and CCNA:Security.

I have in total about 2 years doing cisco work (although most of it has been very light and I spent the last year before this almost completely disconnected from cisco).

When I first started IT, I didn't really have a goal . I then got on a helpdesk and my goal became get the cuss off the helpdesk. Then I got off the helpdesk and I wanted to get into "Network Security". Then I want into "Network Security Engineering". Well now I am in a place where I could be that soon. What I have found is that people who get stuck on titles usually are compensating for something that's lacking (in their heads or in their pants). As long as it isn't something racially, sexually or just plan offensive, call me whatever the cuss you want. I don't even care if it makes sense. Give me duties. Let me grow. Pay me on time. Rinse and repeat. That's all you can ask for. The sooner you realize that, the better.

NOW what I will say is some HR people will scan your resume to see if you have done say "Network Engineering" or "Network Administration". No matter what you job title is, make sure you accurately describe your job duties and skills on your resume. I cannot stress that enough. In fact, if you know you are trying to look for a new job and the title is "Network Engineer", change your descriptions on your resume to include some form of those words. I am not talking about making anything up (if you didn't do it, you didn't do it) but if you worked with cisco gear and you did all of the work, say you engineered a cisco solution for your business or whatever. Don't like, but use their "catch phrases". Lot's of people will see "Helpdesk X" on your resume and say well you can only do helpdesk jobs or they won't even consider you for Admin positions because you haven't "been an admin". But if you are doing file permissions, maintaining the server farm, setting up a voip solutions, banging out gpos and whatever, you should say that you adminsitered a windows network. Not everyone will agree with me here but I am speaking from experience.

ehnde

I, for one, am a Network Janitor (and you should welcome your new Network Janitor overlords).

Panzer919

My company gave me the title, Network Specialist. I manage 2 ASA 5520's with IPS modules, 13 WAAS devices, 2 Nexus 7010's, 26 Cisco Routers, somewhere around 90 Cisco switches, a WLC, 20+ AP's and some other devices I know I am forgetting at the moment. The only think I don't exclusively manage is our Cisco voice setup. 1 guy handles all that while I handle the rest. Do I do the job of a Network Engineer, I'd like to think so. I have a friend who has the title Sr. Network Engineer and I know I can run rings around him. It just all depends on what they want to call you. Wish I could create my own title, although I don't think network ninja would go over to well on a resume

ChooseLife

when you can troubleshoot a routing protocol by laying your hand on the network cable...