3 ms·

If it's specifically about feedback on the whiteboard exercise, I find the legal excuse to be a bit weak. It is something organizations will hide behind becaus

If it's specifically about feedback on the whiteboard exercise, I find the legal excuse to be a bit weak. It is something organizations will hide behind because it's a lot easier to say, "I'd love to give you feedback, but HR/Legal says we can't because of liability concerns." That makes the company look like the good guy, just blame the system. Specifically on the whiteboard, the primary reason for not providing feedback is very simple - HR and managers have jobs to do, and they're going to focus on their primary duties on the business side, and active candidates on the HR side. Once you didn't pass the exercise, they're not going to spend time on you because that's inefficient for them - essentially sinking someone's time to write you feedback when you ultimately won't be working for them. In the US, anyone can be sued for anything, so it is technically true that there's a legal reason not to give feedback there. But I think the risk of that takes a back seat to simply not wanting to spend the time on something that isn't seen as valuable to the company even if it is to the excluded candidate. Now, as to everything else, particularly "fit" and all of that - yeah, there's a very valid legal risk that would suggest you should not provide that feedback. Fit is subjective, and a lot easier for someone to decide fit meant age/race/sex/etc. My final opinion is that this type of feedback wouldn't actually be useful. It sounds like it would be, but that suggests that hiring orgs all think the same. They don't, and that's good for all of us.

vinhboy 9y ago
> If it's specifically about feedback on the whiteboard exercise That's exactly what I am asking for. I am not looking for feedback on me personally, but I would like to know why I failed the whiteboard. If I did something wrong, or inefficient, I want to know this. It's such a good learning opportunity, it's a shame for it to be wasted. And it won't even take that much time. Just send me a quick email. I always ask for feedback, so one company said something along the lines of "you didn't use OO, and you didn't name functions very well for someone with your experience" That was like a lightbulb moment for me.
- SmellTheGlove 9y ago
  The thing is, if you know you screwed up the whiteboard exercise, you should think about whether you need anyone's feedback. There are lots of materials and guides on working whiteboard exercises, given how pervasive they are in the industry. If you're self-aware enough to know the whiteboard exercise sunk you, you are in a good spot to identify and fix your weaknesses. This is not intended to be harsh, but comes across that way in writing: It's not a wasted learning opportunity just because someone else isn't willing to read out your evaluation. Critical thinking is as important as any other skill to a developer, so you going back through what you did and then looking at opportunities for improvement is as valuable as anyone else's feedback. I get that it's helpful, all I'm saying is it's not entirely necessary, and not a showstopper to improvement.
  - vinhboy 9y ago
    I mostly agree with you and I very much do what you suggested. After all my interviews, I spend a lot of time researching the question to see what the correct answer is. For example, in one interview they asked me to make a crossword puzzle solver. After the interview, I spent the rest of the day researching algorithms to do this. That's great and all, but it doesn't give me insight into specific things I could improve for the next interview. Was I too slow? Was my solution too convoluted? Did I spent too much time thinking and not verbalizing? Is my solution wrong? I wish to have that kind of feedback because it will highlight my deficiencies. I get that they don't owe it to me to provide that feedback, and there is no incentive for them to. But it's a nice to have. As software engineers, we're all familiar with code reviews and why we do them. This is very much similar to that.
    - SmellTheGlove 9y ago
      > That's great and all, but it doesn't give me insight into specific things I could improve for the next interview. This is where I have an issue - it presumes that the interviewer knows more than you! They might, but the next interview might care about a completely different set of issues. That's why I suggest limiting the importance on feedback there. It's as good as the person giving you feedback, and you don't have much to go by on that. You also don't know if it's the whole story or the whole truth. > I get that they don't owe it to me to provide that feedback, and there is no incentive for them to. But it's a nice to have. I agree it's nice to have. I'd probably provide it if I did whiteboard interviews.

vinhboy 9y ago

> If it's specifically about feedback on the whiteboard exercise That's exactly what I am asking for. I am not looking for feedback on me personally, but I would like to know why I failed the whiteboard. If I did something wrong, or inefficient, I want to know this. It's such a good learning opportunity, it's a shame for it to be wasted. And it won't even take that much time. Just send me a quick email. I always ask for feedback, so one company said something along the lines of "you didn't use OO, and you didn't name functions very well for someone with your experience" That was like a lightbulb moment for me.

SmellTheGlove 9y ago
The thing is, if you know you screwed up the whiteboard exercise, you should think about whether you need anyone's feedback. There are lots of materials and guides on working whiteboard exercises, given how pervasive they are in the industry. If you're self-aware enough to know the whiteboard exercise sunk you, you are in a good spot to identify and fix your weaknesses. This is not intended to be harsh, but comes across that way in writing: It's not a wasted learning opportunity just because someone else isn't willing to read out your evaluation. Critical thinking is as important as any other skill to a developer, so you going back through what you did and then looking at opportunities for improvement is as valuable as anyone else's feedback. I get that it's helpful, all I'm saying is it's not entirely necessary, and not a showstopper to improvement.
- vinhboy 9y ago
  I mostly agree with you and I very much do what you suggested. After all my interviews, I spend a lot of time researching the question to see what the correct answer is. For example, in one interview they asked me to make a crossword puzzle solver. After the interview, I spent the rest of the day researching algorithms to do this. That's great and all, but it doesn't give me insight into specific things I could improve for the next interview. Was I too slow? Was my solution too convoluted? Did I spent too much time thinking and not verbalizing? Is my solution wrong? I wish to have that kind of feedback because it will highlight my deficiencies. I get that they don't owe it to me to provide that feedback, and there is no incentive for them to. But it's a nice to have. As software engineers, we're all familiar with code reviews and why we do them. This is very much similar to that.
  - SmellTheGlove 9y ago
    > That's great and all, but it doesn't give me insight into specific things I could improve for the next interview. This is where I have an issue - it presumes that the interviewer knows more than you! They might, but the next interview might care about a completely different set of issues. That's why I suggest limiting the importance on feedback there. It's as good as the person giving you feedback, and you don't have much to go by on that. You also don't know if it's the whole story or the whole truth. > I get that they don't owe it to me to provide that feedback, and there is no incentive for them to. But it's a nice to have. I agree it's nice to have. I'd probably provide it if I did whiteboard interviews.