[hacknut13]

But that's their point. When you have people with no jobs, that counts for the unemployment. But even I know how difficult it is to find people to hire for our company as I do HR for a technology firm. There is a high demand, just shortage of people to fill the positions.

[maxxxxx]

I see an increasing unwillingness of companies to train people who don't have EXACTLY the right skillset. This used be different in the 90s.

[arethuza]

Which, as far as I can see, has led to a vicious circle where developers will often refuse/bitch/complain about working on something that doesn't increase their immediate employability prospects. Not to mention CVs that quite often have a half a page or so of solid acronyms to increase the chances of being found by simplistic recruiting company search engines.

[pagekalisedown]

I agree. I think the logic is: "if we train them, they'll go find better paying jobs, and besides, as soon as this project is done, everyone will be laid off anyway." So everyone only wants to hire exact fit.

[neworbit]

My experience differs - I think it was in fact the rule of thumb in the 90s... until the dotcom gold rush got sufficiently out of hand that hiring people and training them became the only reasonable solution.

[simcop2387]

This can also be a function of density of capable talent where you are. I know in my area it can take a while to get a technology position (took me 8 months) due to there being very intense competition. However I did receive more than one offer to an area that I could not afford to relocate to due to other issues (mostly taxes). It seems like there are some great disparities in where the talent is and where the jobs are. The solution would seem to be for someone (people or the company) to move or to find a way for people to be able to work from a larger area around the business.