The things the writer complains about certainly happen, but thankfully haven't been the majority of my experiences. I don't have as much emotion invested into the hiring process, but I have been on both ends of it at various times in my career, and I can say both that (some) companies have ridiculous expectations and hiring gauntlets, and that it's hard to find decent developers. I think any hiring manager can tell you horror stories about devs with "ten years of experience" who can't write a for loop.
I take company complaints about worker shortages not to be literal, but to be part of public relations, marketing, and appealing to politicians. Annoying? Sure. But also part of the game. I understand the article is mostly about berating companies for being dishonest about hiring, but I don't think an appropriate counter is to be dishonest about being hired. The rest of my response focuses mainly on the perspective of a career dev looking for work.
Your mileage may vary with different tech scenes, but my take on these experiences:
"Problem no. 1: Companies rely too heavily on automated filtering." While true, if this is your first and major complaint, you rely too heavily on job submission pages. Get a decent recruiter, reply to some linkedin recruiters, and be open to possibilities. You should expect applying to a job board without an internal champion recommending you to have similar odds to cold calling someone to sell them insurance.
"Problem no. 2: The credentialism barrier." I can't speak to the author's experience with this, only to my own. No more than 20% of the time I've interviewed has not knowing a specific programming language or technology been any sort of problem in the interview or even mentioned. I have noticed this happens somewhat more often with Java shops, who expect you to be very experienced specifically with Java, but even there most of them are pretty understanding that you may have some catching up to do (again, in my experience).
"Problem no. 3: Education is inaccessible." This seems a fair complaint, though not specific to technology.
"Problem no. 4: Low Pay and Bad benefits." This is a surprising one to read in technology. Maybe I've just been lucky and in a good area, but tech jobs are pretty well paid, decent benefits, good vacation (not at AWS though, seriously guys, do better), and with a pretty low investment in learning some people skills and negotiating tactics you can drastically increase your earning power. Read "Getting to Yes: Negotiating Agreement Without Giving In." It's short and phenomenally helpful when negotiating salary and benefits.
I empathize with the author's annoyance about listening to what amounts to a PR campaign from tech employers, but again, I think the counter to that is pointing out that it's a lot of hot air, not complaining about how hard it is from a dev's perspective seeking employment. I am open to being wrong on this, however, and welcome dissenting opinions telling me how wrong I am!
I take company complaints about worker shortages not to be literal, but to be part of public relations, marketing, and appealing to politicians. Annoying? Sure. But also part of the game. I understand the article is mostly about berating companies for being dishonest about hiring, but I don't think an appropriate counter is to be dishonest about being hired. The rest of my response focuses mainly on the perspective of a career dev looking for work.
Your mileage may vary with different tech scenes, but my take on these experiences:
"Problem no. 1: Companies rely too heavily on automated filtering." While true, if this is your first and major complaint, you rely too heavily on job submission pages. Get a decent recruiter, reply to some linkedin recruiters, and be open to possibilities. You should expect applying to a job board without an internal champion recommending you to have similar odds to cold calling someone to sell them insurance.
"Problem no. 2: The credentialism barrier." I can't speak to the author's experience with this, only to my own. No more than 20% of the time I've interviewed has not knowing a specific programming language or technology been any sort of problem in the interview or even mentioned. I have noticed this happens somewhat more often with Java shops, who expect you to be very experienced specifically with Java, but even there most of them are pretty understanding that you may have some catching up to do (again, in my experience).
"Problem no. 3: Education is inaccessible." This seems a fair complaint, though not specific to technology.
"Problem no. 4: Low Pay and Bad benefits." This is a surprising one to read in technology. Maybe I've just been lucky and in a good area, but tech jobs are pretty well paid, decent benefits, good vacation (not at AWS though, seriously guys, do better), and with a pretty low investment in learning some people skills and negotiating tactics you can drastically increase your earning power. Read "Getting to Yes: Negotiating Agreement Without Giving In." It's short and phenomenally helpful when negotiating salary and benefits.
I empathize with the author's annoyance about listening to what amounts to a PR campaign from tech employers, but again, I think the counter to that is pointing out that it's a lot of hot air, not complaining about how hard it is from a dev's perspective seeking employment. I am open to being wrong on this, however, and welcome dissenting opinions telling me how wrong I am!