Ask HN: Why do companies not list your weaknesses in rejection emails?

56 points by leomarta ↗ HN
I applied for a SWE role with Gitlab. I received a standard rejection template post 48 hours. I wish if they have listed key reasons on why they rejected me. It could have helped me work on my weaknesses. I feel awful when rejections are void.

121 comments

[ 1017 ms ] story [ 484 ms ] thread
Most don't. They don't want to list something that could potentially be used against them in court. In addition, if you give people pointers like that people could "study" the interview by getting information from other applicants.
- it's more work - there's a nonzero chance nobody even saw your application, let alone carefully review it and think about whether you would be a good/bad candidate and why

- there's no incentive for them to do it - it's a rejection, they don't have a reason to please you

- the less information they give, the less exposed they are to liabilities like being accused of hiring discrimination

I think the possibility of a lawsuit is the main reason why feedback is generally not given
This is a big part of it. I've worked places we couldn't tell people why they were terminated for fear of a lawsuit, much less why someone's application was rejected.
There's also avoiding the people who want to debate your reasons.
- there's no incentive for them to do it - it's a rejection, they don't have a reason to please you

Oh, my gosh. The sheer quantity of candidates I reject. I have a complicated puzzle that is poorly described by the Job Description. In the interview, I try to see how you fit I to the existing puzzle. If you don't fit, then you "don't fit". As simple as that. Don't take it personal. Don't re think your life. Just... keep looking.

As an employer you are shooting yourself in the foot with a poor job description. Describing it as a complicated puzzle is not an amazing sign.
They didn’t say the job description was a complicated puzzle, they said the puzzle (in this case implied to be the position trying to be filled) is poorly described by the job description. Which is honestly a pretty accurate summation. There are a lot of things that go into making a candidate a good fit for a position, not all of which can be well captured in a job description
Job descriptions shouldnt be a complicated puzzle then. I once interviewed at a company and mid-interview I could see I was struggling, interviewers were super nice though helped me solve the problem they gave.

No wonder i didnt get the job, but rejection email said they thought I am a good engineer. I replied if they can tell me where I can improve. They did so politely.

Few months down the road, I improved and applied again. I got the job

You were always qualified and they shouldn’t have rejected you the first time. This is an example of what not to do on the hiring managers part.
No I was very unprepared, even I could tell
As an interviewer, my job isn't to judge whether a candidate is prepared. My job is to judge whether they can do the job.

If the interviewer says "I think you're a good engineer", the next sentence should be "we would like to make you an offer".

If I could hire people by reading their mind and understanding their ability, without requiring an ounce of preparation, I would do that.

I disagree that the second sentence follows from the first. Interviewing is a game of incomplete information, and you won’t find consensus among programmers for how they would rather be interviewed.

It’s entirely possible that the candidate was just off their game that day, or they weren’t “warmed up”. I get noticeably better at interviewing after the first few. It happens, but the interviewer has the information they got, and it’s not possible to totally control for that kind of variance.

What hiring managers should be actively minimizing, that most hiring managers I’ve seen do not, is variance that their interview process introduces by, for example, not standardizing and training their interviewers.

I don't this the job description is the complicated puzzle - its people that are the complex puzzle.

Even with the most perfectly defined job description, you might have many candidates who "fit" that description, so you have to weigh a lot of other factors which run a huge gamut. Many, many times I've had multiple candidates that are more-or-less the same in terms of experience, technical competence, ability to learn, get shit done, etc - so you start looking at other factors and it can get down to things like communication, personal hygiene, general awkwardness, etc.

Ehhhh I don’t know. I hire for a relatively junior level. I don’t require a lot of specific skills. I just want good reasoning skills and some basic domain familiarity. When I turn someone down, it’s usually an evaluation of their competency. I don’t really get a chance to communicate that, and it would be a bit uncomfortable if I could.
You may or may not be correct, so it would be fine. Many companies have awful interviewing practices.
> - there's no incentive for them to do it - it's a rejection, they don't have a reason to please you

Just want to point out that this really depends on your location - here in Switzerland, the talent pool is vastly smaller compared to the number of companies and open positions.

I have in fact, reapplied to companies before that had a very honest and feedback-rich hiring process and simply rejected me because they found a better fit with another candidate.

(For full disclosure: I reapplied at that company, was hired, and fired after three months for office political reasons. So do take this story with a generous pinch of salt.)

The discrimination thing is kind of bullshit. A just-so story. It's really not that hard to avoid liability on that.

Even so, lot of companies are deficient in explaining to their employees that certain kinds of discrimination are illegal, coz it still happens plenty - almost always during interviews. Remarks about pregnancy do happen.

It is more work to provide feedback (which I think is mainly what people hate) but it's better for your hiring reputation, provided the feedback isnt routinely nonsensical - in which case staying quiet probably is better.

> The discrimination thing is kind of bullshit. A just-so story. It's really not that hard to avoid liability on that.

Plus, if a company is worried that revealing their reason for rejecting is legally risky, then maybe they should stop rejecting candidates for legally risky reasons. If they are worried about a lawsuit, they might want to consider that their evaluation process could be either overtly discriminatory, or reliant on people’s personal biases (conscious or unconscious). For example if they reject based simply on some gut feeling, or whether or not they like the person, or the classic bias: “cultural fit”. Basically, reasons they would not want to have to articulate in front of a judge.

Perception vs reality. What in reality is just an objectively fine reason can be spun into a totally different perspective.
I don't think it really is better for your hiring reputation - if it were people would clearly know companies that gave great feedback, but honestly no one ever says "Oh I really like _company_, because they give great post interview feedback"
> - it's more work - there's a nonzero chance nobody even saw your application, let alone carefully review it and think about whether you would be a good/bad candidate and why

Also if they give reasons, I suppose it's also an invitation to the candidate to rules lawyer why those reasons aren't actually accurate and they should still get the job, which would be even more work for someone to deal with.

Hi, GitLab team member here. Due to a number of factors, which includes high applicant volumes, the talent acquisition team may not be able to provide detailed decline feedback. You can get more details on our handbook page: https://about.gitlab.com/handbook/hiring/interviewing/#rejec...
But you already have the detailed decline feedback (it's bullet point #2 [1]). The only effort on your part would be a simple copy-paste.

I have to imagine that something else in the "number of factors" matters much more than "high applicant volumes".

[1]: https://about.gitlab.com/handbook/hiring/interviewing/#rejec... > Everyone who interviews a candidate must complete a scorecard and are required to input pros and cons as well as an overall recommendation.

> it may not be possible for the talent acquisition team to provide detailed decline feedback

That sounds like the exception, but ok, what happens when it is not possible?

Like you know, send a message "Dear candidate, unfortunately the talent acquisiton team did not manage to provide decline feedback because of xxxxxxx[0] , sorry."

Or "nothing"?

And in how many cases does this happen?

Like 1%, 5%, 35% or 99%?

IMHO it would be much simpler to directly write in your handbook something like:

"No decline feedback will be provided. No exceptions."

This way the candidate won't be expecting it.

[0] Examples:

my dog ate the feedback

the feedback was stored in a cabinet that got flooded

the hard disk where the feedback was stored failed before a backup was made

idk about Gitlab specifically but its a slap on the face after dedicating 6 hours to jumping through hoops just to get ghosted.
There was no ghosting in this case, just a template rejection, two days later.
I think the "If people argue with the feedback..." section is more telling. The fact that there's a SOP for this means it happens a lot.
From an interviewee perspective, it's even worse when you don't hear anything; they just ghost you. That's the norm in my experience, though it's been a long time since I've done the cold interview thing.

From an interviewer perspective, I suspect it's mostly a time/volume thing. Last time I did it, I put out a req for a position, I'll get 10-20 resumes trickle in over the next week or four. I pick the ones that are the best of the lot and schedule interviews until I find someone that I think has the best chance of being successful. Some of it is the way the resume reads, some of it is how well the skills match what we need, some of it is just gut. I certainly don't have the time to go through all the ones that I didn't pick and give a detailed (re: useful) explanation on why. Most of them I could't really offer much advice other than there were better matching resumes. It's usually someone has more years experience, or were better able to articulate their experience, or had more skills that matched what we need, or had more experience in my particular industry.

Also, for most smaller shops, it's the devs that are doing the interviewing and filtering. Typically, we should have hired someone months ago, but companies usually hire later than they should, so I'm buried in work and I have the additional task of filtering resumes and interviewing on top of my already overburdened workload.

In my experience, most single person only interviews are done by someone who is probably not capable of giving a good enough explanation. And multi round interviews with several current employees would require a lot of extra work they simply don't have time for.
When you are applying for a job you are trying to sell something (your time). When someone is trying to sell me something and I don’t want it, I’ve learned the best approach is to say, “no, thanks” and not to give reasons, especially if they ask for reasons. Every reason is an opening for a conversation that I’m not interested in having.
Question for OP: did you attend an interview? In my experience, companies will usually provide a rejection reason if an interview has taken place, especially if you have been through multiple rounds.
Lots of legal liability and often more applicants than needed. Similar to the reason to not say anything in an exit interview and “ok thanks“ is really all employees get to say to management.
Possibly also because of the huge amounts of competition any individual rejection doesn’t need to “hurt” or be taken too seriously. Just know your worth and keep on truckin’. (But do make sure you’re a strong candidate, of course.)
Legal liability is paper thin excuse. Very few companies have been sued for sending an email after saying "we didnt hire you coz you look like you might get pregnant" and playing that off as a "risk" doesnt really add up. You protect against liability by telling hiring managers not to break the law before, during OR after the interview - coz the company is exposed in all three. Even so many companies are deficient in this regard.

Simple laziness and wanting minimize reputational risk from feedback on the feedback seems a more plausible as a reason why.

I think at the application stage, this is fair to not provide any reasoning.

I think if you were interviewed and even made it past a round or two, you should be entitled to some deliberate feedback.

They avoid doing so because of legal liability and other repercussions. I have always emailed them constantly until they get annoyed enough to reply with "something".

Many companies will provide a rejection reason in a telephone call that they would not be happy to put into writing.

Especially companies located in places where phone call recording isn't legal.

It's all about not leaving a liability paper trail.

Why even care? You should be aware whether u have the credentials and experience. Most of the time the rejection is a subjective decision by a small group of people. And as of lately big tech is freezing their hiring anyway.

Keep applying and don't wait for any one company to give any feedback.

Two reasons.

First, even if you perfectly know your suitability for the job, it's (perhaps unfortunately) true that interviewing itself is a skill you can improve at. Feedback is in general a great way to improve faster at things, so I think it's natural to want to know why you were rejected.

Second, if you were rejected for a reason out of your control that would inform what types of jobs you apply for in the future, so also useful knowledge.

I agree in the end that you should accept that you're not going to get much feedback, but it's totally reasonable to want it.

receiving feedback sounds good on the paper, and i understand how it would be helpful and ideal to receive it, but its just not how the real world works, as there is no business incentive to provide the feedback.

i would say in tech its fairly easy to establish hard skill competence during the interview. the remaining portion of why person gets hired is more fuzzy and is much like dating. they like you or they don't. asking why not rarely leads to any response or a meaningful response, because a lot of times they don't even know why, it might just be a gut feeling thing.

i wouldn't obsess about the outcome, as long as person is working on themselves in all areas and keeps trying, success will come.

Giving a reason will give the person a point to dispute. I used to work in customer service dealing with applications to join a membership website. Without fail if I told the person the reason they were declined they would argue against it. You're never going to change your mind so arguing is pointless. Much easier to say you weren't successful without specifics.
As a candidate, I wondered why I didn't get detailed feedback on why I didn't get a role - now I'm on the other side, it often comes down to:

- Time and volume: think of how many applicants they've been through and the time it would take to write this feedback for each of them

- A good chance that people will dispute the reasons, leading to more time, more effort and more chance of a lawsuit

If it's at the final or penultimate stage, I've known this to happen. I also find it more common coming through a recruiter (as the company will be speaking to the recruiter anyway and knows that they will shut down any disputes you have).

As long as there's a concrete rejection email rather than never hearing back, that's all you should expect.

Ask them for feedback on why your application wasn't successful this time and what they think you do to improve your chances of employment with them in the future. They still might not give you any, but in my experience most places will.

Then you can take their feedback into consideration for your next application. Sometimes it'll be something you can't do much about quickly (e.g. if there was a candidate with more experience than you). Other times though you'll discover a quick win (e.g. your application didn't clearly state your relative skills or experience).

