They don't have to provide feedback, so they don't have to take the risk if they don't want to.
Don't really think your comparison was fair.
Most people, ESPECIALLY people who ask you for feedback, do not want feedback. They want to get in a fight with you.
Edit: I don't remember ghosting anyone personally in either setting, but it's happened to me plenty. Getting upset about it just means you're new to the experience.
The data I've seen suggests you're totally wrong about this.
I work at a company in the recruiting space. My primary role is interviewing technical candidates, and we provide very detailed feedback to candidates of all levels, regardless of whether or not we move forward with them.
People consistently tell us they love the feedback that we provide - in fact, people say the feedback we provide is one of the best parts of their experience with us.
Detailed feedback can mean a lot of different things. Recruiters always think they're giving people detailed feedback. That's nothing compared to an honest code review.
Bearing in mind that code reviews often cause tension even in fully employed people, it's hard to imagine they're always well received by job seekers.
The application process was partially automated, with multiple human reviewers that provided detailed scoring on the applicant’s performance.
Initially, we provided a score breakdown to applicants, but we turned this off within a few weeks after a cascade of hostility.
"Based on our interview we think you would really benefit from studying up on data structures and algorithms. If you want to study this stuff on your own, many people find (link) and (link) useful. But there's also (link) or (link) books available on amazon that we've had people recommend."
Or: "We were impressed by your spoken communication skills, but sometimes you seemed to struggle to remember specific technical terms for some of the concepts and areas we discussed...."
The feedback emails themselves are assembled from a mix of interviewer notes and reused snippets for comments we give frequently. This sort of stuff has been very time consuming for us to prepare. At the volume of candidates we interact with, we think its definitely worth it. But its possible that no feedback is better than bad feedback, and most organizations might not have the time to write good feedback to candidates.
But I can say with confidence that almost everyone really appreciates the feedback we send. While its easy for senior people to find work at the moment, there's lots of junior people out there sending dozens of resumes for every call back. Receiving rejection after rejection from companies (or worse, being ghosted) without even being told what you're doing wrong is a really awful experience.
I've been interviewing candidates for more than 15 years (for PhD /RA positions and then for Engineering) and every time I've given honest feedback, candidates just get into an argument on why they think the feedback does not apply to them...
It is just not worth it. If I want to know how am I at certain skills... I test myself in a less "charged" environment.
They want to explain themselves. There is a difference. What you consider an argument or fight is just a Hail Mary, almost an involuntary recovery attempt, for some.
Accepting feedback without trying to dig your way out of a hole or justify your actions is a sign of maturity.
Once you've been a hiring manager and reviewer long enough, it becomes obvious that, while the intent behind giving feedback is good, the reality of it is messy, and provides no consistent upside to the company.
How did I find all of this out? Over A month later, they called me back.
This was after I had been strung along by the business owner and the guy that interviewed me for over a week where they were going to make a final decision about hiring me..and then nothing. They couldn't be bothered to return my phone call or respond to any emails.
They left a message that I had to schedule an appointment with the guy that interviewed me to basically interview me again.
I, of course, never called them back, but sent both of them a nasty email telling them to fuck off in so many words.
I never thought I would be ghosted like this from a potential employer.
Get used to it. It sucks but if I got upset like I used to when a company ghosts me (I'm not just talking about after initial phone screens but even after lengthy on-site interviews), I'd be dead from the stress by now. It happens so often these days. Some companies behave decently but it seems that many more companies are following the lead of recruiters and behaving like jerks.
I'm sorry but that's just ridiculous: we give every applicant we speak to feedback and not once has anybody "got into a fight with us".
> Then maybe there can be a system that provides a disclaimer where they waive all ability to sue or otherwise get into a fight with you.
This ain't gonna help though, because it's not particularly useful at preventing the damage that these companies are afraid of, so it's not really going to tilt the existing balance.
Perhaps companies are just behaving too conservatively, and there is room for interviewing platforms to improving the hiring process by giving the helpful feedback that applicants crave.
Here in Texas, at least, that sort of thing does not seem like something that would ever be a real legal risk. This is a right-to-work state; I figured it’s pretty hard to get sued here.
The advice you will get on HR side is because no binding arb. agreement is in place you are exposed to full litigation efforts including attorney fees.
These can involve disparate effect or implicit bias - which can be difficult to defend against.
> Most candidates finish the coding section in 40 minutes. You took 60 minutes.
> In the system design part of the interview, the candidates we hire talk about SLA requirements.
Facts. No interpretations.
I am not even telling the person what they should do.
A good typical whiteboard interview naturally includes hints, feedback, and collaboration. After several hours of it, we have a very good idea of how well they may respond to feedback from members of our organization.
Honestly, I love giving feedback. I love helping candidates be better at interviewing. Bad interviews are painful to the interviewer too. I'm out of a small market so people and word gets around.
If it really isn't their fault they didn't get the job, we try to make that very very clear. It really sucks when we have to pass up on someone who absolutely killed the interview because someone else did better.
The harsh reality is, many people that don't pass on the interview are people we do not want in the industry. The good ones we give every hint and help we can.
There's also more tactical ways of extracting feedback from companies rather than directly asking for it. We can't tell you about how you did well after rejection, but we can talk about what our expectations are during the interview; put two and two together. I've noticed the good candidates that are serious about improving their interviewing do it, and from the company side, it's a strong signal they're not trying to contest a decision.
Food for thought, when was the last time you gave a company feedback on their interview process? I've traded feedback for feedback quite successfully many times when I was interviewing.
Interviewer: you have great interpersonal communication but I think you need a bit more knowledge in python techniques XYZ. I like being up front and transparent, and the python stuff is a big deal to us, so although you had a great set of traits, we want someone stronger in python.
Me: Thank you for giving me a clear indication on what was important, where I was strong, and most importantly, for not giving me a “we’ll call you if we want to move forward” response. I highly respect you for not wasting my time unnecessarily.
It's pretty bold of you to claim your interview can accurately qualify candidates across the entire industry.
Maybe you have found an interview that works for most companies? There's chests of gold waiting for you if you have.
These are the candidates that can't FizzBuzz or even write a line of code and/or are humongous asshats.
> A good typical whiteboard interview
So, your employer does give feedback to candidates on request? It must be difficult for you to find places that are acceptable to you to work, since very few companies typically give feedback. Or do your friends just not usually ask for feedback and as a result that clause on your criteria never trips (i.e. the company wouldn't have given feedback, but since your friend didn't ask, you don't strike it off your list)?
Hot take: you could hire someone who did absolutely well in the interview, and they could find a few weeks into the job that they loathe everyone, and go on a social media rampage.
And even in places where it does, like Texas, I've never heard of it being applied to software. Like Dell doesn't require a degree for their engineer positions.
A lot of software developers call themselves engineers without even having taken physics 101!
What I’m getting at is, there will always be bad apples, or people who react in a way that damages your organization. But not providing useful feedback to people who ask for it simply because one person went crazy is punishing a lot more people because of that one. Who knows if all of their negative karma ends up being worse in the grand scheme of things?
I personally avoid applying to places that other engineers tell me to avoid because I trust their opinion more than I trust a company selling me the highlight reel in an interview. If a trusted engineer said he got a rejection in an interview, asked for feedback, and none was given, I’d avoid that place too.