3 ms·

Yeah and to be clear I’m the most introverted of all folks, and it was literally torture forcing myself to do this but I wanted to actually get my effort done a

Yeah and to be clear I’m the most introverted of all folks, and it was literally torture forcing myself to do this but I wanted to actually get my effort done and I could see from my peer teams the sourcing and recruiting functions were not functional. I don’t think they actually do nothing though. They’re just highly ineffectual. Not only do they target candidates wrong as you mention they’re known to be five steps removed from any decision. The power of being the hiring manager and directly involved in the project is hard to measure but it’s significant. The other issue is recruiters don’t actually know the tech landscape in enough detail. They know the rough shape of major employers, but details like “UIUC is in central Illinois and there aren’t many employees in the area and those that are there aren’t that desirable so recruiting phd students out of the program isn’t that hard” or “national labs under Trump are a terrible place to work so recruit folks working on climate change super computing projects” aren’t practically tractable. They’re also, to your point, unaware of the adjacencies of technologies - while they know what stack you’re hiring for, they can’t know X is similar to Y so X is sufficient. It’s a hard job and entirely thankless, and I always feel tremendous empathy and sympathy for folks in the recruiter role. But that doesn’t help the fact they’re almost entirely useless in that role.

logicalmonster 4y ago
> It’s a hard job and entirely thankless, and I always feel tremendous empathy and sympathy for folks in the recruiter role. Every job has good and bad things about it, and I'd acknowledge that there's some really bad aspects to recruiting such as the following: > Having to give people bad news frequently is emotionally draining to them sometimes. > I'm sure it gets quite monotonous to round up a bunch of candidates for any role. You probably have to call a lot of people and have the same conversations over and over and over again, day in and out. > Being among the first in line for layoffs in bad times sucks. > I'm sure some client demands they get are unreasonable. There are companies that want to immediately find somebody who takes 50% of the average developer salary who has the technical experience of an entire IT department in 1 person. That said, recruiters can get a pretty favorable overall path in life: for a small fraction of the mental effort of a developer, you can get a fairly large percentage of their salary without having any notable skills other than a few general skills such as being able to organize sending emails and maintaining appointments on a calendar.

logicalmonster 4y ago

> It’s a hard job and entirely thankless, and I always feel tremendous empathy and sympathy for folks in the recruiter role. Every job has good and bad things about it, and I'd acknowledge that there's some really bad aspects to recruiting such as the following: > Having to give people bad news frequently is emotionally draining to them sometimes. > I'm sure it gets quite monotonous to round up a bunch of candidates for any role. You probably have to call a lot of people and have the same conversations over and over and over again, day in and out. > Being among the first in line for layoffs in bad times sucks. > I'm sure some client demands they get are unreasonable. There are companies that want to immediately find somebody who takes 50% of the average developer salary who has the technical experience of an entire IT department in 1 person. That said, recruiters can get a pretty favorable overall path in life: for a small fraction of the mental effort of a developer, you can get a fairly large percentage of their salary without having any notable skills other than a few general skills such as being able to organize sending emails and maintaining appointments on a calendar.