back

by brandonb·13y ago·view on hn ↗
Hmm, did you actually encounter those bad behaviors, or are these hypothetical? I gave feedback to nearly everyone we interviewed onsite, and only dealt with one person who became defensive. I thought it'd be a problem but most people are actually very decent.

For all of your examples, I think you can communicate the feedback in a specific, helpful, and gracious way. For example, for the candidate that you're worried would futz around with technology for technology's sake, why not say something like:

"Hi X,

Thanks for interviewing with us yesterday! Everybody on the team enjoyed meeting you.

Unfortunately, I don't have great news for you: after a lot of discussion, we decided we can't make an offer.

We thought you seemed really smart, and you did great on all of our algorithms and system design questions. What worried us is that, during the pair programming exercise, you spent a lot of time configuring your custom-built editor and trying to use a combination of the D and Brainfuck programming languages running within an Amiga emulator, when C compiled to x86 would have been a more practical choice. Since we're an early-stage startup with only six engineers and limited funding, everything we do has to directly relate to making our customers happy, and so we're especially sensitive about pragmatism at this stage. We know it's entirely possible we're making a mistake, but given our company's small size, we just have to be very cautious, even paranoid, with every single hire.

Thanks again for taking the time to talk with us. We really appreciate it. And sorry again that things didn't work out this time. Best of luck with your other interviews, and please let me know if there's anything I can ever do to help!"

(I'm making up details, but you get the point. I've sent lots of feedback of this type and rarely had a problem.)

1 comments
This is a nice and polite email and I can't see anyone getting offended by it. The problem however is if they respond disagreeing with your conclusion.

Say, in your example above, the person responds with "I used D and Brainfuck in my custom-built editor to show that I am interested in new technologies and pick them up really quickly, and that I customize my workflow for maximum productivity. Aren't these great attributes in an early engineer? I had no idea you guys just wanted C to x86 - you should've asked!"

And now you're stuck. Do you respond to this as well, and if so, how long would you keep the chain going? What if the person was actually correct? Would you now go back to your team and reverse the decision?

I was worried about getting embroiled in arguments, but in practice it virtually never happened. Most people simply thanked us for providing feedback at all; I only dealt with one case where somebody tried to argue against the decision.