Hacker News new | past | comments | ask | show | jobs | submit login

I am skeptical. Because I see this issue in my country too where opening yourself to liability is not an issue. Maybe one could argue that it is due to cultural influences from the US which are copied without the original context, but ... eh, I feel it is pretty weak.



Liability and "speaking for the employer" aside...

When I was first starting out, I found a job posting that I really wanted, so I applied and interviewed. I felt the interview went pretty well, but I got a call back that I wasn't what they were looking for. It was a small company, and the head of IT called me back to give me the bad news.

I really wanted the job, so I asked why. He told me I was too junior of a developer, and didn't understand OOP well enough. Being young and cocky as I was, I straight up told him I disagreed (looking back nearly 15 years, he was totally right). I didn't recall talking about OOP, per se, in the interview, and I had nothing to lose at this point, so I pressed the matter. I doubt it was OOP specifically that concerned him, and that it was more of a proxy for my inexperience. Either way, somehow I managed to get him to ask me about OOP over the phone. We talked a little about the vague concepts, and I have no fucking idea what happened, but he changed his mind and offered me the job. It was a great job, and I quickly learned how inexperienced I really was, but I grew a lot.

What am I getting at... in forums, you still _want_ them to participate, and come back. It is the opposite in an interview, you have essentially ended the relationship. Offering feedback starts the conversation again, and gives punks like me a chance to drag it out, disagree, and waste your time. We are just as likely to disagree with your assessment, if not more so, than to take it to heart.

Thank god he gave me another chance, I loved that job


I like how your story is both a lesson to really push to get what you want, and a lesson to not ever give people the opportunity to do so.


It depends on how the candidate treats it, and it definitely warms my heart when I get actually useful feedback from failed interviews. Though I definitely understand it isn't sustainable for a company to do that, since for every reasonable person, there would be 10 who would argue to death why the interviewer was wrong.

Surprisingly enough, one of the places I least expected to get useful feedback from wasn't some small informal start-up, but a fintech giant Citadel. I already had a feeling about my weaknesses that led to failing their onsite, but their rejection email (with the feedback) helped me way more than that. Not only they pointed out those specific things I knew about already, they also pointed out a few others that I missed (that were all true) and gave me actually something useful to work with. Just wanted to express my gratitude for that, because I definitely (at least partially) attribute my improvement in those areas to that email.


You make it sound as if he regretted hiring you. It's a pain in the ass to find people you want to hire and I'm always relieved when we successfully fill a seat. If someone can convince me at the last minute then more power to them.


You are right, I didn't mean to imply that. But I did feel that in that moment on the phone, he regretted giving me a chance to speak (but I have no way of knowing that... maybe he knew exactly what he was doing). I genuinely didn't expect him to change his mind but I didn't want to make the same mistake, whatever it was, in my next interview.

In the end, it worked out for everyone. I spent 11 years there, finally leaving after we sold the company, and still keep in touch with many of them.




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

Search: