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.)
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?
Hi Bob,
It's Jim at CompanyX. I discussed the interview with the
team. It's difficult for me to say this and I don't know
how to say it properly, but we think you're pretty good but
doesn't quite clear the bar for us.
We'd like someone who has more experience in X, Y, Z, but
in our interview, we thought A, B, C. I know our interview
probably is no where near perfect and may not have
presented the entirety of your skills, but unfortunately
this is our interview process and we will have to abide by
it.
You're certainly welcome to try apply for jobs at our
company in the future.. XYZABC... Thanks for taking the
time to interview with us, and good luck!
'Good fit' tells nothing to the candidate what they can improve, and deters them from applying at your company in the future when they further develop their skills and attitude.I also feel that I am not in a position to give advice or feedback to someone I've barely known. Just because I didn't hire the guy does not mean that I was correct in not hiring him. At some level, we'll never know. So it's pretty hard to even have feedback that I can be 100% confident about.
"Thanks for letting me know; sorry to hear we won't be working together at this time.
"If you have any suggestions to give for additions to my skills and portfolio that might make for a more competitive application at some point in the future, I'd love to hear them!"
Would you take the time to give any hints then?
I occasionally send a note to this effect when I miss out on a job that I wanted enough I'd love to be able to reapply later for a similar position.
But I've received a reply precisely once.
If this wasn't a concern, I would gladly take the time out of my day to write a nice note like this. Even if they're not hired, many technical people will tell their friends about their good experience with you and help improve your reputation in the tech community.
Hi Bob, It's Jim at CompanyX. Hiring is complicated and needs many people to agree on a particular candidate. Often, we don't. Unfortunately, we couldn't all come to agree on hiring you. It's no reflection on you as a candidate and maybe only a reflection on our skills as interviewers and recruiters. We thank you for your time and wish you all the best. Certainly feel free to apply again, and many of us here, including me, may have been bad hires who will be fired soon.
Cheers, Jim
I also think the generic approach is best; in my experience also, giving specifics can open up a can of worms.
Having been on the other side of the hiring coin the majority of my career, when a fit is bad it's usually just that -- the candidate isn't incompetent or a bad person it's just not quite what our particular company is looking for. There's no useful or relevant "advice" to give to the candidate other than explaining in great deal the idiosyncrasies of our team culture and hiring process... this isn't useful. It's not like we have the secret recipe to what makes for awesome programmers and have license to dispense that upon all who fail our review.
With a letter like that you've just burned that bridge.
For example, my reactions to:
'Unfortunately this is our interview process and we have to abide by it'?
That's not misfortune, that's you dodging what responsibility's rightfully yours. You're a startup, you could not abide by it if you wanted to.
'It's difficult for me to say this and I don't know how to say it properly, but we think you're pretty good but doesn't quite clear the bar for us.'
Don't quite clear the bar? You're potentially making an absolute measure of someone's ability there as not good enough. They may very well have good skills in some areas not relevant to you, or just interview poorly - or you might be a cruddy interviewer. Stay away from making absolute statements about people as unified individuals. We can accept, sometimes, some unlovely facts about ourselves - it's difficult to accept that as an entire person we're not good enough.
#
I suppose I might write a similar letter as something like -
-----------------------
Dear X
Thank you for spending the time to interview with us on DAY. On this occasion there was a more qualified candidate. However, if you further developed X Y Z, your skills would be a better fit for the hiring profile.
If you'd like to be kept aware of our vacancies in the future please sign up for our hiring list ....
Yours sincerely,
Ms First-name Second-name
-----------------------
Again though, you probably feel differently about a lot of that than I would.
Telling someone their faults can be either a nice thing to do or a nasty thing to do, but it's difficult to do it either way without the risk of hurting someone.
Some of that's in how you phrase it - 'you fail here' is generally worse than 'you could do better here.' Cloaking it in apologies, even when they're true, rarely goes well though IME. Someone who's just been hurt is rarely going to care that much that you're sorry unless they care a lot about you. (Might give them a target though if you're admitting fault.) They're gonna be caring about themselves, that's where their attention's just been directed after all. So, talk about that if you want to be nice. What's in it for them? How can you make them feel better about the whole thing?
Tricky to know how to do that without knowing the person fairly well.
Generally, I wouldn't give feedback unless asked for it. It feels too presumptuous on such a fragile relationship.