2 ms·
God I couldn't imagine conducting 6+ hours of interviews for a candidate I knew failed it within the first 30 minutes. Ain't nobody got time for that.
by Clubber 3y ago
God I couldn't imagine conducting 6+ hours of interviews for a candidate I knew failed it within the first 30 minutes. Ain't nobody got time for that.
- lazide 3y agoI literally couldn’t let it happen. The thought was roughly as palatable as intentionally ‘groining’ a coworker on a guardrail or letting a kid walk into traffic. After getting chewed out, I never walked them out early though. I guess that is why FAANG told us to not talk between ourselves and put everything into the system for the HC independently - so we wouldn’t know what we were in for, and would give each individual interview a fresh shot without all the anticipated pain and suffering. Makes it easier when you can’t see the nut shot coming I guess? Makes sense, but yeah - terrible. To be fair though, out of hundreds of interviews I’ve done, that was top 5ish for bad. Most were much better.
- sokoloff 3y agoIn the late 90s, I worked at a place that would walk people out as soon as we'd reached a hard-no decision. As the first tech interviewer left the room, in the hallway, the second would ask some innocuous yes/no question. ("Hey, my car's at the shop; can you give me a ride over there later?") The answer to that question was whether or not to continue the interview slate [and was almost always "yeah, sure, no problem"]. If it was yes, go into the room and introduce yourself. If it was no, they'd walk off together to find the recruiter who would walk the candidate out. That place never stopped doing the practice, but other places I've worked (including the current) have decided against that pretty brutal candidate experience. (And, as you say, have also had a policy not to share any information about the candidate's performance until after submitting the write-up and recommendation from the interview.)