Compare cert salaries and plan your next career move
blargoe wrote: » Depends on the environment. I would never do it at my company. Doubt I would do it elsewhere... but if I were in a situation where appearances were more important than ability and results, I might would hang the more advanced certs.
brad- wrote: » I just carry all of them around with me in an accordian folder and hold them up to random people's faces. Honestly though, I have no desire to hang them. The paper really doesnt mean much to me.
networker050184 wrote: » I think it is simply because in IT experience is what really matters. No one cares if you have all the degrees and certifications in the world.
Warsh1p wrote: » I don't get why people keep saying this on this particular forum. Is it the lack of understanding or knowledge of obtaining a job at a large corporation? Or does no one here care for a job in engineering or developing? You can have all the experience in the world but still will only support technology. It would be very difficult for you to obtain an engineering or developing job with just networking, security or help desk experience. I feel like 99% of people on this forum think Master degrees are pointless in this field. But no one ever specifics that a Masters might be pointless if you are only supporting technology for a company. I also find it odd that people get certified but don't care for their certificate or get a degree but don't care for their diploma. Are you that ashamed of them? Coming from a for-profit school or not being a "professional" certification. Or are you simply just too cool?
networker050184 wrote: » In the field I work in (network engineering for service providers) a masters degree isn't something that is really going to help you. No one really cares if you went to college for four years doing completely unrelated work. All that matters is that you understand the technology and can prove that you can do the work. Writing a paper in MLA format isn't going to help you at 2 A.M when you have 200 customers down and you need to engineer and alternate solution for them.
Cherper wrote: » I am also in network engineering, but I don't want to be at this level forever. My degree and working towards a masters will ensure that opportunities for advancement into management happen. If you want to be the go-to operator forever, more power too you, but many want more. Back to studying....
Warsh1p wrote: » I feel like 99% of people on this forum think Master degrees are pointless in this field. But no one ever specifics that a Masters might be pointless if you are only supporting technology for a company. I also find it odd that people get certified but don't care for their certificate or get a degree but don't care for their diploma. Are you that ashamed of them? Coming from a for-profit school or not being a "professional" certification. Or are you simply just too cool?
brad- wrote: » It may be a little harsh, but techies with masters typically are overeducated and cant perform well because they have no work history, and their 'skillset' is extremely limited...and not focused on any particular technology.
Warsh1p wrote: » I also find it odd that people get certified but don't care for their certificate or get a degree but don't care for their diploma. Are you that ashamed of them? Coming from a for-profit school or not being a "professional" certification. Or are you simply just too cool?
Devilsbane wrote: » If you compare a person with a Masters and 0 experience to a person with a Bachelors and two years of experience, then yes I agree. But what happens 10 years down the road when person A has a masters and 10 years of experience and person B has a Bachelors and 12 years of experience? Does person A still have a limited skill set?
brad- wrote: » Of course not...but that scenario is less likely.
Devilsbane wrote: » Because people with Masters degress never get 10 years of experience?
Have you never heard of Network Engineers? Or Security Engineers? Or Network Security Engineers even?
brad- wrote: » nooo....because people with 10 years experience dont need a masters.
Warsh1p wrote: » I don't think you are understanding the term Engineer. Just because your role is called Network Engineer does not mean you are actually engineering technology. Most companies are to vague with the position titles. Unless you work for Juniper, Cisco or any other networking company that creates the technology you go out and get certifications for, you do not engineer anything. lol, this is simply because you are suppose to get your masters prior to going into the workforce or while you are still interning/working entry level positions. I will do one of your "mock" HR hiring processes that only can possibly work in your favor when the Masters degree holder has zero experience... Mr. A has a A.A.S. in Networking at a local community college with his A+, Network+ and 3 years experience as a NOC Mr. B has a Bachelors from WGU in Computer Network Administration with his MCITP, A+, N+, Security+, CCNA, CCNP and CIW Associates and 5 years experience in Networking Administration Mr. C has a Bachelors degree from a State University in Computer Engineering, a Masters degree in Computer Science from a State University or Ivy League school and 1 year internship experience at a top level company in the industry. He has also been a part of many endorsed researches involving Multidisciplinary System Design, Computer & Network Security and Process query systems. Trust me when I say Mr. C wins by a large, I mean large, margin. Even without low level certifications and not really concentrating on Networking. Although I cannot prove this with documentation, I will prove this by promising you that any job you ever apply for in your life time you won't be going up against Mr. C. As for hanging up certifications and diplomas. Trust me if you were Mr. C you would be hanging that Masters Degree at your home office or work office not filing it away with your A+
phoeneous wrote: » You must have a special engineer's dictionary then? I'd like to see it. Based on your logic, someone who builds a network from the ground up isn't considered an engineer? Those poor CCIE guys.... Main Entry: 1en·gi·neer Pronunciation: \ˌen-jə-ˈnir\ Function: noun Etymology: Middle English engineour, from Anglo-French, from enginer to devise, construct, from engin Date: 14th century1 : a member of a military group devoted to engineering work2 obsolete : a crafty schemer : plotter3 a : a designer or builder of engines b : a person who is trained in or follows as a profession a branch of engineering c : a person who carries through an enterprise by skillful or artful contrivance4 : a person who runs or supervises an engine or an apparatus
Just because your role is called Network Engineer does not mean you are actually engineering technology. Most companies are to vague with the position titles.
C definitely wouldn't win out in my group due to a degree only. The only guy we have with a masters works below me and has been doing this a lot longer. This field is all about relevant experience.
Warsh1p wrote: » I don't think you are understanding the term Engineer. Just because your role is called Network Engineer does not mean you are actually engineering technology. Most companies are to vague with the position titles. Unless you work for Juniper, Cisco or any other networking company that creates the technology you go out and get certifications for, you do not engineer anything.
Compare salaries for top cybersecurity certifications. Free download for TechExams community.