Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah almost anything is possible so one really has to try not to obsess about it too much. I know it's hard. I can't say I'm able to do it either.

Anyway, my anecdote: we were interviewing for a C developer position. The next candidate was in his 50s. Our project leader took a dislike to him the moment he saw his resume. No idea why but I assumed it was either his age or that this project leader knew him and didn't want to work with him for some personal reason.

The project leader arrived to the interview at least 40m late. In that time this candidate impressed me (as the C guy) very much and I said 'hire' immediately. However, as presaged, the project leader said no.

This candidate had no way of knowing what had happened. He definitely could tell I was impressed so he probably assumed it was his age. Just imagine how he must've felt. I probably should've contacted him to let him know how messed up the our process was.



Not sure how legal this is (the giving insights into your internal processes to a stranger part) but since there are no trade secrets involved I'd imagine it's quite safe.

As I said above, it can be really bittersweet knowing the details but I'd advise you to strive to show maximum sympathy -- including contact them privately and let them know what and why happened.

It's a little comfort for somebody who is about to run out of savings to hear "sorry that our process is so effed up, dude, and best of luck in the future!" but I can assure you that it helps them make peace with that past further down the line.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: