Live data from Hacker News

Why is recruiting developers so difficult?

polyfill.work

11–20 of 233 posts

Re: Why is recruiting developers so difficult?

#11
post #9

Number one reason: You're not offering me enough good reasons to leave my current job. I don't think HR and software recruiting has really caught up to the reality that many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. Further we usually find equilibrium with our roles wherever we are even if we have gripes with how things are because most devs are pragmatic p…

By my mid-30s and having started programming at 9 and professionally at 14, 200k is chump change for a salary. That's what they really haven't caught up to.

Re: Why is recruiting developers so difficult?

#13
post #7
post #2

Because you make it a complete nightmare. I'd rather wait in line at the DMV all day than go through a typical 6hr tech interview. Hire me based on my resume and a phone call, give me a task, and if it's good enough keep me. Problem solved.

I agree in principle, but not in experience. I've interviewed a few people lately, Senior Eng somehow, who have impressive resumes. I ask basic coding tasks just to make sure they actually know the language claimed - just something like converting numbers to strings, and you'd be amazed how many people had no idea where to start.

Doesnt sound like you disagree. That falls under the "give me a task" part.

Re: Why is recruiting developers so difficult?

#14
Bias.

I interviewed at over 25 places through the past year. Here are my observations:

More than half the time the employer knew the work that needed to be performed in the near immediate but had absolutely no idea what they wanted in a developer.

Nobody can define senior. At some places they were expecting a senior developer who could do anything. At other places it was a trend chaser who plays with dozens of tools. At other places it was a framework user placing text on a screen.

Algorithms are where interviewers go when they don’t really want to talk to people. This is a danger zone because the candidate can fail any number of reason, most especially code style and vanity. Worse, many of these algorithms are completely outside of any real world concern better solved with a well formed data structure.

Unfounded assumptions are the standard. Most people writing software professionally have never done anything else professionally, which is a tragic silo. When you’re a hammer everything is a nail tunnel vision mentality is the expectation. In this case the goal, if want to be hired, is to fall into the middle of the bell curve. Don’t be awesome.

Re: Why is recruiting developers so difficult?

#15
post #6

1) Because recruiters don't understand the subject material. 2) Because companies are hilariously risk adverse. I have over a decade experience in a consultancy environments (faster paced and more rigorous than a lot of other jobs, sorry not sorry). My work was independently driven and I provided input to the projects I was on at the highest levels. I've set IT and SWE policy for and introduced leading products at mo…

When was the last time you interviewed, and how do you feel about remote work?

I interviewed a lot the last couple years, from the Midwest, and had more remote opportunities than I could handle. I'm not interviewing with FAANG though; almost entirely private companies, seed to E.

Re: Why is recruiting developers so difficult?

#16
post #6

1) Because recruiters don't understand the subject material. 2) Because companies are hilariously risk adverse. I have over a decade experience in a consultancy environments (faster paced and more rigorous than a lot of other jobs, sorry not sorry). My work was independently driven and I provided input to the projects I was on at the highest levels. I've set IT and SWE policy for and introduced leading products at mo…

Maybe this is cynical, but in my experience, companies are hyper-averse to expenditure, not to risk. They will thoroughly (though often ineffectively) analyze developers intended for medium- or high-salary brackets, but they are happy to also pay a third of the price for barely questioned offshore developers who are indeed very risky to whatever product they will be touching.

Re: Why is recruiting developers so difficult?

#17
post #11
post #9

Number one reason: You're not offering me enough good reasons to leave my current job. I don't think HR and software recruiting has really caught up to the reality that many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. Further we usually find equilibrium with our roles wherever we are even if we have gripes with how things are because most devs are pragmatic p…

By my mid-30s and having started programming at 9 and professionally at 14, 200k is chump change for a salary. That's what they really haven't caught up to.

This is only true for US salaries (and sometimes specifically within Bay Area/Seattle/New York markets)... pretty much everywhere else, salaries are a lot lower.

L7 salaries are 300k base and around 400k equity in the US, so hiring experienced/accomplished developers is intensely difficult for companies outside of the top tier with high margins or startups with potential exits.

Re: Why is recruiting developers so difficult?

#18
post #11
post #9

Number one reason: You're not offering me enough good reasons to leave my current job. I don't think HR and software recruiting has really caught up to the reality that many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. Further we usually find equilibrium with our roles wherever we are even if we have gripes with how things are because most devs are pragmatic p…

By my mid-30s and having started programming at 9 and professionally at 14, 200k is chump change for a salary. That's what they really haven't caught up to.

200k is not chump change for every other profession. Get off your high horse. You're not special because you know software.

Re: Why is recruiting developers so difficult?

#19
Tell the candidates what you want: I want someone who has 15 years of c++ experience transitioning into a go lang role. Rather than I want someone with 10 years of golang which will land you candidates with 2-5 years.

"which doesn’t necessarily get me any closer to hiring someone good"

Everyone wants to hire only the best developers. The more developers in the pool of candidates the more picky we become. Everyone has 2 years of Java in the candidate pool? We only want the best.. you need to have 3 years. If everyone had 5 years you need to have 7 years to be considered the best. Meanwhile any average developer in the candidate pool would work out fine.

Trying to find the perfect candidate vs the average candidate is the self imposed struggle employers give themselves. The need to hire the best gets harder the bigger the pool for all.

Re: Why is recruiting developers so difficult?

#20
post #9

Number one reason: You're not offering me enough good reasons to leave my current job. I don't think HR and software recruiting has really caught up to the reality that many developers by their mid-30's are sitting on a million+ in assets and good ones can rake in 200K+ easy. Further we usually find equilibrium with our roles wherever we are even if we have gripes with how things are because most devs are pragmatic p…

Don't write off a company just because they have an unlimited PTO policy. Check out the culture first, some actually respect it. Especially in smaller companies, it's sometimes just easier to judge people based on their output rather than the number of days their butt is behind a keyboard.
Post reply on HN