I once posted a job on monster.com and we rejected probably 50 resumes for each one we interviewed. We were looking in the wrong place. At a different job, we had a terrible time trying to find somebody with 10+ years of embedded systems experience in a town that didn't really have that kind of industry. In retrospect, we probably could have found a less experienced person that we could train. We were looking for the wrong person.
I am unlikely to hire a candidate who would need training because I simply do not have the time to train them. I need someone who gets things done, can self-train if needed, and who already has the minimum required experience so they have minimum impact on team velocity. Moreover I live in an "at will" employment state, so any money/time I spend training a person can just walk out the door at any moment (something I have seen happen just because a person was offered even more money elsewhere).
People should come first. Everyone has to start from the beginning at some point.
1 in 300? are you serious? i have a real hard time believing that. are you literally calling every resume you get? do you know how to filter a pile of resumes?
we are a tiny startup offering normal wages and we are at a 1:5 ratio between offers and phone screens. we might have to interview 10 people to get someone on board.
then again, we don't expect our mid-level ruby and python web developers to answer graduate-level algorithms questions, which seems to be kind of an insane expectation these days among employers who take themselves a little too seriously.
I try to convince people to become software engineers all the time, and I tell them all about the salaries and benefits they can expect, and most of the time they just sigh and repeat that it's too hard.
Also, living in regions of the US where salaries for engineers exceed $100k per year also means incredibly high living expenses, so higher salaries would be necessary to entice people to move from out of the area.
As it is, I know people making HALF of what would be entry-level for software engineers, but elsewhere in California, and they have a MUCH better standard of living than entry level engineers. As in, they own a 3 bedroom house with a big yard, a couple of cars that easily fit into a 2-car garage or can be left in their spacious outdoor parking space, OR on the street where there is no-time-limit parking.
This standard of living could easily run $2M in the bay area (the mortgage payment alone would be more than my friend's salary, before taxes), but can be had for about 1/10th of that elsewhere.
My point is simply if there was a shortage rates would go up and those in senior levels would stay in their field.
Also, go talk to those doing enterprise software sales, banking, mba degrees, etc. They will all be making more than software developers. So, either there is a shortage or developers are really bad at negotiating their salaries. (I actually suspect both is true, but the shortage is really because folks are looking for perfect match candidates)
Money is definitely a factor.
I suspect the process of filling the candidate pool was probably broken at your previous company too.
At a previous company I interviewed hundreds for engineering positions (Ruby & Rails or JS/Backbone.) Our average was 1 offer extended for every 300 phone screens. The problem wasn't that we extended 50 offers and got rejected; money was not a part of the equation. We simply couldn't find the quality we were looking for.
Specifically, coding schools have capitalized on the gluttony of open positions, but don't actually go towards solving the problem. There isn't a shortage of bodies, there is a shortage of experienced developers.