Earlier quoted context omitted.
Of course. I apologized for wasting their time and walked them out within 30 minutes. They had clearly flat out lied about their qualifications. I also got lectured by senior management for exposing them to liability since I didn’t ’go through the whole process’. And this was a middle aged white dude candidate, a small company, and about 20 years ago. The risk tolerance has only decreased since then.
>I also got lectured by senior management for exposing them to liability since I didn’t ’go through the whole process’. I work in an "at will" state. Our 3 people are usually on teams chatting about the interview going on and will decide to end it early and not waste everyone's time if it's not going well. We've never had anyone tell us they were concerned about that. What liability was senior management at your comp…
To paraphase "We want to give the candidate every chance to prove themselves, and cutting the interview short gives them a bad impression of the company (and it would make it easier to sue us for unfair discrimination)."
Since it was just a few (or in this case 1) interviews, and that makes it easier to claim that I cut it short because queue whatever protected class. Which, if someone was going to be that kind of jerk to a candidate, I guess doing it on the first interview WOULD be the one, eh? It would just be my word against theirs, instead of x interviewers vs theirs.
And I guess the riskiest type of candidate for that kind of crazy behavior WOULD be the person who felt okay blatantly lying on their resume about such a fundamental fact AND EVEN SHOWING UP FOR THE INTERVIEW, come to think about it.
We didn't get sued in this case though. I think the interviewee was just surprised someone was interviewing him who actually knew how to code.