upvote
I applied for a role involving Linux kernel development, TPMs, and corporate security. I got rejected immediately. I was able to follow up with a friend in a senior engineering position who was able to get my resume in front of the hiring manager, and I was interviewed the next day and made an offer less than a week later. An anecdote rather than data, but on the other side you're rarely going to see the people you're missing out on - they may be filling positions with people they're happy with, but that doesn't mean they're filling positions with the applicant who'd do the best job.
reply
I'd counter this with two realities;

Firstly, most employers don't specifically target "best". Partly because "best" is hard to define, and includes measurements across multiple axles. And partly because it's impossible to know you have just seen the "best" so leading to paralysis.

Typically companies thus target "good enough" and for lots of positions there are several candidates that fit that bill. Sure they'll choose the one they think will be the best, but there's no way to know for sure.

Secondly, and speaking generally here, for most of us, this is probably a good thing since it's very likely there is a better candidate than me out there somewhere. If companies only hire "the best" then all us "second best, still good enough " folk would struggle a lot more.

Of course we all think we are the best possible option. Because we value our strengths and devalue our weaknesses. But objectively what are the odds that out of hundreds of applicants we're the actual "best"?

This doubly so when so many high quality people are looking for jobs?

reply
I can't say I'm absolutely the best possible candidate for the role, or even that such a thing is objectively measurable, but in this case the fact that the process went so quickly the moment I got in front of them is a pretty strong indication that something went wrong in terms of the initial rejection. Anecdotally I've heard other people in similar positions, and on this occasion I was just fortunate enough to have a side channel.
reply
From a purely utilitarian perspective, good enough is often better than best, as the good enough employee is likely to be cheaper and have a longer tenure than the best.
reply
Yep, that’s why companies generally don’t hire people who are overqualified for the position.
reply
> And partly because it's impossible to know you have just seen the "best" so leading to paralysis.

This is the (unfortunately named) "secretary problem": how do you decide when to stop interviewing and make a hiring decision? It's possible that the first person you interview is the best candidate you're ever going to find, but you don't know that. At the same time, you can't just keep interviewing forever, hoping that you find someone better than everyone you've seen so far. But you can never be 100% confident that you've found "the best" - you just have to get to the point where you're happy that someone is better than the others.

The unfortunate reality is that the first candidates to be interviewed won't ever get an offer, because there aren't enough data points to make a decision yet. Which can be comforting if you've ever interviewed somewhere and thought you did well but they went with someone else - you might have just been too early in the process.

https://en.wikipedia.org/wiki/Secretary_problem

reply
> The unfortunate reality is that the first candidates to be interviewed won't ever get an offer, because there aren't enough data points to make a decision yet.

This doesn't follow in any way. Sure, the offer the first candidate might receive will be delayed, but if you're looking to fill a position in 1 month and the first candidate you've seen was still the best you saw in that month, you'll of course make him an offer.

And I am saying this from experience - we've often hired our first candidate for an interview in my team. Though I will admit that we don't follow much of the practices I read about and have heard from other friends, so maybe we are not typical in this either.

reply
That assumes that candidates are ok with waiting a month to hear the results of their interview, which in my experience isn't realistic. Also, the best candidates have plenty of options. So there's a significant chance that if they are actively looking then they'll receive another offer in that month. Even if that's just because the other company interviewed them further along in their process and is comfortable making an offer quickly, because they have enough data points to know how good they are!
reply
Mag 7 companies typically take months to finish an interview/hiring cycle. It took over three and a half months to join Google for me. Similar but shorter for other Mag 7 companies I have worked for.
reply
No, it’s broken. On the hiring side, most resumes are fraudulent, most phone screens will be with foreign spies, and the sheer quantity nearly drowns out the plentiful number of good candidates. Also our old way of doing code challenges doesn’t make sense in the age of AI.
reply
Last year I helped a friend’s startup hire for multiple SWE positions and it was easily 75% North Koreans.

It got so bad I opened every interview with “You will be required to travel to San Francisco to meet with the founders, they will pay your travel expenses, is that an issue?” - and click hung up. Once had this happen 4 consecutive interviews.

I did approximately 32 interviews and maybe 8 were not NK.

reply
> "You will be required to travel to San Francisco to meet with the founders, they will pay your travel expenses"

There were times when that actually was the case, can you imagine?

reply
Arguably it didn't make sense before either.
reply
I agree, but it’s definitely worse today. The only positive as a hiring manager is that there is better talent out there than normal. As a candidate, it’s clearly terrible.
reply