StupidUser123
Discussing how many no’s it should take to reject a candidate is a worthwhile discussion. I can override specific no’s with good reason at my company, but not all companies have that.
My broader point is that this is a specific issue with the process we can iterate on. We don’t need to throw out the whole process.
My response was in good faith, and yours is not.
The processes you are questioning scale to thousands of people with varying backgrounds. It’s not an accident all of these companies do this. Your process places extreme trust in one group of people. It’s just so risky.
Also, resumes are mostly bullshit, IMO. Reference checks are complete bullshit, IMO. I’ve worked with my buddies at startups (who get lofty titles) and just have them give me reference checks. Other references have asked me for call scripts.
Also keep in mind that most of these big tech jobs are highly competitive. Your solution eventually requires a coin toss if you have limited spots. There’s only so much data you can collect from the process you propose. The natural thing is to then assess each candidate a bit more until you’re confident you’ve picked the right one. And then you’re here.
I’d take 15 interviews before taking that risk.
Scaling any process to thousands of people is always hard.
Is it annoying for candidates? Yeah, but we pay you a lot of money, and it does actually work for us. Is it perfect? No, but it does work.
“Hire and Fire fast” doesn’t actually work well if you want to give people a chance to succeed. Also people tend to keep low performers around too long. Best to avoid this as much as possible.