Very simple - it all too often invites you to dispute the reasons. At the end of the day it's not productive for the employer to give you this because you will likely not accept it. As with many things in life the unfortunate reality is this is on you to figure out...
the best way to find your weaknesses is to just be more self aware.

no one can give you a better answer about yourself than you.

they usually dont even know why they rejected you. its not a logical thing. its mostly emotional.

I once got great feedback by asking verbally at the end of the interview.

I said "You've just interviewed me, what do you think I need to improve?" That way it's really easy for the interviewer to give the feedback and you get round any corporate policies about not giving feedback.

I always do that. I don't ask about improvement. I keep it neutral. So, what do you think?
Unless the feedback is more fluffy or there's something light and concrete (or just straight up positive), then that has always felt like a record scratching moment to me when I've been asked it. Not that it hasn't ever went well, but it's hard to ask that without coming across as "so how'd I do?". It's especially hard to juggle with straight being undecided because they were _okay_, but you have other candidates to interview that sound promising.

I think the question as phrased is a good way to ask it, and more likely to make it land. It just also has the potential to leave things on a more sour note than they would have been if not done right.

I'd respond that the evaluation is done after feedback from all interviewers is gathered and reviewed, and I can't comment on anything at the moment - there were a number of post-interview discussions where my opinion and opinions of other interviewers were different, sometimes slightly (we overlooked some additional evidence), sometimes substantially (e.g. no hire vs hire)
i have done this at time, depending on various things like whether i thought i wanted the job or not.

