What does “there's a shortage of talent” mean?
I've heard from various reliable sources that there's "a shortage of talent" in the tech industry.
On the other hand, I read things like http://unemployable.pen.io/ about people struggling to find jobs. Additionally, I recently graduated from one of the top coding bootcamps, and while I did find a job, I got non-responses or rejections from pretty much everywhere I applied. And this is the story I hear from everyone I talk to at the bootcamp. We're told that it's a "numbers game".
So what is meant by "there's a shortage of talent"? In the context of that claim, what is threshold you have to surpass to be considered "talent"?
29 comments
[ 2.6 ms ] story [ 63.9 ms ] threadBut a bigger question than that is what market are you talking about? Are you talking about the valley? Boston? Have you considered that IT shortage is not a local problem, and a broader search could turn up unexpected opportunity?
http://www.nybooks.com/articles/archives/2015/jul/09/frenzy-...
My take, as an older, very experienced software engineer (with 25+ years of professional experience): it's basically bullshit. Big employers just don't want to pay for American citizens, especially ones who want to be compensated appropriately for their degree of skill and experience, because they have a track record of getting stuff done. These employers want H1-B warm bodies to fill seats at half my salary. These employers can go !@#$% themselves.
I am currently hiring and as part of the interview process, I ask a very straightforward question. I expect it to take on the order of 5 minutes and 7 lines of code. It is programming 101. Out of the 10 or so people I've interviewed, exactly none of them has gotten past this question. Most of them take 45 minutes to work on it and few of them get it to work even then. These are people who have contracted at big name places, with 10+ years of experience, with CS degrees, H1-B and non-H1-B.
So if I am going to hire someone who is unable to write a simple algorithm, I would rather do it at offshore prices. And sadly, that is something I am seriously considering doing.
I have written hundreds of thousands of lines of shipping code, and I've faced this kind of code-for-an-interview process repeatedly. The last time I had to do it, I found that I actually choked on a simple string reverse problem.
It was a really basic algorithm; there was absolutely no difficulty with my understanding of how the algorithm worked, or how to code it. I just choked. I was talking to three people on Skype with a shared whiteboard, and I had to give up. It was very frustrating. This had more to do with the fact that I had been out of work for several months and was facing a huge amount of stress about things like paying the mortgage than it did with my actual abilities on the job.
Forgive my skepticism, but I have been battle-hardened by some pretty bad horror stories.
I work at a Big 4, we see a lot of fresh graduates coming in every weeks or so.
To give you an idea of how bad it can be: a group of technical recruiters took the decision to "tweak" one of the interview questions we are asking during on-sites. They thought the change was benign when in fact it made the problem NP-hard, which is you know... pretty "tough" to solve under 45 minutes (or without a lab, a research team and 20 years). Of course, all of them were baffled by the fact that none of the candidates were performing well on this "trivial" question.
It took us three engineers, and two interviewees to make them acknowledge, and understand their mistake.
A big waste of time for everyone.
If you're trying to get hired, then maybe when you write a blog post on the fact, you also include a link to your resume. Or at least your name. Because otherwise, I'm sitting here thinking to myself "welp, no idea who this person is"
This person acknowledges that for more than a decade, she/he coasted in an office job. I tend to hire for strong initiative and drive, and I'd worry about this person. And that still wouldn't stop me from talking to them IF THEY MADE IT EASY FOR ME TO FIND THEM.
That said, the hiring process is completely broken. I know barely literate programmers making bank, while exceptional programmers are just scraping by.
This causes software projects to be both extremely expensive, hard to estimate and with terrible success rates.
Because all of that, finding software developers that can regularly deliver business value is extremely difficult and it is usually priced too high for most businesses.
Personally, I don't view this as a hiring problem, I view this as an oddity of the times we live in. Give it another 25 or 30 years and maybe we will actually know something about how software projects should work.
1. Truly there are not enough trained people for the jobs available, but I don't necessarily think that is our core problem in the US based market right now.
2. There is a shortage of new graduates to fill the entry level jobs available to do the grunt work on projects, and paying a senior engineer 6 figures to write programs or utilities slightly harder than Hello World is a bad investment (obviously a bit of an exaggeration but you get the idea).
3. Employers are not willing to pay the wage necessary to hire the people that are available in the market with the capability to do what the employer needs. e.g. they want to pay 70k/year for a 10 year senior engineer instead of a 6 figure salary. Supply and demand issue basically.
4. Employers are not willing to invest in an employee with 75-80% of the skill set to get them to the 100% they need. This can be because companies are so focused on quarterly numbers that they don't want a carrying and training cost or that they are fearful the employee will just leave once they are trained. I have heard both fairly recently.
Personally, I think all of these are true at different times and in different places, and I think there is some type of "shortage" now depending on the market you are in.
When demand for talent out paces the supply then wages should generally continue to rise until some equilibrium is established. Tech is on the rise side of this. A side affect is it has made it harder for small businesses to afford senior engineers. Many companies are also playing games primarily using foreign workers that essentially is manipulating supply which allows them to control wages.
There are of course other reasons an employer could be priced out of the market or unwilling to pay market wages of course. Maybe they just can't afford a senior engineer because their business isn't mature enough, it happens so they need to get creative. e.g. Use an outside firm or hire an individual who has less experience and hence has a lower cost.
I also had friends that would interview 10-15 times before getting an offer, and yet I typically would interview just a few times and have an offer. Not being cocky, I really think the only difference was that I was selling myself whereas they were just answering questions.
Selling yourself means answering more than the question on the table, answer it with examples to show proof you know it not just read about it. People have to feel like you did more then stayed at a Holiday Inn Express last night, they need to feel like you really know and can demonstrate it. So examples are good, past experience good and bad is relevant and helps. Asking questions during the interview that are detailed and show you have studied the team, individual or at least the company goes a long way. Also, asking questions during the interview instead of waiting until prompted can many times throws the interviewer off the question/answer method and turns it into a conversation instead.
Treat the interview like you would a date and that alone goes a lot to selling yourself. Turning the interview into a conversation where the interviewer comes out knowing you are competent but you can also communicate. Learning to do this takes a little practice, but it is just common social skills mixed with asking questions so you can open conversation paths. Think about any date you have witnessed or been on where it was awkward and there wasn't any give and take during the conversation, it never ends well, same with an interview.
You won't be able to do this with everyone, there are people that are so nervous themselves or such complete asses that they won't budge, so just hammer through those best you can and move on to the next interviewer or company.
edit: BTW humor goes a long way many times. Breaking tension by recognizing it and saying something can sometimes be the fastest way to get people to let their guard down.
-Unfrozen Caveman Businessman
If we set aside the possibility of greed on the part of employers, it may mean that they cannot afford to pay market rates i.e. their business model isn't compatible with paying the market rate for the labor they need.
Turns out that Corporate America is really bad at recruiting, thanks to poor technology investment decisions.
Here's an excellent assessment on the hiring situation by headhunter Nick Corcodilos > http://www.pbs.org/newshour/making-sense/ask-headhunter-recr...
1) train people, and 2) pay for talent
Businesses have pretty much tapped out the supply of devs who will spend thousands of hours of their own time on l&d for the love of the craft. So now if they want the expertise they have to pay.
If I am learning on my own time in order to increase my income I expect to get returns of at least 1cent/hour (and that's the extreme low end). So if I invest 10,000 hours I expect at least a $100/hr return.
How many companies complaining about a dev shortage are offering salaries of $300k+/year (intermediate dev salary + $100/hr compensation for all the l&d)?