3 ms·
Yes yes and yes. On #2 if a candidate gets to a technical interview they are fairly likely to know if they crashed and burned or not. If they are not right for
by midnightclubbed 12y ago
Yes yes and yes.
On #2 if a candidate gets to a technical interview they are fairly likely to know if they crashed and burned or not. If they are not right for some other issue (they didn't communicate clearly, were rude, dwelt on negatives about previous employers) then there is not always a professional way to say it other than a straight NO.
A decent candidate will learn from difficult questions and things they tripped up on. If you are acting professionally, asking pertinent questions and responding to the candidates answers then you are providing all the help they should need to nail their next opportunity.
- namelezz 12y ago"providing all the help they should need to nail their next opportunity". Too bad most interviewers do not care that much to go that far due to legal risks, especially here in US.
- midnightclubbed 12y agoThe interviewer generally doesn't need to explicitly tell the interviewee what went wrong (and yes there are possible legal implications if you do). As an interviewee if you are unable to answer technical questions (and unable to work through to the answer without being told the solution) then it should be obvious what you need to work on. If the interviewer asks a question that you stumble on or give a vague answer to then that should also be flagging something to work on. Of course you can seem to nail the interview and get no-where but in that case you're being rejected for something out of your control (another better candidate, internal politics) in which case you have a good chance at your next interview. Or you are delusional about your own skills and experience, not sure what to do there though!