i prob read it somewhere as advice.

  In terms of qualifications or just being a good fit for the position, does it sound like I might be a good fit? Maybe I'm missing some experience? For instance, I haven't done 'x' but, to me, that's baby stuff. But are there some other things?
The main idea at this point is less 'to learn' and more to 'address aspects of my skills/experience/etc. that did not come thru during the interview'.
I always follow up asking why, to date (over about 18 years of memory) only about 4 or 5 ever responded, and of those I think only 2 actually said why but incidentally they were smaller more technical companies, corporates don't even give applications to a human anymore so I don't bother.

It's a disgusting practice tbh and should be dealt with properly by things like regulation but why bother I guess.

They do not inform you for a number of reasons, the most important of which is that they do not benefit from the information you think they should or could give you. And it could fire back. Through this lens, it becomes much easier to interpret many of the "easy things to do" that do not occur in personal and professional relationships.

Think about online dating. You chat with someone, they seem interesting, but you notice something you hadn't paid enough attention to when you were too caught up in your earthly desires. Maybe they live 40 miles away from you, maybe they have bad teeth, maybe they could lose a few pounds. You, an outspoken and, in your mind, generous person, decide to tell them that they are perfectly fine, but that you prefer someone a little taller than they are, or someone of lighter build, because you have always been active and you are not sure you can share your lifestyle with them.

You expect them to appreciate your candor and helpful cooking tips, but instead they tell you that you are a loser and don't know what you are missing out.

What happens then is that whenever you next feel you are losing interest in the person you are chatting with, you simply delete their profile: "Oh, well."

When some recruiter from an underrepresented minority working at a FAANG company got fired, they wrote a tweet thread where there were glaring mistakes and wrong concepts about everything.

Like they said the company hired 0 grads from Historically <Minority> Universities (HMUs) before they were hired, and they increased it to 300. And they said it was "a 300% increase". Their words, not mine.

When people from the co went to one HMU, and they hired a very low number of people, and the engineers wrote in their documents absolutely true things, like, "the grads have no idea about even the basic algorithms" (paraphrased). They cited that report and accused the engineers and the whole company of discriminatory practices.

Now, say, you start writing weaknesses, and write "lack of understanding basic arithmetic like GCD" for some of the candidates.

Now all it takes for your company and you to be accused of discriminatory practices is one zelous reporter from WaPo or NYT to get a sample of ~15 of these rejection mails and find your list of weaknesses. Then they just have to show that all of the ~15 people are from historically underrepresented communities.

This is the reason I am never going to do it.

This is a really good observation about how cancel culture works. Anything you say now that's considered perfectly harmless might soon be redefined as "code" for something unacceptable, and your words will be judged by that new ex post facto standard.
> Now all it takes for your company and you to be accused of discriminatory practices is one zelous reporter from WaPo or NYT to get a sample of ~15 of these rejection mails and find your list of weaknesses.

Sounds like this happened to you.

If you are an EU citizen, you can try using GDPR to request the feedback information they have on you. This might also work even after joining the company to see what feedback they wrote on you.

As people mentioned, companies have no incentive of putting the extra effort just to get more liability, and lots of candidates that would contest that.

While I get that there are various reasons as to why a company may not want to provide feedback, I recently interviewed for a company that:

- reached out to me through a recruiter

- had me go through multiple interview rounds and a take home

only to ghost me afterwards entirely (even after my asking for feedback). Once a candidate has invested time, you would think common decency dictates keeping them in the loop properly. But even that appears to much to ask in the current climate.

Sorry to hear! First, know that it's a numbers game, and your energy is better spent preparing for your next interview than wondering about this one. Second, talk to your peers. If you know someone who works at the kind of company you're applying to, they can tell you the vast majority of things that will make a difference. If you haven't, do a mock interview with one of them. That will reveal if there are any giant red flags, and those are the only things you should be worried about. Good luck!
To add to those who have said that there are legal implications, I would add anecdotally I was advised by my HR department not to give feedback for exactly that reason. (We had a junior candidate who misrepresented his experience on his resume, and I would've offered some advice about this sort of thing for the future.)

There is also often a very high volume of candidates for particular positions, and it is a challenge to offer feedback, especially when they're not brought in for a live interview.

In my own process, interesting positions result in me searching for hiring managers at the company, sending a cover letter+resume that includes a table of their needs listed in the JD alongside my skills. This tends to get me closer to the interview table and provides an opportunity to exchange enough information for feedback purposes. It's also a bit of a differentiator in terms of resume structure (more than one interviewer has commented on it).