4 ms·
Well, HR does have final say-so in terms of logistics. Like does the candidate require sponsorship to work in this country, do they have a criminal record, did
by tootie 13y ago
Well, HR does have final say-so in terms of logistics. Like does the candidate require sponsorship to work in this country, do they have a criminal record, did their reference say they were an asshole, are they asking for more money than we can afford. Even judging personality and communication skills is not outside their expertise. The lesson of this article is to not use personality tests.
- jerf 13y agoYou explained why they should have input, not why they should have final say.
- Tyrannosaurs 13y agoWe tend to say anyone involved in the process can veto and I'd extend that to HR if they'd shown themselves to add to the process. Work permit issues are entirely a reason to veto and they're better placed to spot that sort of thing that the dev team, similarly issues around references and the like. The issue here isn't with HR per se, it's with a bad HR department overreaching, but personally I'd be just as skeptical about a technologist pointing to poor performance on a technical test (with good face to face interview results) as I would about this.
- deleted 13y ago[deleted]
- 6d0debc071 13y ago> We tend to say anyone involved in the process can veto and I'd extend that to HR if they'd shown themselves to add to the process. IIRC there was a woman a few months back with Valve who couldn't get the staff she needed because of that sort of veto setup.
- Tyrannosaurs 13y agoThat may be the case. It works for us because the people involved all understand the log jam it can cause if people don't behave properly but I can see in another company (or even division) it might not work. You would only need one or two people deciding they wanted to throw their weight around to wreck it. Maybe I'm lucky but I've worked with some good HR people who understood where they could add value and where they should step back. To me this really feels like a good people / bad people thing rather than an HR people / technical people thing.
- rayiner 13y agoIf you're trying to separate "face to face" performance and put that in the domain of HR, and "technical test" performance and put that in the domain of the technologists, then you're going to have a bad time. That prospective hire who did great on the face to face isn't going to spend part of every work day chatting with HR... Between your technical people and your technical management, there should be enough people skills to function coherently and effectively as a team. As such, those people together should have enough people skills to figure out whether a prospective candidate has the people skills to function effectively in the team. If those people see people skills as exclusively the domain of HR, well then you made prior mistakes in hiring that cannot be remedied with further mistakes. This is exactly the sort of mission confusion that results in HR departments overreaching. If HR sees itself as "the people people" and its role as evaluating candidates for "people skills" and engineering's role as evaluating candidates for "technical skills" that's an unworkable division of labor and will invite improper encroachment from HR into the hiring process.
- Tyrannosaurs 13y agoThat's not what I said. What I'm saying is that putting too much faith in tests isn't just something HR do (I've seen people put far too much faith in technical tests), and that HR having a veto isn't per se a bad thing so long as they exercise it sensibly based on things within their expertise.
- RogerL 13y agowe tend to say okay, you say that, but any empirical evidence that this leads to better decisions? Especially when, as in this article, the only one saying no is the one unable to judge the person's ability to actually do the job?
- rayiner 13y agoWell there are obviously certain areas where they should have final say (e.g. this candidate is great, but here illegally and not authorized to work in this country). They should not have final say over a candidate based on personality or communications skills. They should be a source of input (i.e. this guy is an asshole, because he was very rude to the guy who helped him scheduled his callback interview, or perhaps more importantly to inject some company-wide context into what can turn into a group-specific analysis) but it's the technical people who know what kind of communication goes on in a technical team, and thus it's the technical people who should evaluate a candidate on that characteristic. Yes, this requires trusting your technical people and investing them with a greater responsibility to understand the dynamics of their work group. That's a good thing.
- cllns 13y agoTo be fair, you did say: > There is absolutely zero reason why HR/recruiting people should have final say on a candidate. None. Now you're saying: > Well there are obviously certain areas where they should have final say
- rayiner 13y agoFair, if pedantic, criticism.
- hvs 13y agoIf you are hyperbolic, then you can expect pedantry in return.
- nitrogen 13y agoIf every hyperbole was met with pedantry then nobody would ever go fishing again, and HN would turn into the worst newsgroup you can remember from the 90s.
- moocowduckquack 13y ago
- wpietri 13y agoWhen groups designed to serve become self-serving control apparatuses, I think a company is deeply fucked. Probably irrevocably so, although I'd love to learn otherwise. It means people have forgotten the mission, and once that happens I think it's slow death by turf battle. You also see this happen with IT, Ops, and software development organizations, not just HR. E.g., feature X is the company's highest business priority, but the DBAs don't like it and they control all schema changes, so they just say no. In my view, HR's job is to help hiring managers find the people they need, and then to support those people when they're there. If hiring managers need help with making hiring decisions, then by all means offer them help. And if HR,or anybody, spots something that concerns them, they should speak up. But I think giving HR a veto is a clear mistake. So no, I'd say that tests just make this an obvious problem, rather than a subtle one.