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?"

5 of 1,525 comments (clear)

  1. Bad news by betelgeuse68 · · Score: 5, Interesting

    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.

  2. Re:Likewise by el-spectre · · Score: 5, Interesting

    This is true... I had several years of experience, including several applications written for my (work) department at school.

    Another thing: If you can get a skill that differentiates you, it helps a LOT. My grades sucked, but when I was competing with the "2 quarters of ASP" kids and I had 4 years CGI experience, plus some java, it made me a lot more marketable. Not so much the skills, but that I acquired 'em on my own. Being a geek is helpful.

    --
    "Faith: Belief without evidence in what is told by one who speaks without knowledge, of things without parallel." - A.B.
  3. Whats Open Source Experience worth? by CaptainPinko · · Score: 5, Interesting

    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.
  4. Re:I've been programming for 3 years by SnapShot · · Score: 5, Interesting

    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.
  5. Wage distribution has changed by SirShadowlord · · Score: 5, Interesting

    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)