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 r…
If good developers want to level up their skills, how do you keep the senior developer who you've turned into a tutor happy?
Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
21–30 of 105 posts
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#22Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#23Curious what your definition of an A versus B profile is?
Not OP, but during a recent hiring process we asked for backend engineers (e.g. java/golang/databases etc). Half of the CVs we received were for Angular/React developers. I'm unsure how this could happen with any sane vetting process.
I do believe the "technical" layer in a recruiter is the most important thing. Amarraja, how do you go about vetting your recruiter? Have you had any set of criteria to identify a solid talent acquisition partner?
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#24This 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 r…
If good developers want to level up their skills, how do you keep the senior developer who you've turned into a tutor happy?
At least in the above scenario, it was Andres doing the work of initially getting someone up to speed and then pairing the coworkers on an appropriate level feature/bug. He'd stop by and check in to see where they were stuck and would genuinely try and solve the problem.
So, it has to be someone who is a great coder for that stack and enjoys teaching.
If it's done right, other members of the team become good teachers as well, so the initial burden of teaching is lightened.
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#25Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#26> 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 t…
This reminds me of a recent post that rings pretty true: "When hiring senior engineers, you’re not buying, you’re selling"
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#27I think a lot of this is based on they myth of: A bad hire causes tons more damage than not hiring a good person.
I call BS. To me this is just weak management. It's actually not that difficult to fire someone. If you're in doubt, put an explicit probation period in the contract. I think being able to effectively fire is management 101 but looks like it's becoming a lost art. I'm not sure if this is because people are afraid of confrontation or they're just cargo culting the story they've heard about bad hires.
Easy in, easy out and you'll see your dev shortage problem start to solve itself.
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#28As 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 mon…
I got it! We will hire anyone who sounds good, and fire them within a month if it turns out they're not up to our standards. Then, we will ensure we never get anyone who isn't already employed and anyone just looking for a paycheck or three. If you heard that even 20% of people were fired within the first month, how likely would you be to take that job? Note: It's usually called contract to hire. And it just takes th…
I would prefer that 80% of people are fired in the first month.
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#29The salaries that are offered are a joke in London. The expenses are so huge there! Even if the salary is a bit higher than my current one, I would spend much more.
There are a lot of joke startups, some new cryptocurrency or blockchain startups... Nope, I'm not gonna join anything like that.
Also, I'm not a huge fan of big cities and London is too crowded (for me).
Allow remote and I'm sure you are gonna find someone.
Re: Ask HN: Finding tech talent is getting harder. It's not a Bay Area problem only
#30This 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 r…
If good developers want to level up their skills, how do you keep the senior developer who you've turned into a tutor happy?