Slashdot Mirror


IT Jobs With the Best (and Worst) ROI

Nerval's Lobster writes: Over at Dice, there's a breakdown of which tech jobs have the greatest return on investment, with regard to high starting salaries and growth potential relative to how much you need to spend on degrees and certifications. Which jobs top this particular calculation? No shockers here: DBAs, software engineers, programmers, and Web developers all head up the list, with salaries that tick into six-figure territory. How about those with the worst ROI? Graphic designers, sysadmins, tech support, and software QA testers often present a less-than-great combination of relatively little money and room for advancement, even if you possess a four-year degree or higher, unless you're one of the lucky few.

77 of 139 comments (clear)

  1. "Over at Dice" by vux984 · · Score: 4, Insightful

    "Over at Dice...[...]"

    Since when is that "somewhere else"? Any submission of news from Dice lacks any credibility... and puff piece articles like this aren't worth anyone's time at the best of time.

    1. Re:"Over at Dice" by 93+Escort+Wagon · · Score: 1

      Does Dice still do the job listings thing? I ask because its been a few years since I heard anyone talk about looking there, either for jobs or for candidates.

      --
      #DeleteChrome
    2. Re:"Over at Dice" by vux984 · · Score: 1

      Hey guess what. When you're spending thousands of dollars a month on running /. then you can link to all your own relevant content you like.

      If I were running /. I'd have the editorial integrity not to.

  2. software dev vs programmer by clockwise_music · · Score: 1

    What's the difference between a software developer and a programmer? One develops software by programming, and the other programs computers to develop software.

    1. Re:software dev vs programmer by Spy+Handler · · Score: 4, Funny

      Developers are more in demand than mere programmers.

      Notice how Ballmer never says,
      Programmers
      programmers programmers
      programmers, programmers, programmers, programmers, programmers, programmers, PROGRAMMERS!

    2. Re:software dev vs programmer by crgrace · · Score: 4, Interesting

      Yeah it makes no sense. They have separate categories for Software Engineer, Programmer, and Software Developer. They are the same job, although often they have slightly different connotations in that in some organizations the word engineer has more prestige than programmer but it varies.

      Pretty much useless... a distinction that makes no different at best. Even if some pedant comes along and says "a software engineer has XX degree and a programmer has YY degree" it is still meaningless because these types of distinctions are not generally agreed upon.

    3. Re:software dev vs programmer by Anonymous Coward · · Score: 5, Interesting

      Software developer is someone who is capable of dealing with more of the software development lifecycle than the programming part. Architecture, design, requirements analysis, etc.

      programmer = code producer (aka code monkey)

    4. Re:software dev vs programmer by PolygamousRanchKid+ · · Score: 1, Funny

      Well, now he is saying:

      Basketball players
      Basketball players basketball players, etc . . .

      I am no fan of the NBA, but if it lured Ballmer out of the IT industry, and keeps him out . . . I will love the NBA . . .

      --
      Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
    5. Re:software dev vs programmer by Dutch+Gun · · Score: 2

      I tend to use "programmer" or "computer programmer" for myself, because I think it's the most accurate description.

      Most professions with "engineer" in the title require state certification and licensing to practice their trade. I figure that's a reasonable benchmark for whether someone should put "engineer" in their title. Some engineers get in a snit about this, and I can sort of see their point.

      I generally view "developer" as anyone who works on the software product in any capacity, although "software developer" still would likely refer to a programmer. For many products, there may be little distinction between "programmers" and "developers" simply because all the developers happen to be programmers. I happen to work in video games, where there are typically many more non-programmers than programmers working on a given project. As such, the distinction becomes more important. It's fairly common in the video game industry (and the public at large) to refer to everyone involved as developers, or "devs".

      --
      Irony: Agile development has too much intertia to be abandoned now.
    6. Re:software dev vs programmer by Anonymous Coward · · Score: 3, Informative

      Where I work, the software engineers work with the system and sub system engineers (mechanical electrical and chemical), write specs, develop the overall software 'architecture', frameworks and do some coding while the programmers implement the specs as provided by the engineers.

        Eg, developing the control software for a large food processing plant, the engineer would be familiar with the valves, levers, relays, transformers, host of sensors and types including electrical characteristics, etc. They would also understand the failure modes of each of said devices and how a failure at any one point affects the plant as whole so they would understand how a stuck valve at position 244 could be detected by a temperature drop followed by a rapid rise at mixing valve 11 on the other side of the plant. They understand what signals need to be debounced and how to debounce them, how to filter the different signals, detect system inconsistent states, etc.

      The programmers do some of this also, but it's not their primary responsibility which is to implement the specs in software

    7. Re:software dev vs programmer by AuMatar · · Score: 1

      No they don't. At least not in the US. Do you think the guy who drives a train has a state certification? And they're the originals.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    8. Re:software dev vs programmer by Dutch+Gun · · Score: 3, Informative

      In the US, railroad engineers are required to be state certified and re-certified every two to three years. How about civil engineers? Oh yeah, them too. Mechanical engineers? To become a Professional Engineer in the US, state certification is required. As for electrical engineers, I don't think they have any state licensing requirements, but for all practical purposes, a four-year degree (a state-certified document as well) is typically required for employment.

      This shouldn't be surprising to you. Any profession that could adversely affect the safety or lives of the public if mistakes are made often requires state certification. For the most part, this doesn't affect EE or CS. No one dies if MS Word crashes or your microwave stops working. And in those exceptions when that's NOT the case, certification is typically required of the products themselves (cars, airplanes, medical equipment) instead of the people who worked on them.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    9. Re:software dev vs programmer by Princeofcups · · Score: 1

      Yeah it makes no sense. They have separate categories for Software Engineer, Programmer, and Software Developer. They are the same job, although often they have slightly different connotations in that in some organizations the word engineer has more prestige than programmer but it varies.

      Pretty much useless... a distinction that makes no different at best. Even if some pedant comes along and says "a software engineer has XX degree and a programmer has YY degree" it is still meaningless because these types of distinctions are not generally agreed upon.

      But that's why all three are listed. Companies that post may have different names for pretty much the same job, but the posters have to find a matching title. I don't see what the problem is.

      --
      The only thing worse than a Democrat is a Republican.
    10. Re:software dev vs programmer by Anonymous Coward · · Score: 1

      I work on avionics systems and do not have a professional certification other than college degrees. No one whom I work with does either (and I know many people in the industry). I even know people without college degrees doing the same work for decades...since the 70's even.

    11. Re:software dev vs programmer by mrchaotica · · Score: 4, Informative

      First of all, quit being obtuse.

      Second, train engineers are not the "original" engineers. The original engineers were people who designed siege engines (hence the name) for warfare -- ballistas, trebuchets, battering rams, etc. -- as well as fortifications. Military engineers predate trains by several thousand years.

      Third, the second-oldest type of engineering is "civil engineering," and is named such because "civil" is the opposite of "military." Civil engineering is also several thousand years older than trains.

      Oh, and by the way: the word "engine" didn't originally have anything to do with internal or external combustion; the Latin root word translates roughly as "a produced thing," or an object created by ingenuity. So in the truest sense, an engineer is anyone who uses his ingenuity to build something.

      The only reason railroad engineers are called such is because presumably the earliest ones built the damn locomotive as well as operated it. Besides, the US and Canada are the only places that call people who drive trains "engineers" anyway -- everywhere else calls them "drivers," "operators" or "pilots."

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    12. Re:software dev vs programmer by Zero__Kelvin · · Score: 4, Interesting

      A programmer can take a specification and implement it. For example he can be told: "Create a module with function that takes two arguments from the databse and stores their product back into the database.* He may even be able to take a set of specs and write all the code for the project.

      A Software Developer on the other hand knows how to do requirements gathering and analysis, create time lines and cost projections, recommend and implement solid Source Code Control mechanisms (In other words they use git in 2015)

      Above that level of competence is the Software Engineer. They understand various development models (e.g. Waterfall, Iterative/Spiral, etc.) and paradigms (e.g. Structured, Object Oriented, Event Driven) , and patterns such as Idempotence, singletons, etc.).

      * One other difference between a programmer and the Software Dev or Engineer is that the programmer thinks this is easy, and the latter two know that there can be a lot more involved than you might imagine

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    13. Re:software dev vs programmer by Zero__Kelvin · · Score: 1

      "Yeah it makes no sense. They have separate categories for Software Engineer, Programmer, and Software Developer."

      You wouldn't say that if you were a software developer or a software engineer.

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    14. Re:software dev vs programmer by Dutch+Gun · · Score: 3, Insightful

      Sure, of course. It's why I used the qualifier "most" and "typically". And that's also why I mentioned that if the professions themselves aren't certified, then it may be the products themselves. I have no idea about the specifics of your industry, but I'd bet your company's products have to get certified by the FAA.

      --
      Irony: Agile development has too much intertia to be abandoned now.
    15. Re:software dev vs programmer by dargaud · · Score: 4, Interesting

      In England we call them, much more accurately, train drivers.

      Interestingly, in France we call them chauffeurs, as in heaters. Because they used to have to shovel coal under the steam engine long before they could start them. And taxi and truck drivers are still called this way. Etymology...

      --
      Non-Linux Penguins ?
    16. Re: software dev vs programmer by Larryish · · Score: 1

      Only the 20-sided one.

    17. Re:software dev vs programmer by xaxa · · Score: 1

      In England we call them, much more accurately, train drivers.

      Interestingly, in France we call them chauffeurs, as in heaters. Because they used to have to shovel coal under the steam engine long before they could start them. And taxi and truck drivers are still called this way. Etymology...

      That is interesting -- because chauffer in English means the person who drives your limousine.

      The man responsible for the fire on a steam locomotive is called a fireman. (It's actually moderately skilled -- the fire is large, and needs to be balanced, and provide the right level of heat, and not waste coal. I had a go when I was about 13, unofficially on a tourist steam railway.)

    18. Re:software dev vs programmer by Drethon · · Score: 2

      Though you are typically expected to understand DO-178b, or at your company should have people who do in order to certify the software. Then the FAA DER audits that software based on DO-178b. At least if the software is considered critical to safety of flight.

    19. Re:software dev vs programmer by RabidReindeer · · Score: 4, Insightful

      Certification is all very well and good when most people in the profession are doing the same thing and the state of the art is advancing relatively slowiy.

      One the other hand, one of the IT professional organizations of the 1970s attempted to create the concept of a "Certified Data Processor" (CDP).

      I have a copy of a CDP exam prep guide. Not many things in it are even possible any more. Reading punch cards by eye, knowledge of COBOL program organization, mainframe JCL - the stuff that isn't flat-out obsolete is really niche these days. Few RoR programmers know JCL. People who Java well aren't usually also top-tier .Net experts. Some people work intensively with Struts, but more don't. And that's not counting system expertise like how to endure the Windows Registry or run dtrace on Linux.

      Sure we have dozens of domain-specific certs in IT. Most of them carry little or no weight. There's no general cert that defines your overall competence or lack thereof.

      The only hope for professional certification would be if someone could devise an exam sufficiently abstract to work in all major variants of an IT discipline, regardless of OS, language or platform. So far, no one has done that.

    20. Re:software dev vs programmer by RabidReindeer · · Score: 1

      These days, we are more likely to call your train "engineers" developers, designers, or inventors. Or at the very least design engineers.

      We use the general term "engineer" for a persons who runs an engine, whether it be a railroad engine or a Warp Drive.

      Similarly, a "computer" used to be a person. Now it's hardware.

      The English language isn't as regular as some would like it to be.

    21. Re:software dev vs programmer by ranton · · Score: 2

      Most professions with "engineer" in the title require state certification and licensing to practice their trade. I figure that's a reasonable benchmark for whether someone should put "engineer" in their title. Some engineers get in a snit about this, and I can sort of see their point.

      IMHO, the mere usage of the term engineering in the software industry is a good thing. The more developers who think of themselves as engineers, and try to elevate their professional practices to a level worthy of the term, the better the industry will be. It may take some time for software engineering practices to become as mature as civil engineering, but I believe the developers who consider themselves software engineers are the ones who will do it.

      I personally am fine considering myself a software engineer. I find the connotations the term carries apply well to how I try to separate my capabilities from less structured programmers.

      And as for engineers being rubbed the wrong way, I have yet to meet a "true" engineer who I admire who felt there was anything profound about being called an engineer. To paraphrase one college friend / mechanical engineer: "There are a lot of incompetent certified engineers out there."

      --
      -- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
    22. Re:software dev vs programmer by luckymutt · · Score: 1

      About $20k per year.

  3. A little surprised by guises · · Score: 1

    Maybe not "shocked," but I'm a little surprised to see such a difference between sysadmins and DBAs. I usually think of them in the same group, with DBAs being a notch higher by dint of specialization.

    1. Re:A little surprised by Anonymous Coward · · Score: 1

      Maybe on old school systems, but modern day they are quite different. And that's a beef I have with this "article", DBA entry level might be $59,000, but I haven't met many 22 year old DBAs pulling in a nice salary like 60k. My experience has been they are all 30+ with other experience prior, like sys admin or programmer. Average age has been 40+. YMMV.

  4. Over at McDonald's by Anonymous Coward · · Score: 5, Funny

    Over at McDonald's (one of the worlds greatest Scottish Restaurants) you can taste a variety of taste sensations...

    All you'd have to do is type www.mcdonalds.com and it could all be yours. Yep Over at Mcdonalds you could figure out the dinner that best suits your needs over at McDonalds. People might think that by saying over at McDonalds I'd like you to you know go over to Mcdonalds but I'm just Say'n it (I can say this because Slashdot isn't owned by McDonalds its owned by Dice)

    1. Re:Over at McDonald's by TheGratefulNet · · Score: 1

      'say it once.

      say it twice.

      three time's the charm.'

      (the B guy)

      --

      --
      "It is now safe to switch off your computer."
    2. Re:Over at McDonald's by Ice+Station+Zebra · · Score: 1

      I tried ordering haggis once at the drive-thru, and they asked me if I wanted fries with it. WTF, do they think I'm a brit?

    3. Re:Over at McDonald's by Paul+Jakma · · Score: 1

      Nae neeps and tatties?

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
  5. Nonsense by moogied · · Score: 3, Insightful

    Nonsense. Job titles in IT are just "guidelines" as for your job duties and job duties are what decide salaries once you've become established at a company. I've seen "sys admins" who wrote C++ code all day long for various system tools and got paid well into 6 figures for it. I've seen DBA's who spend there days building systems and configuring various components of the server who also make 6 figures. I think the bottom line is generally that you need to have multiple strong skill sets and to find ways to apply these various skills at your job. A quick story that probably has no real merit: A linux admin at my current job got saddled with trying to get the microsoft system suite to do a few fancier things in terms of configuration management. This means that he had to write a few dozen modules in C++ to get the right data placed into the microsoft suite. He makes well into 6 figures (we're drinking buds). Talent + effort + correct company == high pay.

    --
    So basically, -1 troll/offtopic is really slashdots way of saying "I hate that you thought of something before me."
    1. Re:Nonsense by Anonymous Coward · · Score: 1

      I'd argue this has more to do with the size of the company than anything.

      In large enterprise systems, you usually stick pretty close to your job description. In smaller companies, they need people with a more wide range of skills.

  6. My Job: /. commenter by Ice+Station+Zebra · · Score: 3, Funny

    ROI: I think I owe somebody some money.

  7. Missing: Technical Writers by Nova+Express · · Score: 1

    Good pay, good hours, limited room for advancement.

    But it's not like I expect a Dice Slashvertizement to be remotely complete...

    --
    Lawrence Person (lawrencepersonh@gmailh.com (remove all "h"s to mail)

    http://www.lawrenceperson.com/

  8. "Over at dice..." by DoofusOfDeath · · Score: 3, Funny

    At the risk of sounding cruel, this reminds me of an unpopular kid who's walking all around school, casually mentioning to everyone that lots of people are going to hang out at his house that night.

  9. Waiting for SUPER-Dice story plant. by DoofusOfDeath · · Score: 2

    "Genders that pay the best in I.T."

  10. Re:The Job Title doesn't matter.... by plopez · · Score: 4, Insightful

    Tell that to the HR drones or the managers who see people as interchangeable biological units.

    --
    putting the 'B' in LGBTQ+
  11. DBAs first? Strange by hibiki_r · · Score: 1

    Around here, if anything, the DBA job is disappearing: There are a lot less openings, and most are at huge, extremely corporate places that you'd not even want to work for. And even in that world, they are switching to development models that don't need DBAs. So maybe the averages are high because only companies that pay well would even hire DBAs?

    They also talk of averages, but not high ends. Around here, a programmer's high end is very high: I make 4x what my employer pays an entry level developer. People realize how much a top developer can get you. DBAs, not so much.

    1. Re:DBAs first? Strange by tompaulco · · Score: 5, Insightful

      The DBA probably gets paid a lot because the company is desperate for someone to come in and fix the database after the developers thought they could do the job themselves.

      --
      If you are not allowed to question your government then the government has answered your question.
    2. Re:DBAs first? Strange by Anonymous Coward · · Score: 4, Insightful

      Ditto. Where I work we've gone through cycles of having devs design DB changes and implement procs only to go back to stricter guidelines once the DBAs have to get engaged in performance issues. In cases where a high performing application is a must, a DBA is essential.

    3. Re:DBAs first? Strange by Antique+Geekmeister · · Score: 2

      Unfortunately, the cost of hiring one is often spending six months to re-engineer the nightmare created by semi-sophisticated developers, the nightmare which simply cannot support the next level of service or next round of customers on the original architecture. This sort of problem pays for the DBA members of my group, others of us work with other aspects of such projects.

    4. Re:DBAs first? Strange by Per+Wigren · · Score: 4, Insightful

      The DBA probably gets paid a lot because the company is desperate for someone to come in and fix the database after the developers thought they could do the job themselves.

      This.

      Sincerely, a DBA.

      --
      My other account has a 3-digit UID.
  12. I do a lot of what I do for money by Rinikusu · · Score: 1

    but mostly because I mostly enjoy the job. We don't need another wave of money-chasing mouth-breathers fucking up the industry.

    --
    If you were me, you'd be good lookin'. - six string samurai
    1. Re:I do a lot of what I do for money by Zero__Kelvin · · Score: 1

      And How!!! Unfortunately I think it may be too late. The industry is flooded with incompetents, as we both know all too well :-(

      --
      Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
    2. Re:I do a lot of what I do for money by RuffMasterD · · Score: 1

      Fixing the damage done by cheap fuckups keeps me employed and makes me look good in the process. But there's an optimal level, maybe one low level fuckup per company. Just enough to remind management that something needs money spent to fix, but not so much that everything collapses. If we do our jobs really well nobody will notice. It's like the sewage system. So without a few fuckups, management forgets why they pay us.

      --
      Human Rights, Article 12: Freedom from Interference with Privacy, Family, Home and Correspondence
  13. Re:The Job Title doesn't matter.... by tompaulco · · Score: 2

    People who do have talent and drive also sometimes end up not succeeding. The people who are willing to step on anyone will definitely end up succeeding though.

    --
    If you are not allowed to question your government then the government has answered your question.
  14. Dev ops seems to be missing by Anonymous Coward · · Score: 2, Interesting

    Dev ops, I have gone from 40k 6 years ago to 120K+bennies now.
    That's not mentioning side work or the 6 emails A week I get about new jobs.

    1. Re:Dev ops seems to be missing by tnk1 · · Score: 2

      That is why sys admins look a little low on the scale. The ones making the money have re-branded themselves as "DevOps Engineers".

      Which is sort of funny, because DevOps isn't supposed to be a title, it is literally supposed to be collaboration between Operations and Development, where the jobs are still distinct but inter-operate better by using certain tools and methods.

      Most security standards tend to still insist on some sort of separation of duties, so you basically end up with DevOps being Ops with more street cred and more $$$. Not that I am complaining.

    2. Re:Dev ops seems to be missing by Billly+Gates · · Score: 1

      Shouldn't that be the job of the manager or supervisor to talk to operations and be the so called quarterback instructing everyone else what to do?

    3. Re:Dev ops seems to be missing by tnk1 · · Score: 1

      I suppose it depends on your structure. In reality, the managers have to deal more with the business aspects of what their team is doing, in addition to coordination and planning. You could have the managers also do the technical coordination, but I find it better to just let the sys admins and developers talk to each other directly.

      I manage the conflicts with their manager if they happen. That discussion is usually based on business criteria, not technical criteria. Which is not to say that it is not technical, but honestly, I couldn't give a fig for what technology you want to use, but it has to allow us to meet our business goals. If you have a "better" technology that will require a lot of time and effort to implement at a difficult time? Guess what? You're using the old stuff until I can make the time and resources available to pay down on technical debt without blowing our commitments out of the water.

      Once the business decisions are made, however, the tech leads should coordinate without me having to become involved. DevOps is about making tools and decisions that allow Dev and Ops to make the transition to production ready features as seamless as possible by using collaborative methods and technology to unite these teams as two points in a process, not two bastions defending against each other.

  15. Satisfaction by Bo'Bob'O · · Score: 1

    For some people a satisfying job is an important part of their overall happiness, so even if they might be making less, still might be more fulfilled by their lives.

    Of course for other people the job is just 8 hours a day they can easily partition from the rest of their lives, and don't have any such concerns.

    There is no good or bad about one or the other, it's just how some people's natures are different. It is though, too important of a metric to be left out of an article like this. Graphic designers might be a good example of this. Some may be making less, but for them it might be more valuable on the balance for their mental state then the money.

  16. Oh Really. A Sample of One by caferace · · Score: 1
    As a SQA guy, I did have to laugh at this 'story'.

    Software QA Tester

    Entry-level salary: $51,322
    Average salary: $51,322

    At times I make near double that.

  17. Money by manu0601 · · Score: 4, Insightful

    Money seems a bad metric to choose a job. Once it pays enough, having an interesting job is quite important, since you are going to spend at least 8 hours a day at it. Job security can also be another important point: who cares a high wage if you are going to be fired within 2 years and remain unemployed after that (hint: another technological bubble exploded)

    1. Re:Money by Anonymous Coward · · Score: 1

      Money seems a bad metric to choose a job. Once it pays enough, having an interesting job is quite important, since you are going to spend at least 8 hours a day at it. Job security can also be another important point: who cares a high wage if you are going to be fired within 2 years and remain unemployed after that (hint: another technological bubble exploded)

      Pay me ten times a minimally acceptable wage for two years and I can retire the next eighteen doing what I want.

    2. Re:Money by dargaud · · Score: 1

      Pay me ten times a minimally acceptable wage for two years and I can retire the next eighteen doing what I want.

      Not necessarily because by then you'll have a loan on an expensive house, a bunch of kids on the way and a greedy mistress.

      --
      Non-Linux Penguins ?
  18. Re:Not me! by Anonymous Coward · · Score: 1, Funny

    I make a seven figure salary as a consultant fixing Admin screw-ups on AIX systems for large hospitals so the DBAs can do their work. Jimmy, is that you?

  19. Re:The Job Title doesn't matter.... by Anonymous Coward · · Score: 1

    There's a degree for "Help Desk" support! Am I the only person that sees that as, obviously a waste of time and money?

  20. Digital Forensic Analyst by neghvar1 · · Score: 1

    As a digital forensic analyst, I began at 45K after graduating from Champlain College. Now I make 87K

  21. Familiar jobs ... by Anonymous Coward · · Score: 1

    These reviews always seem to only include the IT jobs everyone's heard of. Where do SAN Admins fit in this? Or enterprise backup? As a storage area network admin, I do pretty well and have a degree in Theater, with no certs at all. And I recently saw a job posting for Avamar/Data Domain for $105k, in a medium-sized market.

    1. Re:Familiar jobs ... by El_Oscuro · · Score: 1

      SAN Administrators? Man you guys nned to be paid some serious $DOUGH. That shit is gnarly. An EMC (Even More Complicated) tech tried to show me mapping and zoning and my head was ready to explode after 10 minutes. I'm just a user, a low life DBA. All I know is how to set up BCV backups and restore from them. I practice that shit because my job depends on it, but everything else, no, I'll leave it to the experts.

      --
      "Be grateful for what you have. You may never know when you may lose it."
  22. Re:The Job Title doesn't matter.... by Anonymous Coward · · Score: 2, Insightful

    If you did not make it up the IT ladder, some of it may be your manager(s) fault but I'd say even without knowing you, it was more than likely yours. I started at my current company as a Tier 2 tech in one of our regional offices making roughly 50K/yr. I was a desktop admin, a network admin, a systems engineer, I expanded into VM and then storage, and eventually voice and networking, now eleven years later I am the infrastructure manager sitting over 7 engineers in our world wide operation and my salary has tripled. I am still physically in the same regional office and 6 of my 7 guys are are not even in my physical office, they are spread across two different offices, most at our headquarters. My situation is not unique. Many of us have worked our way up but also.. a person that started 2 months after me in the same regional office is still here and still a regional Tier 2 tech.

    If anyone in your company doing IT is getting promoted and it is not you, don't blame the other guy. If the situation is "bad" and people have it out for you, then go somewhere else and try again. Don't blame others for you not getting promoted. Those engineers and managers at your current company did not start at 20 as senior engineers and managers. They did it somehow. Take responsibility for your career or be happy and comfortable where you are, that is your choice. Just don't complain about a choice YOU made.

  23. The Dice are loaded ..... by King_TJ · · Score: 2

    I have to admit that I haven't even looked at the job listings on Dice for years (largely because I've been happily employed and didn't feel the need). But as someone with a background in network/systems administration, PC support, etc. -- I distinctly recall finding FEW interesting listings on Dice. The web site seemed slanted towards those looking for software coding or web development jobs, DBAs, or specialists in rolling out and supporting large ERP packages.

    So when a survey from Dice tells me that there's more growth, opportunity and money in all of those areas -- I have to take that with a grain of salt.

    I mean, look.... I think we should all know by now that help desk jobs are a dead end, unless you're with one of the few remaining companies who hires from within and essentially demands you do your time on their help desk to earn the right to one of the better positions in I.T. they offer. We don't need a survey to tell us that. There's a whole group of jobs out there that tend to have titles like "systems specialist", "support specialist", "support analyst" or even "network manager" where you're likely to wear multiple hats. Often, these turn out to be jobs where you're really the only full-time I.T. person for a small business who finally decided to get serious about I.T. and quit hiring consultants at hourly rates whenever they screwed things up. Other times, you're part of a team who does everything from help desk type support to ensuring backups run to making recommendations for upgrading the whole infrastructure.

    I find these positions to be right up my alley, in the sense they aren't as likely to get boring and I get to "call the shots" more and more often, as I get established in such a role and prove to management that I know what I'm doing. (You probably won't make big $'s in these positions, but you'll get your hands on all sorts of different things and get a decent shot at working for a business where you're not just a number or line-item in a spreadsheet.)

    So sure.... Dice can hawk the software development side of I.T. as "where the money's at!" -- but I'm good doing what I do, thanks.

  24. Re:Not me! by Zero__Kelvin · · Score: 2

    "UNIX Administrators (notice I didn't say Linux) "

    I did notice that, actually. I also noticed that you are either too lazy, too stupid, or too ashamed to log in as you say it :-)

    --
    Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
  25. Ouch. by antdude · · Score: 1

    SQA jobs hence why I got laid off over a couple months ago. :(

    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  26. Re:The Job Title doesn't matter.... by Per+Wigren · · Score: 4, Interesting

    You actually kind of proved the point because you are not an engineer/admin anymore, you are now a manager. It's a pretty sad cultural quirk that the target of every so called "career path" always tend to be some kind of management, removing the best engineers from what they do best if they want to have a good salary.

    --
    My other account has a 3-digit UID.
  27. Network Architects and Engineers by Anonymous Coward · · Score: 1

    I noticed there's no ROI mention here. Interesting.

  28. Re:The Job Title doesn't matter.... by RabidReindeer · · Score: 1

    Those who can, do.

    Those who can't, teach.

    Those who can't teach, manage.

    Those who can't manage, administrate.

  29. Re:The Job Title doesn't matter.... by Culture20 · · Score: 1

    "Those who can, do. Those who can't, teach."
    This is a reason/excuse for pay reduction.
    "Those who can't teach, manage. Those who can't manage, administrate."
    And these two jobs have sudden pay raises over those who "can do"

  30. Re:ROI? by gmhowell · · Score: 1

    Pretty sure it means 'return on investment' in this context, but as they don't supply the cost of the investment, the location these salaries are drawn from, the number of years after the degree, etc, etc, etc, it's just another bit of Dice-tastic link bait.

    --
    Jesus was all right but his disciples were thick and ordinary. -John Lennon
  31. Re:The Job Title doesn't matter.... by Anonymous Coward · · Score: 1

    I CHOSE that route based on the options presented. I spoke with my fellow engineers at the time and got their backing. I only got the supervisor position because of their support. I could have stayed as an engineer, held out or pitched for an architect position. I could have left and went somewhere else for an arcitech position. The point is you cannot blame others or "them" for your lack of moving up no matter what track or disipline you are doing. In my specific case supervisory and management is not my thing but luckiliy I am still involved in the day to day because of the relationship I maintain with the team and the "middle" sizing of our IP department. IT is my second career and I've only been doing it for 15 years. I am losing interest in it. I exited completely out of my old career (nuclear power) for the same reason. As soon as my 20 something kids move out, I'll move on to a totally different career. I've recently got a welding certification and I'm completing up what I need for my HVAC certification. I"ll start at the bottom again and see how far those can get me.

  32. Re:The Job Title doesn't matter.... by JaredOfEuropa · · Score: 2

    There is a problem with the IT or technical ladder itself in many companies where IT is not core business (and even in some where it is). The ladder can be rather short: Junior / Medior / Senior tech (and senior can be someone with as little as 5 years experience), then you basically leave tech and be project manager, line manager or the manager of a division or competence center or some such. A few rock stars may stay in tech as Principal Consultants, but those are rare (and often not promoted from within).

    In many companies, there will be a few clever techies who are recognized as being very knowledgable in their own area of expertise as well as having a wider and forward looking view, and who are consulted on where to head the company's strategic direction. Such a techie may be promoted to management (and possibly do a crap job at the people and process aspects of that), or the existing manager may continue to draw upon his best techies to help him strategize, but why not turn it into a role? Some companies do, but I don't see it very often and it's a shame, because it can be a very nice role for a senior tech to be promoted into, increasing his value to the company as well.

    --
    If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
  33. Feature Request User Story by Fnord666 · · Score: 1

    As a slashdot reader I would like to filter stories by submitter so that I can save myself the pain of seeing articles from Dice shills and other self promoters.

    --
    'The tyrant will always find pretext for his tyranny.' - Aesop's Fables
  34. Re:The Job Title doesn't matter.... by luis_a_espinal · · Score: 4, Insightful

    Those who can, do.

    Those who can't, teach.

    Those who can't teach, manage.

    Those who can't manage, administrate.

    What a load of unsubstantiated ideological crock.

  35. But us SE's want DBAs by NotSoHeavyD3 · · Score: 1

    Since as a software engineer I completely admit you know way more about databases than I do.(You're worth every dollar you get paid.) The problem is so many managers think "Oh we don't need DBA's, you SE's can do it. It'll be just as good. Oh and we don't need release engineers either since we'll save money by having the SE's do that as well." (Yeah, right.)

    --
    Did you know 80 to 90% of the moderators on slashdot wouldn't recognize a troll even if one dragged them under a bridge.
  36. ROI depends on investment as well as return by billstewart · · Score: 1

    The original material talked about salaries and job titles; it didn't say how much investment it took to develop the skills to get those titles. Some of those skills are things you can add quickly; others take a long time or access to appropriate work environments. (For instance, learning PHP is quick, and Ruby on Rails isn't that hard either. But while you can learn SQL and MySQL pretty quickly, becoming a DBA really needs access to real-world databases and workloads that you're involved in administering.)

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks