Basically when you start a job there is a relatively long learning curve. The technology, business, and interpersonal relationships are all unique and they all take a rather long time to develop. Usually the beginning part of that learning curve hurts the most (ex. learning how not to break the build and speak with some competency about the code base) and the rest is called personal "growth" and is usually satisfying and can run for many years without plateauing. The problem is that once you get to this middle staged growth, you dont want to have to go back to beginning part that comes with getting a new job (although I do recognize some people are different).
Now on the flip side if we were assembly line workers building light bulbs, the moment you heard the light bulb shop across the street pays 20% more and desperately needs people you'd probably be running across the street in a flash. And the next day at the new place would probably be about the same with 20% more pay.
The fear within tech is that, without standardization of work places, you can end up realizing you stepped into a big pile of crap. Crazy managers, incompetence, long hours, shady investors, etc etc.
Its not my desire to suggest we should turn the industry into light bulb manufacturing but I think the non-standardization has probably lead to the strangeness in hiring.
Not so sure about that. A lot of talented engineers are already in a job. They might be receptive to looking at another job for a period of months or years, but never actually looking. So a lot of the skill in recruitment is reaching those engineers with opportunities that will entice them to consider a move. Yes, sometimes this happens via aggressive recruiters, but it can also happen via "softer" approaches like publicity, sposnsorship, advertising etc.
"But again and again, he points out that qualified engineers do exist, and they’re being shut out of companies for what amounts to a cultural stigma about what sociologists would call “the other.”"
This is the point.
Edit: I think is important say that the "there's a terrible programmer shortage" belief is a myth, in the sense that it is a dramatic story that impels people towards certain behaviors and to say that this myth is wrong, in the sense that it excludes many people, in order to add some kind of sanity to the hiring process.
Along that vein, almost no place is interested in paying for talent. I consistently get incredulous responses from recruiters when I tell them my rate. Many companies cap their reqs at $90/hr or $100/hr. This seems like a decent rate, but a major part of the problem is that the recruiting firm wants to take 30% of that hourly rate. If the maximum cap is 100, that means the contractor is getting (at most) $70/hr. Companies either need to up their rate, or cut out the middle man completely. The vast majority of recruiters I encounter today have a premium LinkedIn account and just spam everyone that matches keywords. Are you telling me a company couldn't have an intern do that kind of thing for a lot less than the recruiters are getting?
for me there was just too much friction in the process which is what we think our model can remove/reduce.
I'm a little torn. It's interesting that he describes finding engineers as like "detective work". My first instinct (as a developer) is that if someone is difficult to find, it's quite possible that they're not interested in being found. If they were looking for a job, they'd be visible. Does he consider it his role to 'educate' engineers about the possibilities available to them?
I've just been through the process of finding a new job. I expressly avoided using any recruiters, and am very happy with the result. Maybe engineers are hard to find because they're used to hiding from recruiters. I negatively judge startups that use recruitment agencies, but maybe I'm part of the problem.