As a candidate, I’ve had some interesting (and some stupid) questions come my way.
52 comments
If you have scathing feedback for someone you are interviewing, you should probably just shut up. Or at least deliver it in a different context where they aren't being held hostage and having their every reaction scrutinized. Sounds miserable, I seriously doubt they were actually "generally positive"
Would HR advise you to give this kind of feedback to someone you're terminating? Normally you say zero for this exact reason.
“Can’t complain!”
I learned it the hard way that even if someone asks for a feedback be very polite and simply convey that the HR has instructed you to route this via proper (HR/recruiter) channels. In fact in some cases, we were specifically asked to exactly say that and often our recruiters set these expectations with the candidates in advance (I've been informed of this in advance before some of my interviews). In one case a candidate kept mailing my team recruiter that the interviewers (a colleague and I) were very happy with the performance and why they were still not getting the offer.
If I want feedback (and this is only when the interview process was good irrespective of whether my performance, as per me, was good enough for that role or not), I ask for a a feedback via the recruiter and in most cases I don't get a response but that's fine. The last thing I want is feedback from someone who, let's just say, is not very ideal.
Another thing is, unless the candidate is someone who is giving an interview knowing they will get 11 offers out of 10 interviews they might be on the backfoot, a bit defensive, even stressed, or scared, and may not downright tell the interviewer that they are being an ass, or insensitive, etc.
It also doesn't cover the case of junior interviewers interviewing more experienced people either by accident or by design.
There are a lot of failure modes that could simply turn into useful conversations with this approach I think.
"This is utter shite"
"Thank you chef!" (Proceeds to burst into tears as they walk away).
I don't think it should be emulated.
Furthermore, as an interviewer, my job is to be a candidate. Why should this person choose my team/company to work at? It's a privilege that anyone show up to join, and I ought to be as prepared to give answers as they are.
That said, any "feedback" I would give would be arbitrary. I am not this person's mentor and I shouldn't—after only 40 minutes—assume I know enough to give them feedback. Saying that I have concerns about not getting enough information, and that somehow being their "feedback," is bad framing. Try:
Before moving on, I really want to make sure I get a full picture of your time at Acme working with the Foobar team. Would you say that you led project X? Who ultimately decided when it shipped and set deadlines? Was that part of your responsibilities?
I'd recommend avoiding giving anything framed as feedback altogether. End interviews by saying "We're all finished with this part of the interview. Thank you for taking the time to go through your work history with us. You should be hearing from [Hiring Person] about the next steps."I know TFA mentioned similar things about also being a candidate and that the "feedback" is to spur discussion, but the framing of giving "highly opinionated" thoughts about someone's capabilities as a way to ask questions is unnecessarily adversarial is an already power-imbalanced situation. I think it's better to try to tilt the power imbalance in the other direction—giving the candidate a feeling that you, the interviewer, are also auditioning for them. Doing that shows humility and, in my experience, gives a better opportunity to get to honest answers about being a good fit for each other.
Oof, what the hell? I'm not a big fan of people who want to offer feedback but don't genuinely ask first, and accept that the person might say "no". (And then honor that!)
Some of the feedback the author described wasn't really feedback, it was more like they didn't fully ask the questions they wanted to and should have during the interview, got the wrong impression, and then thought that offering feedback was the way to get that fixed up. No, the right thing to do is immediately ask a direct question about what you're looking for, at the point in the interview when you aren't getting it.
There is no fixing an interviewer who doesn't understand the answers really. You need a third party for that.
Have had weird interviews with people who don't introduce themselves and assume that I definitely am interested in whatever the job is even though I know nothing and proceed to ask questions that amount to "how does palantir work" and get irritated when the answer isn't "we used database X".
Fundamentally one needs a meta approach that handles these cases too without knowing who is interviewing who. Could an interviewee give feedback like this without sounding arrogant?
This kind of thing is weird to call out. Your perception of a candidate’s emotions isn’t relevant. People are wired differently. Some people can bullshit with no nervousness at all. Some people can be highly skilled and not able to practice this away. It’s a matter of wiring.
Calling out actions and behaviors and words, observable reality, is fine. Emotions, no.
Read the full thread on Hacker News →
Related stories
- Hacker News · 20 points · 4 days ago
- DEV Community · 9 points · 5 days ago
- Show HN: Every Credit Cardevery-credit-card.numberplanet.comHacker News · 1 points · 8 days ago
- Hacker News · 5 points · 7 days ago
- RippleNav – A web instrument provides real-time visual feedback on thought focusaccess.ripplenav.orgHacker News · 1 points · 9 days ago
- Hacker News · 25 points · 9 days ago