Slashdot Mirror
Reasonable Salary for Entry Level Programmers?
An anonymous reader asks: "I will be graduating from college in May with a degree in computer science. I have begun the job search and gone on a few interviews. So far I have gotten two job offers which I am thankful for, but the salary seems low. I am not saying that I am too good to pay my dues and work my way up, but I could make more waiting tables. It is somewhat distressing that I have spent 4 years of college and years before that developing my programming skills. I am not trying to get rich, but I was hoping that the high level of skill required would account for something(no offense intended to waiters). Can anyone give me any insight about what a reasonable starting salary would be, for an entry level software engineer?"
...but it'll probably be paid in rupees.
The CB App. What's your 20?
Ill be graduating in May as well and the range Ive seen is 45k to 55k
You found a programming job in America?
The Bureau of Labor Statistics keeps this sort of data, though possibly with some significant lag time.
Try looking at: http://www.bls.gov/bls/blswage.htm.
"...It proves you can learn,"
I know a lot of college grads that prove you wrong Sir.
Note to self: No more arguing with the faithful.
If you're starting out, I have bad news - given the decreases in salaries for people who've had 10 years experience, I hate to say this but the timing of your graduation is QUITE BAD. Offshoring fueling the latter along with the economic downturn and I don't expect things to improve much.
I have over 10+ years in tech, worked at a major software company and left for the dot bomb craze. I gave up lots of salary for equity and while the company was profitable and public, the market tanked a mere few weeks before my first vesting period. Even if it hadn't the AMT tax would have probably screwed me over anyway.
Since then I've worked some side stuff, waited tables, had the stupidity to try to sell cars and only in the last few months have things returned to what I call "normal."
Never mind that I worked on shrink wrapped products, developed a source level debugger, have had lots of experience on both Windows and UNIX. It all didn't matter to anyone.
I have to say, despite returning to a salary level that bests my previous best. I'm a changed person. Save, save, save.
IT blows. That's my 2 cents. HR people simply care about the last six months and are clueless if you are well ahead of your peers. They don't have the capacity to make this judgement.
You could tell them you architected (as an example) SSH and Kerberos have encryption patents and they might ask some stupid arse question like "Do you know JavaScript?"
Anyone starting school today... my advice is forget tech. If you feel it in your soul (like you should do it), fine, go to a tech school like DeVry, start making money and save it. Going to traditional 4 year programs for CS is an utter waste of time. Way too much change and like I said it's always about what you did in the last six months.
How many people graduated with you? How many other schools graduated as many, or more people at the same time? How many programming jobs do you think exist? Granted, this number is growing, but still. As an electrical engineering major, I can tell that at least half the people that graduate aren't worth having in a company. They just don't retain knowledge and apply it well. Why should a company assume you're worth more money? You're going to have to prove yourself to them. For all they know, you're the guy like my lab partner, who did no design on a major project, built none of it, and wrote 4 of a final report when I asked him to write six. Of his four pages, I totally rewrote one, made him rewrite one, and had to correct all his others. One of the mechanical engineers that I work with has a resume that would impress people at NASA and JPL, but in reality, he knows very little. Considering the number of graduates who know very little these days, I think you should be happy for a job. Besides, you ought to take one based on what you'll be doing, not so much how much money you'll make. With a CS degree, those dreams of high salaries you had going into college faded while you were there. Work your way, and be happy with it.
while it seems like the dotcom craze is over, we are really still at the dawn of what the internet and personal computers can do... it will be decades before this tech has realized it's full potential and the arc of innovation wanes and computers/ internet become just another commodity like the cotton gin or the radio
therefore, within the span of your lifetime, there is much impact you can make on this world, personally, and of course, financially
so after you come home from your thankless soul-sucking underpaid 9-5 existence, don't forget to tinker with the very sparks of imagination which got you interested in computers in the first place
someone reading slashdot right now, either you, me, or someone else, will probably be making a contribution to mankind in the field of computer science which will forever alter humanity, and perhaps make that person fabulously rich... but that's an afterthought
your prime motivation should be happiness, not money
no six figure slary is worth self-hatred
don't give up on any of the things that got you interested in computers in the first place just because you can't seem to find your happiness in a cubicle
you will never be happy working for someone else, you will only be happy pursuing your own interests
so think of your job as something to keep your brain cells well-exercised, and something that keeps food in the refridgerator, and therefore you won't look to your salary as some end-all justification for your existence
your job will forever be little more than just a means to an ends, unless you yourself are deadset on making your life little more than what your employer decides you are worth, and that would be a sad day indeed
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Assuming you are single, and just out of collge, and still willing to share an apartment to keep costs down, take any job offering $30k or more, AND is something you are interested in or could see a future in. In other words don't get hung up on salary alone, but consider what you want to do with your career and what you want to do. If you don't know exactly what you want to do with your skills, consider jobs that might offer a variety of opportunity. Remember, like any job, there will be pluses and minuses and you might have to reall look to see what the opportunities are.
As for the money, remember the dot com days are over, and paying your bills while getting your career going is not a bad way to start in the "real world".
They can suck you into the 80 hour week at any salary. Likewise, many $50k plus people are adept at avoiding the 80 hour work week. You only get 45 hours of work done in an 80 hour week anyway.
I really would be looking more at the company and projects than the salary. If the company is full of people making good money, then you will likely get good raises.
Employers look for progression in your salary. Going in low and getting a good raise in the first year can really jump start a resume. Leaving without a good raise makes you look bad.
So, if it looks like a company pays well, then going in low is a wise choice.
Considering that professors can often get grad students to work for free, it looks like someone in that university is pulling strings and doing one of their friends a favor by hiring you (a HS student) for pay. Take full advantage of the opportunity.
As for the original poster talking about entry level programming jobs: "Whatever the market will bear is fair".
Jobs are like relationships. It's always easier to get a new job offer when you've already got an existing job -- even a crappy one.
If you're working at Foocorp, a hiring manager at Barcorp knows you must be worth something (or Foocorp wouldn't have hired you) - and he also knows that you must be interested in Barcorp (because you've already got a job at Foocorp, so you're interviewing for reasons that go beyond "I'm unemployed and need food").
Same thing applies in relationships -- ChickFoo obviously digs your stuff, and that makes your stuff more interesting to ChickBar. (No, I'm not gonna let myself write that as "BarChick" :)
skill is the application of knowledge. A degree is proof of knowledge, and thus proof of possibility of skill, which is much more certain than someone with no degree. Even so, I think you're just being flippant.
Of course, someone with 10 years of experience would have the most demostrated ability which is why those persons make the most money.
-Ryan
AUWYHSTOT (Acronyms are Useless When You Have to Spell Them Out Too)
Oh please. Unless you are Ivy League, nobody bumps your salary because you graduated from a certain college. IT Managers aren't THAT dumb anymore....quit fooling yourself.
"I threw up my hands in disgust and wondered if it had been such a good idea to have eaten my hands in the first place."
I am also persuing a degree in ComputerScience. I am working on a combined Honours with Computer Science and Philosophy, but am planning on getting a Master's or PhD. I was wondering about how much does having OSS development on your resumé improve your chances? Does it count for anything in the 'real world'? Do employers look at it as 'real experience' like as if I had been been employed? Really what is it all worth? For anyone hiring what are you looking for? Would say that a Philosophy degree brings a little something more to the table (I'm taking philosohy because I enjoy it and find it more intellectually demanding than under-grad CompSci, not for monetary gain, but I do figure it should at least show that I am a flexible thinker)? How about non-CS job experience?
Your CPU is not doing anything else, at least do something.
Here's some job advice for the recent computer graduate in today's economy.
1. Join the military and get into an intelligence specialty. If you plan on working with computers after you get out, I suggest Navy or Air Force though I know a great sys admin who was a Marine.
2. Get and keep a security clearance. Don't let it lapse. Don't do drugs or, God forbid, marry a non-U.S. citizen. Always pretend that you agree with everything George says and repeat after me: "Hanging is too good for anyone from France".
3. Earn 35% more (at least) once you get out and you don't even need to have any skills or a degree. Your job will be safe from outsourcing, there's a thousand Beltway Bandits begging for your resume, and headhunters are tracking down kids straight out of the military (as long as they have a ticket). It's like the dot com bubble!
Waltz, nymph, for quick jigs vex Bud.
So, as one who has hired (and been hired) at a number of startups and medium size companies, I have a bit on insight into the dynamics of what salaries have been doing in the valley since 1996 (when I started at Netscape). I'm not so sure how the specific analysis applies elsewhere, but the general advice applies.
:-)
Basically things got out of control between 98 and 2001 as venture capital flowed into companies that were required to grow quickly by the venture capital. All of the good talent was hired quickly, and then some of the average talent was hired. All that was left was the basic low-no skill talent.
So, there was a situation in which it became difficult to find low-average talent, and our standard economic models tell us that when demand goes up and supply stays relatively stable (it takes a little bit of time to supply new IT/Developers) that the price per unit will go up.
And that's what happened. The market tried to correct, everybody came flooding into the valley (as evidenced by Traffic Jams, zero rental inventory and huge monthly rentals) and, in order to have any chance of holding onto employees, companies started increasing salaries.
Good employees had great salaries and average employees had salaries that they would never normally be able to earn as companies scrambled to bring on staff. Salary inversions happened all of the time as an employee who started at $50K/year doing desktop support was making $20K/year less than a guy who started a year later. Most companies leveled these off, bringing up the $50K/year employee to $70K which created even more pricing pressure on employees.....
And then the Bust in 2001 when Venture capital dried up, the stock market basically collapsed. Public companies could no longer do secondaries to raise capital and Private companies, well, they grew very, very slowly if at all.
Companies laid off employees by the thousands and people fled the valley. (As evidenced by vast rental inventories, much lower traffic on 880 and 101 and a 30-40% drop in the cost of rental housing). Salaries in some cases dropped (HP/Microsoft dropped by approx 10% in the valley) and in almost every case froze for several years for existing employees.
For new employees, it was (and still is) a totally different situation - Basically for every IT job there are about 100-200 applicants. Only the good ones get hired and their salaries are at a competitive level. A solid IT Desktop Support employee at a mid-level company can expect to make 96-97 salaries in the valley ($50K-$60K). Sysadmins with 8-10 years experience are making $70-$90K. Everything has cooled off and the employer is in the drivers seat again.
The good news is that Great Engineers (IT/Software Developers) are _always_ impossible to find in the valley, good/bad/otherwise. You basically have to steal them from another company in order to hire them as they don't typically come directly out of school. Their salaries haven't dropped at all (as their companies held onto them - Great employees are always the last to be laid off) at their current salary, or they made a lateral move (equal salary) to a new company if their previous company went out of business.
What this means for you - If you love the business ignore the salary - it means nothing in the first 3-4 years of your career. Absolutely nothing. Work for free if you have to. Focus only on three things:
o The Quality of the Job - What will you be doing, will you have the resources to do it, will you be given lots of authority and opportunity to do new things.
o The Quality of the Company. Does it treat it employees ethically, Is it well financed (!!!), does it have great management, do you have highly skilled coworkers who will cross train you/develop you.
o The Quality of the Opportunity - Is this company in a hot space, are they developing a great product, are they first movers in a cool new technology that will become a standard.
Everything else will take care of itself if you are passionate, skilled and focussed. Don't worry about negotiating/looking for a great wage/etc... That will take care of itself. I promise you.
Even if you do make less than a waiter for the first 18 months or so.
- Any Day above Ground is a good Day (Michael Rich, 1997)
Stock options...
Yahoo's Neighborhood Profiles section, searchable by zip code, has lots of nice data if you're pricing a job.
So what you're saying is that women are like evil hiring managers?
Grrr.
Without the Amazon-referer whoring: