I’ve hired for 3 companies for engineers from entry level to staff level, and for non technical candidates for other departments. Applicant tracking systems like greenhouse send me an email for every application that comes through, you get the resume and cover letter attached. There’s a reject candidate button where you choose why, and it auto fills in the template for you with the reason you selected (and the email was pre written).
Don’t mistake an automated email for assuming your resume wasn’t looked at.
I don't fill my my resume with a bunch of spam buzzwords for every adjacent technology I've ever used, because certain things are kind of implied by other things. If I put "set up multiple clusters across different Linux systems", I don't also cram in "systemd, bash, upstart, scripting, ls, cp, du, nohup", despite the fact that I know how to use all of those things, because I think they're implied by "me setting up Linux clusters".
A software engineer reading my resume would come away with a decent understanding of what skills I have, but a recruiter who doesn't know anything outside of keyword-matching and hitting the `fwd` button in Outlook (which appears to be most recruiters) will see "HE DOESN'T KNOW BASH, SEE HE DIDN'T PUT IT ON HIS RESUME."
Now, of course, most of this is on me, it's up to me to learn how to play the game, whether or not I like the system doesn't really change anything, but as far as I can tell, the "solution" to this is to turn my resume into a low-quality SEO-spam piece of shit so as to try and satisfy the most incompetent person who might read it.
If a posting gets 500 applications (which is about how many apps the last 4 roles I’ve listed got before we closed them) and we have an engineer spend 5 minutes per resume reading through each resume, that’s a full week of engineer time spent on screening alone. That’s not a good use of time when most of the resumes are a straight no.
I’m assuming your writing style is different in professional environments, but if it’s not, and I saw even like 10% of the snark you’ve put here, I’d instantly dismiss you unless we were hiring for a principal into fellowship IC role and you were a 100% match.
If you’re writing your resume to be read by software engineers or sysadmins, you’re writing for the wrong audience. That’s not their fault for being “incompetent”, it’s yours.
I don’t write it to be “read by software engineers” per se. I describe my skillset and things I have worked on. I don’t load it with a million buzzwords of every single noun that I am aware of.
I acknowledge that I probably play the game “wrong”, insofar that there’s any “right” way of doing it, but I don’t have to like the game, and I certainly am allowed to think that it’s very frustrating that I have to fill my resume with SEO spam of synonyms because most recruiters are unwilling to learn anything more than basic keyword matching.
The same is true of those other fields too really - I certainly wouldn't want a newly qualified doctor operating on me, or lawyer defending me, or civil engineer designing a bridge I'm driving over. It's nice to know that someone has been professionally educated and passed some entry level exam, but to be useful in a field it's experience that counts.
Not to mentioned I spend forever doing it, there's so many and I wouldn't want to do it halfway...
A scary number of candidates did not take rejection well and tried to use my feedback against me. I had people trying to argue that my feedback was wrong, someone stalking me across social media and trying to argue everything there, and eventually someone who threatened to use my feedback as the basis for a discrimination lawsuit.
So now we’re back to simple “we’re proceeding with other candidates” feedback.
If we’re going to play the blame-game, then you have to see the full picture. Many candidates can be awful and even vengeful. Many people do not handle rejection well.
The line is between saying something brief and saying nothing.
Somehow, it has become standard to say absolutely nothing instead of telling people a simple no.
I've even had situations where people said they wanted to keep talking to me, and then went completely silent.
The sad truth of the situation is that all the incentives for a company point in the direction of giving no feedback at all. This isn’t because hiring managers are sociopaths.
This happened to one of my bosses. As a result, I've never attempted it.
Except once, a candidate realized at the end of a technical screen they had done poorly and demanded feedback. I gave an initial bit (shouldn't have, my mistake) and instantly turned it around on me.
Hell if companies would even do that - I've spent a lot of time (7+ hours) interviewing with some known companies including meeting with the VP of engineering and then they just stop messaging and ghost you (looking at you Glassdoor..)
For example, in an interview once I got the typical "design Twitter" whiteboarding question, and it's going fine, until the topic of databases and storage comes up.
I ask "do we want consistency or availability here?"
The interviewer says that he wants both. To which I say "umm, ok, but I thought you said you wanted this to be distributed?", and he said yeah that's what he wants.
So I have to push back and say "well I mean, we all want that, but I'm pretty sure you can't have stuff be distributed or partitionable while also having availability and consistent."
We go back and forth for about another minute (or course eating away at my interview time), until I eventually pull out my phone and pull up the Wikipedia article for CAP theorem, to which the interviewer said that this is "different" somehow. I said "it's actually not different, but lets just use assume that there exists some kind of database X that gives us all these perks".
Now, in fairness to this particular company, they actually did move forward and gave me a (crappy) offer, so credit there, but I've had other interviews that went similarly and I'm declined. I've never done it, but I've sort of wanted to go onto LinkedIn and try and explain that their interview questions either need to change or they need to become better informed about the concepts that they're interviewing for. Not to change anything, not to convince anyone to suddenly give me an offer, but simply to prove my point.
And I say that even while writing this comment in Firefox
... Legal action on what basis, exactly?
Dumb example, say you didn't hire someone because they wore a Marilyn Manson Antichrist Superstar shirt to an interview and you think that's not appropriate attire for an interview, and suppose you put that into your feedback for the rejection letter.
Now the candidate has a specific "I was rejected for this shirt". They might come back and say "Actually I'm a satanist and this shirt is part of my religion, so I'm going to sue you for religious discrimination". Suddenly you have a lawsuit on your hands, simply because you thought they were dressing unprofessionally.
Obviously this is a hyperbolic example and I doubt that there are a ton of Marilyn Manson fans trying this, but it's just to show my point: It's much safer to simply leave it vague with something generic like "while we were impressed with your qualifications, we've decided to pursue other candidates" email. They can maintain plausible deniability about the reasons they rejected you, and you don't really have fodder to sue them over that.
That said, I absolutely hate how normalized ghosting is in the job world. A candidate isn't entitled to a job, but I do think they're entitled to a response, even if it's just a blanket form rejection.
Hiring manager here. I don’t like the situation either, but to honest a lot of what you’re seeing is a natural reaction to the shenanigans that applicants are doing.
When you post a job listing and get 500 resumes from people who aren’t even close to qualified and obviously didn’t read the job description, you understand why we’re not sending custom written rejection letters to every single application.
>When you post a job listing and get 500 resumes from people who aren’t even close to qualified and obviously didn’t read the job description, you understand why we’re not sending custom written rejection letters to every single application.
Awhile ago I applied to an internship at one of the larger, successful startups that most tech workers have heard of (several thousand employees). I got a response from a real person in a day. There's really no excuse for not being decent.
This is one of the few aspects of hiring I feel government employers handle better than private. My state hold monthly events where you can just show up and talk to a representatives and if you pass the vibes check you are virtually guaranteed a proper interview.