More generally I learned that giving proper feedback is statistically worse than not doing so.

When I started doing technical interviews I wanted to be different than other companies giving canned unfortunately.

I naively thought that explaining candidates what went wrong would be appreciated, because I would've wanted to know if I was in their position.

To the guy that had 20 technologies in their CV but failed to answer on any topics I would suggest:

"Anything you put on a CV increases the risk of you being asked about it. Maybe try to move those you don't want to talk about to previous experiences instead of a "skills" section. If you list C but can't answer basic pointer or compilation questions, or you put Node.js but can't talk about eventemitters or TypeScript but can't describe a union, you are casting a giant doubt in the other 17 technologies you have listed, even though you might be great at them."

Just to be met with a 300+ likes post on LinkedIn about how my company expected the impossible, was _hiring a team instead of an individual_ and how I was the worst interviewer in the world.

I thought it was a one off, but months later I would get occasionally angry candidates emails arguing my feedback and how I didn't understand how good they are.

Then I realized why corporate bs talk it is the way it is. Genuine content and feedback, especially in the social media age is a liability, it has more cons than pros.