Slashdot Mirror


Study Says Software Engineers Have the Best US Jobs

D H NG writes "According to a new study by CareerCast.com, software engineers have the best jobs of 2011 in the United States, based on factors such as income, working environment, stress, physical demands and job outlook, using Labor Department and Census data. Mid-level software engineers make between $87,000 and $132,000 a year, putting them in the top 25% of the 200 professions studied by income. Software engineers beat out last year's number one job, actuary, which came in third, behind mathematician."

46 of 337 comments (clear)

  1. Software engineer vs. computer programmer? by Mad+Marlin · · Score: 3, Interesting

    Software engineer: $87,000; Computer programmer: $71,000. It is weird that they break those two up.

    1. Re:Software engineer vs. computer programmer? by Anonymous Coward · · Score: 3, Interesting

      As someone who's worked in the field for a decade (and who survived the CS department at Cal), the difference seems to be that of executive assistant versus secretary. What are the connotations you have for the terms, and where did they come from? My wild guess is if back in the days of punch cards, the programmer fed the punch cards to the computer and the engineer wrote them.

    2. Re:Software engineer vs. computer programmer? by blair1q · · Score: 4, Insightful

      Not really. Since it's self-reported, it's up to the person checking the box to bin themselves. What we learn here is that people who shy from calling themselves "software engineer", or are labelled "computer programmer" by their company's org chart, make less than people who report in as "software engineer".

    3. Re:Software engineer vs. computer programmer? by darkstar949 · · Score: 3, Insightful

      From what I have seen in my time in industry, companies typically have fewer software engineers than computer programmers and while both roles will have employees sitting at a computer writing code, the software engineers will also spend a good deal of time designing the overall architecture of a system. Likewise, the software engineer is also generally the more senior level position and may also be the first person to take heat when a major problem is found in a system.

    4. Re:Software engineer vs. computer programmer? by frosty_tsm · · Score: 4, Insightful

      Not really. Since it's self-reported, it's up to the person checking the box to bin themselves. What we learn here is that people who shy from calling themselves "software engineer", or are labelled "computer programmer" by their company's org chart, make less than people who report in as "software engineer".

      Maybe it's because those who know the difference also know how to make themselves more valuable.

    5. Re:Software engineer vs. computer programmer? by AuMatar · · Score: 2

      From my time, the terms are interchangable. The org charts and the business cards call everyone a software engineer. In normal discussion, everyone uses the term programmer or coder.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    6. Re:Software engineer vs. computer programmer? by Antisyzygy · · Score: 2

      Dunno about that. Software engineer is just a hyped up term. If you can list yourself as that rather than a computer programmer it makes the layman think "Oh shit, hes an engineer we need to pay him a bit more". Its like being called a "mathematician" versus a "topologist", "algebraist", "analyst", "graph theorist", or "geometer". They make you think one person has some knowledge the others dont have, but really they all are just mathematicians that each have a particular specialty just like maybe an undergraduate "software engineer" specialized in operating systems or computer graphics. They could still probably do eachother's job if they had time to read up on it.

      --
      That brings me to an interesting point, / . is just "the ramblings of socially-inept, technology-literate news-mongers".
    7. Re:Software engineer vs. computer programmer? by 0xdeadbeef · · Score: 4, Informative

      Jesus fucking Christ you people are retarded. There is no "traditional" background for the "programmer" title, and while a lot of people want "software engineer" to mean something, it doesn't, because the industry doesn't give a shit.

      In fact, reality is quite the opposite of what you're saying. MIT and Stanford do not give out "software engineering" degrees. They have schools of computer science, and the give out CS degrees. Every top tier school gives out CS degrees. Only the diploma mills have "software engineering" programs, because they don't have the chops to teach real CS.

    8. Re:Software engineer vs. computer programmer? by 0xdeadbeef · · Score: 3, Insightful

      I mean "software engineer" in lieu of a CS degree. Most schools pay lip service to software engineering, from individual classes all the way to dedicated research programs (like CMU).

      But software engineering is nothing more than applied CS. It exists to serve the needs of industry. The people promoting it as some sort of status symbol are delusional.

    9. Re:Software engineer vs. computer programmer? by AuMatar · · Score: 2

      Perhaps not in their original use. But in practice they are. My title has said senior software engineer or principal for 4 or 5 years now. I'm not about to call myself one though- too big a mouthful. I'm a coder or a dev. If I need to be semi-formal I'm a developer or programmer. The term "software engineer" isn't ever used outside of resumes and business cards. And truthfully I've never seen anyone hired as just a programmer- what you term is what we tend to hire as juniors, and expect them to grow into bigger roles. Of course I never work for places that just make quick websites or the like, not my cup of tea.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    10. Re:Software engineer vs. computer programmer? by jedidiah · · Score: 3, Insightful

      So now you're going to conflate CMU with the diploma mills?

      --
      A Pirate and a Puritan look the same on a balance sheet.
    11. Re:Software engineer vs. computer programmer? by aclarke · · Score: 2
      You're very wrong on this point. I'll use my alma mater as an example: the University of Waterloo in ON, Canada. Please see their software engineering home page: http://www.softeng.uwaterloo.ca/. Waterloo also had the largest Math & Computer Science programme in the world at one point, although now that they're (AFAIK) broken into two separate faculties that's probably no longer the case.

      The University of Waterloo also happens to have been Canada's top-ranked undergraduate school for something like 18 of the past 19 years by Mclean's magazine, so I'd hardly call it a "diploma mill".

      I'll even give you a little quote from UW's software engineering home page:

      Software engineering is a systematic and disciplined approach to developing software. It applies both computer science and engineering principles and practices to the creation, operation, and maintenance of software systems.

      At the University of Waterloo, Software Engineering is an independent, interdisciplinary program supported by both the Faculty of Mathematics and the Faculty of Engineering. Graduates of this program will earn a Bachelor of SoftwareEngineering (BSE) degree.

      There is a reason that one of the most highly regarded engineering AND computer science schools in the world sees the need to have separate programmes for both computer science and software engineering. It's because they are different. They are similar, but not identical.

      If you think that the term "software engineering" is a meaningless, self-appointed term, then you're right. It's because, in most of the US at least, "engineer" is not a regulated professional term whereas maybe it should be. Generally, I'd say that most people calling themselves software engineers are not software engineers. That doesn't mean that it's not a valid profession with valid differences from being a computer scientist or a programmer. We just need better ways of weeding out the people who like to call themselves software engineers from those who actually are.

    12. Re:Software engineer vs. computer programmer? by OutputLogic · · Score: 2

      Those who design the overall architecture of a system called software architects

    13. Re:Software engineer vs. computer programmer? by Ixitar · · Score: 2

      So, you are calling the University of Minnesota a diploma mill? You should avoid such sweeping statements. I am in the MSSE program myself. Here is the text from "Why an MSSE degree?":

      Advance your career with a Master of Science in Software Engineering degree. MSSE is a full-time, 2-year Master's program with a 95% graduation rate and is designed for working professionals.

      The need is clear

      Recently, a "skills development and preparedness" study was conducted in Maryland. This survey found that: "In the high-tech area, more than two-thirds of businesses that hire computer engineers, laboratory or technical personnel... reported difficulty in finding qualified workers. Overall, nearly 40 percent of survey respondents reported that a lack of skilled workers negatively impacted their firm's ability to do business..."

      Industry needs qualified leaders - those who can understand the fundamentals of a software system, and be able to guide its development and deployment through an organization. These leadership roles are integral to the success of a company, and are not easily outsourced.

      Critical thinking

      The Master of Science & Software Engineering (MSSE) degree prepares students to become Software Engineering leaders. The core of the program is focused on building a foundation of critical thinking skills on which to make professional judgements.

      Often, in the workplace, that's what is needed of an engineer - his or her professional judgement; to assess a request and judge whether it makes sense. 'Is the request reasonable?' 'Given the constraints of my organization, can something be produced that will be acceptable to the users?' 'Do we understand the risks?' 'If yes, how could a solution be structured?' 'After all is said and done, is it a good solution?' 'Why?'

      Theory and practice

      The MSSE program builds these thinking skills through a solid understanding of theoretical methods, principles, and tools and an examination of fundamental software development issues and processes. Topics include requirements engineering, project management, quality assurance, and database management systems.

      Acclaimed faculty with both academic and industry backgrounds also provide practical perspective. Real-world problems and opportunities with software intensive systems are explored, and methods to evaluate, adopt and take advantage of emerging technologies are learned.

      MSSE students will also be working closely with fellow software professionals, completing applicable class assignments within teams. Working relationships developed will be a significant resource throughout one's career.

      I design enterprise scale systems. That involves taking in to consideration many stakeholders concerns and being able to address then and to communicate the architecture to them based on their viewpoint of the system.

  2. Before slashdotters post with opposition views by Anonymous Coward · · Score: 2, Funny

    This study covers competent software engineers which might explain why your outcomes are so different.

    1. Re:Before slashdotters post with opposition views by MrEricSir · · Score: 2, Insightful

      If Wall Street proves anything, it's that competence and compensation are in no way related.

      --
      There's no -1 for "I don't get it."
    2. Re:Before slashdotters post with opposition views by Yvanhoe · · Score: 5, Funny

      Oh, don't be so harsh. There could be a negative correlation...

      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  3. Actuary? Really? by damn_registrars · · Score: 5, Funny

    I'm astonished that would be the top job last year. Personally, I'd rather shoot myself than be an actuary. But of course, a good actuary would already know that...

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  4. Job security by Anonymous Coward · · Score: 4, Insightful

    Assuming you can actually find a Software Engineering job that will stay in the U.S., yeah, they're the "best."

    1. Re:Job security by Anonymous Coward · · Score: 5, Funny

      someone has to fix the offshore teams' fuckups.

    2. Re:Job security by Lord+Ender · · Score: 2

      Salaries are set by supply and demand. Those salaries are high because companies can't find enough programmers.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    3. Re:Job security by Aargau · · Score: 3, Insightful

      I gather you're not in Silicon Valley? My small startup is having a really hard time the last 6 months competing against Facebook, Google, Zynga, Apple in hiring quality developers, even just out of college. Thanks to goldman sachs, we've also got 2000 people about to move into the real estate market with $10 million in fungible stock options as well.

  5. Of course it is. by tool462 · · Score: 5, Funny

    Where else can you get paid $100k+ a year to gripe all day on Slashdot about how crappy your job is?

    1. Re:Of course it is. by Grishnakh · · Score: 2

      Big GPUs aren't going to help your compile times, and an i7 Extreme isn't all that great. If you really want to give your programmers/software engineers a powerful machine so they aren't wasting time waiting for compilation, you need to get them a 2 or 4-processor Xeon system (with each CPU having 4 or 6 cores). When compiling, the more cores, the better: "make -j x" takes care of everything. On top of that, 16 or 32GB of RAM, and a big and fast RAID array. The nice thing is you only need one of these powerful machines, and your whole team can share it, since it's unlikely that everyone will be compiling at once.

      Using a desktop machine for heavy-duty compilation, and wasting money on video cards of any kind, is just dumb.

  6. Scared me for a second. by Maltheus · · Score: 5, Informative

    The 132k figure is not for mid-level engineers (although maybe it is in a big city). The actual quote from the article is "Most earn a typical mid-level income of about $87,000 and top out at $132,000". Makes me feel a little better and it's maybe the first time I RTFA in over a decade of visiting here.

    1. Re:Scared me for a second. by timeOday · · Score: 2

      On top of the fact that salary normally increases rapidly near the start of one's career, you timing for starting your career was very unlucky, with the bad job market. I suspect you may be able to wrangle big raises as the market improves, but you'll likely have to switch jobs to get them. IME employers find it acceptible to pay big bucks to get the shiny new guy, but harder to pay the same amount to retain those for whom they're accustomed to paying less.

  7. eh by buddyglass · · Score: 2

    I'm 10 years out of college and make at the low end of that range, though I live somewhere that's relatively cheap compared to most hotbeds of software development. I work 40 hours a week (sometimes a few less) and probably spend 25% of that not doing anything productive in a work-related sense. So from a "money per unit effort" sense I'm pretty well off. From a "doing something that is intrinsically rewarding and gives me a sense of pride and accomplishment"...not so much.

  8. Re:Obviously, you're not a golfer. by Monkeedude1212 · · Score: 2

    Nah, you really don't.

  9. I think that it's sad, really... by mark-t · · Score: 4, Insightful

    ... that so much of the perception of how good a job is would be derived from how much money one makes doing it.

    1. Re:I think that it's sad, really... by blair1q · · Score: 2

      It's only one of the five criteria they combined to produce their metric.

      And they probably under-weighted it.

      How much money you make may not have a lot of bearing were it not for studies like these that show you where your pay fits in the scale.

      That will either make you happy or unhappy, or both at the same time, on the spot.

      Me, I'm whistling at the moment.

  10. Re:Actuary? Really? by swillden · · Score: 4, Informative

    You'll notice that the criteria don't include "intellectual fulfillment." Actuaries rate pretty highly in all the criteria the study considers, but perhaps their job is not as interesting as some others.

    I know some actuaries, and they find their jobs very intellectually stimulating and fulfilling. For people who really like math and statistics, doing it professionally is enjoyable and challenging. It's not like actuaries spend their days adding up big columns of numbers -- we have computers for that. Actuaries figure out how to use sophisticated statistics to tease out subtle patterns from large masses of information. It's challenging and the results are often surprising.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  11. Mathematician's rank contradicts the old joke: by 1yongyorf · · Score: 5, Funny

    What's the difference between a mathematician and a large pizza?

    A large pizza can feed a family of four.

    1. Re:Mathematician's rank contradicts the old joke: by Monkeedude1212 · · Score: 2

      Unemployment among mathematicians is very, very low.

      But that's because there are very few people who class themselves as mathematicians.

      That's because Mathematician isn't a job. No one would claim their job is a Mathematician unless they were specifically getting paid to do research into math - which is very rare. Often you are paid to teach Math at a university while persuing your study of mathematics.

  12. Stressful job, but not a bad one by Mean+Variance · · Score: 5, Informative

    I have carried the title "Software Engineer" for 13 years. I'm of mixed opinion about how great the job is. It pays pretty well, but much of that is relative to what you're comparing to.

    There are worse jobs out there, no doubt, but we're not just coders at least in my experience and many people I know in Silicon Valley. You have to read a lot of boring documents. You have to know how to write. There are meetings. There are customers to talk with. For me what makes it "not the greatest job in the world" is that it's stressful in a way that people don't understand.

    Deadlines always loom, and they are always too short. A good SE has to constantly decide where to unit test, design, explain to management, or just hack to get it done. There's no worse feeling when management decides that a project is taking too long and asks "who can we add to the project?" like we and our code is just plug-n-play factory work.

    That is stressful and few people understand the kind of stress created on the job. I'm not asking for pity. It's a good gig overall, but sometimes I wish I would have stuck with my original, lower paying pursuit of teaching junior college mathematics.

    1. Re:Stressful job, but not a bad one by bzipitidoo · · Score: 4, Informative

      I don't buy this article. The article claims software engineering is low stress. No way! You say software engineering is moderately stressful. Closer. I say it's often much worse. Many of the software related jobs I had were extremely stressful.

      Software projects are notoriously difficult to plan, schedule, and execute. Just figuring out a goal can be difficult. Even good planners can be way off with their estimates. But many people don't have a good grasp of what computers can and cannot do, and it is very easy to step across the line from asking for a mere number and data crunching app to asking that the capabilities of human intelligence be exceeded. Or that it scale to impossible levels. They think they're asking for something easy and trivial, and fail to understand they're asking for perpetual motion. "Scope creep" is endemic. Communication is difficult. Often businesses discover that the engineers were asked to solve the wrong problem. Add that lack of understanding to suspicious, adversarial management 'tards who feel that coders (and everyone else) are just naturally lazy slackers, and you have trouble. Are the coders telling it straight, or are they making mountains out of molehills in a big conspiracy to make their lives too easy, or because they're a bunch of wimps?

      Deep Thought didn't usher in a new era of AI superior to human intellect, instead it demonstrated that chess is amenable to number crunching. I like to put it this way, that computers can compute for you, but they can't (yet) think for you. You must still ask good questions, choose good directions to pursue, otherwise it is like the old saying: garbage in, garbage out. When management doesn't get this right, it is stressful for everyone. It's a hard problem that is often got wrong.

      Most software projects end in failure. Why is a big question-- is it that software engineering should be no more difficult than any other engineering endeavor but we still suck at it because it is still a new discipline, or is it that software engineering really is harder? The questioning of the professionalism of the software engineering discipline is yet another doubt to add a tiny bit more stress. Or that typical expectations are way off base? By one measure I heard, roughly 30% of projects are total failures, 30% are only partially successful, achieving only some of the goals, and 30% are successful but late. Only 10% are successful and on time. And failure is stressful and hateful.

      Another thing adding to the stress in software engineering is that there is very little downtime. Many jobs have slow days, but in software engineering, you can bang away at the keyboard every minute you're on the clock. On those rare occasions when downtime does happen, it isn't a chance to relax. More often it adds to the stress. Just like a meeting, downtime is taking away time you need to meet your schedule.

      At the worst such job I had, we had management who had no clue how to plan anything, and zero interest in honestly trying as they were much more concerned with the infighting, each trying to make sure it would be the other guys who were eventually fired. They weren't about to listen to or solicit input from each other, let alone any uppity engineers, so each was making up their own plans and schedules in a vacuum, and trashing the others. Since they didn't know a real schedule from a load of buzzwords and bull, they couldn't see it when someone managed a miracle, and would reprimand the guy for not being even faster! Beating up the engineers for being too slow, incompetent, and stupid, in absence of any metrics whatsoever to make their case, was SOP for them. No matter how much evidence there was that that kind of management was counterproductive, their answer was to flog everyone harder. In hindsight I should have quit that job much sooner.

      --
      Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
  13. $132K is a bit low for top-tier engineers by jmcbain · · Score: 5, Informative

    $132K as an upper bound sounds about right for mid-level engineers but is a bit low as an upper bound for senior software engineers at large corporations. Principal software engineers at Microsoft are paid at around $160K with fairly huge bonuses that push their yearly pay to nearly $200K. Staff software engineers at Google and others are in the neighbourhood. Note that these are cream-of-the-crop engineers who have chosen to stay as ICs rather than go into management. Source: personal knowledge and glassdoor.com.

    1. Re:$132K is a bit low for top-tier engineers by Anonymous Coward · · Score: 3, Informative

      It's the same at Apple. I'm a level-5 software engineer. I'm on circa 170k + bonuses (mainly in shares). I'll pay taxes on about 300k this year because of stock vesting - although Apple's stock has risen dramatically in the last few years.

  14. Re:Electrical engineer vs. electrician? by dlgeek · · Score: 2

    Automotive engineer (the guy who designs the engine) and mechanic?

  15. Re:Mid-Level $132k, really? by company+suckup · · Score: 2, Interesting

    Well in that case I'm sure Grand Island, NE. would love to have you.

  16. Re:Mid-Level $132k, really? by CrashandDie · · Score: 2

    European here. After a few years in London and then some time in Australia where things didn't pan out so great, I decided to head back to the old country, south of France.

    Turns out I only lost about 10% on the salary, when really, I expected the cut to be more something like 30-40%. Turns out that if you find the right employer, they will go the extra mile if they've estimated your worth correctly.

  17. Not what I've heard. by RackinFrackin · · Score: 2

    I seem to remember a guy named Steve saying that there's better money selling magazines door-to-door.

  18. Re:Actuary? Really? by tchuladdiass · · Score: 2

    If you don't find that you are getting a good deal with insurance, then why buy it? Except in cases where you are required to (minimal car insurance, or full coverage if you have a loan). For example, I never buy extended warranties on electronics (I consider that a form of insurance), because in my experience it would cost more than it pays back in the long run. Another example, if you are a teenager driving a $8000 car, it doesn't make sense to pay $4000 a year for comprehensive collision insurance.

  19. Re:meaningless question by Grishnakh · · Score: 2

    My last job had a lot of those traits: great pay for local COL, no physical labor, not terribly difficult work. I almost never had to talk on the phone either. However, the work environment was horrible: I had to sit in a bull-pen environment, with all kinds of noise and distractions around me. I finally quit because of that. I simply couldn't concentrate with people interrupting me and having to listen to conversations around me. I also was fed up with never knowing what was going on, as the company had a policy against having meetings to disseminate information. The last straw was when I was told that I was expected to learn about the company direction, what's going on with the project, etc. by overhearing it.

  20. Re:Actuary? Really? by Joking611 · · Score: 3, Informative

    As someone who spends $1,400 a month on private health insurance, I spend it because the risk of someone in the family needing a 6 figure treatment is worse. Since the risk is actually low, I don't consider it a good deal. A child's health has a different weight than that $8000 car.

    --
    www.joking.net
  21. Hmmm by JimboFBX · · Score: 2

    Where are these high paying jobs they speak of? And how much do they really make after you take into account all the high paying jobs are in places with a high cost of living to go with it, and the lower paying ones.. well you get the idea. Everyone in California makes ridiculous amounts of money even though their job is usually perfectly transplantable elsewhere. With so many tech jobs in that state it really skews the numbers. How much does a "software engineer" make in a humble small town in a red state? Usually not so much...

  22. Re:Actuary? Really? by Z8 · · Score: 2

    You obviously know nothing about the industry. Many insurance lines (especially liability) are in a "soft market", and effective rates have been decreasing for several years, often by 5%+ a year.

    If you don't buy liability insurance you may not get that example. But you probably know something about car insurance. On a loss ratio basis, companies like Progressive and Geico attacked the auto market and won market share from companies like State Farm and Allstate. Their secret? More sophisticated and efficient pricing algorithms, which enabled lower prices for many drivers.

    Your whole post doesn't make any sense anyway—insurance is a competitive market; if they were really screwing their customers, new companies could just enter and take their profits. It only takes a few guys to start an insurance company and there are about 1000 registered in the US.