Top 10 IT Positions by Prestige

Bokeh

10 IT positions ranked by prestige | TechRepublic

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

chrisone

Maybe i am biased but no one on that list can do their job without the network guy LOL

unless the system analyst is considered a network engineer.

down77

chrisone wrote: »

Maybe i am biased but no one on that list can do their job without the network guy LOL

unless the system analyst is considered a network engineer.

They forgot to mention that when issues plague the data center the Network team is the first one blamed and usually the one who ends up finding the problem (which was usually caused by one of the other 9 on the list). Network Engineering is not the most prestigious role, but the are the Marines of the technology realm.

DevilWAH

chrisone wrote: »

Maybe i am biased but no one on that list can do their job without the network guy LOL

unless the system analyst is considered a network engineer.

what about the network admin whos on the list?? hes a network guy ?

shodown

down77 wrote: »

They forgot to mention that when issues plague the data center the Network team is the first one blamed and usually the one who ends up finding the problem (which was usually caused by one of the other 9 on the list). Network Engineering is not the most prestigious role, but the are the Marines of the technology realm.

Never heard it put that way, but it makes so much since. Networks always goes in 1st.

down77

Shodown, a Marine friend who works as a Network Engineer for AT&T was the one who told me that. "First to be deployed, last to come home."

Hypntick

Love how they put #10 on there. The help desk gets no respect, even from management.

erpadmin

chrisone wrote: »

Maybe i am biased but no one on that list can do their job without the network guy LOL

unless the system analyst is considered a network engineer.

Whenever I hear that smack, I instantly respond that I'm the one responsible for the network guy(s) to get paid. Our payroll is inhouse handled by our inhouse PeopleSoft servers that I maintain. If they hit the UPS killswitch, payroll can't process our checks...

In fact to take it one step further, I can make it where just the network guy(s) payroll isn't processed....that's about 2-3 lines of SQL...

Network guys...they make stuff run
Database guys...we really make stuff run...

jibbajabba

And I am the engineer who can pull the plug on the datacenter / server so neither of you would get paid

chrisone

We are also the network engineers who keep you safe from the outskirts of hackers looking to cause your data bases harm.

Excellent1

After reading this thread, what popped into mind was 1 Corinthians 12:12-26.

Most positions in IT are dependent on their fellow workers to function. Which is more important is debateable, but the fact is that to function well, all are necessary. Of course, it's always nice to be the one making more money, but we can't all drive Ferrari's.

mikedisd2

How is this a list of prestige? Items 4 to 10 are all majorly dissed by the writer.

Anyway, if you're after prestige in IT you're there for the wrong reason. I'd rather be in a role that actually makes a difference to people and the company.

jibbajabba

If one part suffers, every part suffers with it; if one part is honored, every part rejoices with it.

JDMurray

#2 "[Programmers] are typically held in a special place of esteem."

Oh please...

The term "programmer" is just one step up from "code monkey," "code grinder," and "Can't you write a program without any bugs?"

If we are to rank the #2 spot then at least dignify us with the proper title of "software engineer."

Mishra

Our QA department just walked over and introduced someone to our department. Her quote was "Here is the technical operations department... They know everything so if you need someone then ask these guys."

There you go... The system/network engineers know EVERYTHING.

Turgon

down77 wrote: »

They forgot to mention that when issues plague the data center the Network team is the first one blamed and usually the one who ends up finding the problem (which was usually caused by one of the other 9 on the list). Network Engineering is not the most prestigious role, but the are the Marines of the technology realm.

Aroooga!

RobertKaucher

What if your job includes 1,2,3,5 and 7? And 8 and 10...

bertieb

mikedisd2 wrote: »

How is this a list of prestige? Items 4 to 10 are all majorly dissed by the writer.

My thoughts exactly.

RobertKaucher wrote: »

What if your job includes 1,2,3,5 and 7? And 8 and 10...

You chose the wrong career and should have been an actor/neurosurgeon or the like where you can officially use the work 'prestige' in place of 'geek'

it_consultant

In all fairness I think that network admin in this article is the network guy. Most people nowadays have to wear more than one hat.

Panzer919

down77 wrote: »

Network Engineering is not the most prestigious role, but the are the Marines of the technology realm.

I am stealing this

It makes even more sense if you have ever been in the military. Even though a Marine (or Army Soldier) might specialize in one thing or another, when the #### hits the fan, everyone is infantry first.

So when #### hits the fan and our network is being blamed, we go back to our basics and prove out that it's not.

erpadmin

Excellent1 wrote: »

After reading this thread, what popped into mind was 1 Corinthians 12:12-26.

Most positions in IT are dependent on their fellow workers to function. Which is more important is debateable, but the fact is that to function well, all are necessary. Of course, it's always nice to be the one making more money, but we can't all drive Ferrari's.

This is the mindset you have to bring into an IT shop when you are in a team environment. There were countless times (in fact I have two specific things in mind...one yesterday and the other last week) where I'm working with my network colleagues to solve a problem.

It's so easy to point a finger, walk away and say "not my job..."; it's not so easy to work together and solve a problem.

At the end of the day, whether it's the network or the databases (for example), if we can't fix the problem, we're all out of work! The same is true with programmers and database administrators. It's not necessary to know how to write code, but it is necessary to read it to do your job as a DBA. When something gets migrated and all of a sudden the database is slower than a Yugo, I better know what's running against my database to ascertain what the issue is. Being able to function in a team environment is essential to IT...period!

Finger pointing, comparing the size of *whatever*....at the end of the day, no one cares.

Panzer919

erpadmin wrote: »

It's so easy to point a finger, walk away and say "not my job..."; it's not so easy to work together and solve a problem.

At the end of the day, whether it's the network or the databases (for example), if we can't fix the problem, we're all out of work!

Finger pointing, comparing the size of *whatever*....at the end of the day, no one cares.

too true