2 ms·
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 a
by 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.
- rhizome 9y agoThat's why I suggest limiting the importance on feedback there. Nothing they said suggests this feedback is the most important thing to them, they were only asking for a quick email.