3 ms·
See? This! This would make the job search process a lil' less opaque.
by NetOpWibby 9y ago
See? This! This would make the job search process a lil' less opaque.
- fooblitzky 9y agoOne reason I've been given for not providing feedback is that it could open the company to lawsuits.
- SilasX 9y agoHow? That's just general "how to do well" advice, it doesn't help explain which of the reasons were relevant to a particular rejection. And even that comment doesn't give an example of a shortcoming relative to one of those bullet points. I mean, from the comment it sounds like kaspm literally told the candidate: "hey, sometimes it just doesn't work out, you should be glad at 'batting .200'.". I don't see the actionable feedback.
- kaspm 9y agoAh sorry, this is a good point. Edit: I added the specific examples of each item that I gave the candidate but decided to remove them so as not to expose them publicly should this candidate read hacker news. People can PM me if they'd like to know more information about the way this particular candidate could have benefited from the above.
- SilasX 9y agoAh, that makes sense! Thanks for explaining. Sadly, that was the interesting part. But I don't really see the privacy issue if the name is left off and there's no way to figure out who it was you interviewed.
- web007 9y agoI'm interested in the details, but I don't see PM info in your bio. Please reach out to twitter@web007 or ryan at geekportfolio with anything you can share - I'm working on a side-side-side-project for increasing employability, and this kind of info is exactly what I want to promote.
- kaspm 9y agoI see that the contact info is private. Will do