Slashdot Mirror
How Much Money do Programmers Really Make?
bigman2003 asks: "ADTmag.com recently released a list of average salaries for IT workers. Usually when I see these lists, I find out that I am grossly below the average salary. But this time I was very surprised to see that I am actually above the average! This is partly because of a recent raise, but it is also because the numbers quoted in this survey are lower than what I've seen the past from other surveys. This report quotes about $56,000 for the average application developer. I am a web developer (sure, laugh all you want) and I wanted to know specifically: How much are other web developers were making? And- How many hours a week does it take you to make it?"
It's not that easy. Where you live, standard of living costs, specialized training and abilities, years of experience, etc, all influence and alter this. Averages give you an idea, but you have to go on your abilities and what you can find. If you like your job, it often means more than an extra 5-10k per year. I think the real issue here is that people like to know how they rank compared to others, and reality is way to gray for that black & white approach.
Microsoft Sucks, F/OSS Rocks. I get mod points now right?
How much you make is pretty meaningless without normalizing by cost of living. $50k in Idaho is effectively 2x as much as $50k in San Francisco.
-me
I don't know if this is true of every company, but it wouldn't surprise me, since global companies make the same profit from your work, no matter where you live.
So, as I see it, at least with my company, living in the heart of an urban area is something that comes straight out of employee's pockets, since it's primarily a benefit to the employee (we're a tech/manufacturing company, not a financial/investment firm or anything that might more reasonably REQUIRE you to live in the heart of a large city).
I'm a web developer, doing fine, but I'm not really conformable divulging what I make on Slashdot.
I don't mean this as a personal slam, but that exact attitude keeps salaries low. Why NOT talk about your salary? If you don't talk about it, you can't know how you compare. And although you might not care how you compare in a rat-race sense, you damned well should care that your employer treats you "fairly"...
Me, I make just a hair over $40k. Sound low, for someone with 10 years experience? In my area, I can afford a mortgage on that. And together with my SO, as a DINK couple, we do pretty damned well combined.
TALK about your salary! Don't brag about it, that just sounds obnoxious, but chat. Make sure that neither you nor your friends have gotten royally screwed.
I will never understand people who have this phobia of discussing how much they make. If you make something truly obscene (either minimum wage or seven figures), okay, you might have a reason to shy away from the topic - But within an order of magnitude of "average", help create a basis of comparison! It only hurts us, the workers, to remain tight-lipped about it.
A salary survey is nigh useless to begin with, and this one seems to be worse than normal. "Average salary" - what's that? Median or mean? Where's the standard deviation? What does 'broad spectrum of organizations' mean? Is it geographically diverse?
Here's another hint: a survey requires people who answer surveys. I'm going to go out on a limb and say that people making on the high end do not generally go out of their way to answer salary surveys, whereas people paid average or less than average might be a bit prone to worrying about their salary and therefore filling out surveys and looking them up.
Want to make more money? Instead of asking what other people make, ask yourself:
* What can I do that other people (or most other people) can't? What makes me good? What's my strength? How can I be better?
* How much is what I'm doing worth? How can I use my skills to create a larger value for a company or client?
* How can I leverage my work to produce more?
* What have I done that has exceeded expectations, that could not have been predicted and is a boon for whoever pays me?
If you have already come up with good answers for the questions above, you're probably making way more than the average already.
Be in good financial shape. People living paycheck to paycheck hurt themselves because they end up afraid to take risks. Save up a large cushion of living expenses - while 4-6 months is a normal financial planner's estimate, make sure you can get an additional 12 month's worth by the time that 6 is up. With the 18 month cushion you can afford to try a lot of other things.
Finally, if you don't like what you're making, consider doing something else. A friend of mine is making over $20/hr plus benefits reading gas meters. If I was getting paid a lousy $50k to program, I'd have taken a job at his place and spent my day walking around outside. If you find yourself on the low rung, maybe this is just not what you're meant to be doing.
You are making too much.
You are responsible for the design and implementation of the entire system, and yet you allow a huge, honking unreliable single point of failure that can bring the entire operation to its knees - you. That doesn't smack of good systems design to me.
Trust the Computer. The Computer is your friend.
The best way to find out what you should be making is to get some job offers from other employers. If you are underpaid, then you will probably not have too much difficulty getting a better offer. This will also give you the opportunity to negotiate, without fear, with your present employer.
On the other hand, if you are better-paid than average, it will be hard to find a better paying job.
One of the best bosses I ever had told me (among other people), "If you don't think you are being paid enough, look for another job that will pay you what you think you are worth. You will soon find out if you are right." I eventually took his advice, got another offer, and my employer countered.
And don't be shy about asking prospective employers for what you think you are worth. They won't hesitate to tell you if your expectations are out of line. If they say "OK" too quickly, you know you set your price too low.
Does anyone have any idea what someone like that should be making?
A request to hire a second IT guy. You can't do everything reliably, even if you were paid to do everything.
> I still can not understand why the average pay of a well-seasoned applications designer is still no match to that of a recently-graduated MBA
That is the attitude of a Computer Science student or recent grad.
Look at any company. Find where the money comes into that company. See how close or far your position is to that money entering the company. That determines your salary right there.
A company doesn't mind paying salespeople (who perform well) plenty of money because it is clear what they are worth. They are bringing in the money that keeps the company alive.
MBAs are closer to the money. They are in a "profit-center" of their companies.
The programmers are pretty far from the money. In most companies they are in a "cost-center", ie: they are a cost that the company grudgingly pays as a cost of doing business. They would be eager to lower that cost.
At one place I worked a few years ago there were programmers who worked in the "back office" servicing the company-wide infrastructure and there were programmers who working directly for a "front office" department, ie: closer to where the money is made. I worked for a front-office department and made $120K for doing the exact same thing programmers in the back office were paid $60K to do.
Just follow the money...
- For the complete works of Shakespeare: cat
...you're only worth what somebody else is willing to pay you.
I've heard the same thing from my last employer and while it's hard to disagree with such hard-nosed economic logic, I think it breaks down for a lot of IT jobs because IT jobs tend to be pretty fluid -- they often flow around the rigid HR-type job descriptions. Developers admin systems, admins doing programming, DBAs doing admin tasks AND programming, guys (like the grandparent poster) doing it all. Immersively intellectually challenging work that involves taking calls once a week about spyware and why the Intraweb is down? Or repetitive tasks, but never suffering end-luzers?
The "other job" that may pay me more may or may not include more job responsibilities, but I can almost guarandamtee you that the other job will not end up being the "same" job.
And then there's the whole question of "pay". How much are some bennies worth? How much is it worth to have a job with a ton of flexibility with start-end times vs. one with real rigid work hours? And if the former is a 60 minute gauntlet of traffic and the other is a 10 minute walk?
A boss who's a dick but makes sure to hire a lot of sharp people? A boss who's a saint but tolerates nincompoops? A closed door office vs. a low-wall cube in a farm? 8 days off you can take whenever vs. 3 weeks that requires D-Day logistics to be able to take a single day?
All of these things jumble together to make the "someone who pays more" concept so untestable that it's hard to measure.
I saw my salary double between 1992 and 1997, and again between 1997 and 2001. Then the great tech implosion happened. My salary dropped to half in 2003, and right now I'm just coding "for free" letting the wife work as I watch the kids. Quite a rollercoaster ride, but honestly, I'm happier now than I have ever been. Here's why:
When you work in tech for someone else, you are creatively constrained. You look for creative outlets any way you can, but ultimately, someone else is in control of your destiny. You can tell yourself; hey, the creative, fun stuff I'll do in my free time! Yeah, right; your free time should be with your family and friends, not sitting in front of a computer, just like at work. Or maybe you think: my creative outlet is at work! Yeah, right...
Maybe you're the programmer; cool, someone else gets to decide the architecture. Maybe you are the architect; cool, someone else gets to decide your budget. Maybe you're the CIO, cool, someone else affects the architecture, and someone else actually build the sh*t, and if they do a sh*tty job, you're hosed. Yes, you can't do it all. You need to work on teams to tackle big things. But do you really get to decide, in any way, what those big things are? Or are you just being told to dig a ditch at a certain place, to a certain depth and width and breadth?
If you want to be truly happy, let go of the need for the material crap and focus on taking control of your own creative direction. WORK FOR LESS MONEY but take a greater stake in what you are doing. Freelance. Work on a small team. Work part time and free up time to follow your creative bliss. Or just live off the spouse for awhile. It's ok; 50 years ago it was *normal* for someone to stay at home.
Be proactive and choose who and what you rely on, keep things lean and mean, and INVENT; CREATE. Work hands-on at creating.
Remember this: in 20 years, when you look back, will you think "gosh, I'm glad I had a house with 2 more bedrooms, that extra car, those weekends at the cabin. I'm glad I had that extra TV in the bedroom, and took that trip to Florida every year!" Or will you think, "I made some cool stuff. We lived OK. I followed my dream."
If you're reading this, you're probably in tech. That means you're likely getting paid twice as much as everyone else anyways, simply because tech is still a valued commodity, no matter what the outsourcers or people stuck in dot-com-lala-land say. WORK HALF AS MUCH, and invest that extra time into an open source project that you care about... your karma will thank you.