Live data from Hacker News

Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

news.ycombinator.com

1–10 of 105 posts

Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#1
If you're a CTO for a growing startup, this might be a familiar challenge for you.

On top of building the product, finding product engineers is becoming one of the hardest things for a CTO to do in 2019, especially in tech hubs like NY and London due to higher demand and competition.

This problem is no longer exclusive to the Bay Area. Hiring is time-consuming and expensive, and many startups feel that they can’t compete with some of the top salaries and perks offered by deep-pocketed alternatives.

It makes sense to rely on your network to hire the initial few developers, but this approach is not sustainable in the long run.

Job boards are getting crowded. Recruiters are generally worse.

I've read a lot of stories about using recruitment platforms. Few are great, but many are unpleasant. The flaw with many recruitment companies is they don't reliably deliver enough good candidates to build trust.

Asking for profile A and getting profile B is a common frustration. For startups, this tends to be a deal-breaker because hiring the wrong candidate has a significant cost and impact on backlog and team.

Is it that most recruiters or on-demand marketplaces aren't highly technical? Is it that they also suffer from talent shortage?

Remote work has been getting a lot of love in recent years to bypass the talent war. Although it has come a long way, it's still hard to pull off, especially for companies that are trying to do both local and remote but are not remote-first (think infrastructure and payroll primarily).

With that being said. How do startups in hubs currently find great engineers quicker? What's an approach that you have been investing in recently to hire product hackers?

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#2
As a developer who has recently been through the hiring process, I think the problem is not a shortage of talent, but rather that companies are awful at hiring. Here are a few of the main issues:

1. Don't limit your potential talent pool to the miserable and the unemployed. In theory, any developer who is currently employed might be interested in leaving their job to work for you. Perhaps you will offer them more money, or perhaps a better quality of (work) life. However, most developers won't bother to talk to you if they already have a job. Why is that? Simple, if they do talk to you, you're going to offer them a homework assignment. You're going to tell them that it shouldn't take more than an hour, but it will actually take two full days to do right. Giving someone a homework assignment isn't a way to woo them away from their current job. So you are left with a candidate pool that consists mostly of people who are desperate enough that they have to agree to jump through your hoops (i.e. unemployed, miserable in their current job, etc.)

2. Don't discard capable people. The average interview begins with a remote code challenge whereby the candidate, who is probably nervous, has to pair program a completely contrived problem with a complete stranger watching them over a webcam. There are tons of developers who are good at coding solutions to real world problems in real world situations but simply don't perform well in this type of situation. This type of scenario is not really assessing a candidate's skills. It's assessing their familiarity with specific contrived interview problems and their ability to perform under duress.

Of course, the points you raised are fair as well. Recruiters are not technical people, they are sales people. You will have to find a good recruiter. They are out there, you just have to find the right ones. But my point is, once you find the good recruiter(s) don't waste the human capital they can being to you by having a terrible interview process. Here is my advice. Once your recruiter has a handful of resumes you like, carve out half a days worth of 30-minute sessions to meet with them at the recruiter's office. Ask them about projects they've worked on. You'll find out much more about what they know and what they're like to work with than you would with the typical remote code challenge. One you narrow the pool down a bit bring them in for on-sites.

Best of luck!

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#4
>Asking for profile A and getting profile B is a common frustration. For startups, this tends to be a deal-breaker because hiring the wrong candidate has a significant cost and impact on backlog and team.

This sticks out: the hiring process is really bad at making this judgement effectively. We face this problem at my company, most of our best and worst team members have been surprises.

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#5
> Job boards are getting crowded. Recruiters are generally worse.

It seems that most (young) recruiters these days rely primarily on Linkedin as a sourcing tool. But that's not where the best talent is found.

The Hack to finding talent is to truly learn the recruiting process. That is to say, can you identify, assess, and ATTRACT decent people on your own?

Start by asking: Who would know know my ideal candidate?

ON this subject, Lou Adler is masterful > https://youtu.be/9KLR6rteoOU

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#6
Please write to us (i'am developer with more than 10 years exp): support@fastogt.com we will find you talents in Belarus, our developers can relocate, we have topnotch developers , here website: https://fastogt.com , without Recruiters, only direct contacts with developers.

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#7
post #4

>Asking for profile A and getting profile B is a common frustration. For startups, this tends to be a deal-breaker because hiring the wrong candidate has a significant cost and impact on backlog and team. This sticks out: the hiring process is really bad at making this judgement effectively. We face this problem at my company, most of our best and worst team members have been surprises.

That is very relatable, and results primarily from failing to identify false positives and false negatives in the hiring process.

An interview can result in a bad engineer being hired and later fired (a false positive). And an interview can disqualify someone who could have done that job well (a false negatives).

In order to keep the false positive rate low in the face of this noise, companies have to bias decision ever farther toward rejection. The result is a process that misses good engineers, still often preferences credentials over real skill, and often feels capricious and frustrating to the people involved. If everyone at your company had to re-interview for their current jobs, what percentage would pass? This is a scary question. The answer is almost certainly well under 100%. Candidates are harmed when they are rejected by companies they could have done great work for, and companies are harmed when they can't find the talent they need.

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#8
> This problem is no longer exclusive to the Bay Area.

When people question why so many companies start or stay in the Bay Area, "density of talent" inevitably comes up as one of the reasons. I can't reconcile that assertion with this one here.

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#9

Curious what your definition of an A versus B profile is?

I don't have a particular example in mind, but a lot of recruiters or even companies are still biased by credentials and resume buzzwords and don't have a proper vetting process to filter through the noise.

Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only

#10
This problem is no longer exclusive to the Bay Area. Hiring is time-consuming and expensive, and many startups feel that they can’t compete with some of the top salaries and perks offered by deep-pocketed alternatives.

Offer to teach the developer something.

"Java developers - want to learn Node and React?"

"Rails developers - want to learn Elixir?"

Get one senior person on staff who really knows the stack well and require that they pair program every day with a different member of the team.

Good developers are grateful for the opportunity to level up their skills, contribute, and still make a living.

Andres Camacho in SF has been VP of Engineering and CTO at several startups and is king of this strategy.

Post reply on HN