I mean, I don't even have to suggest; I can let the OP suggest instead. > Having an interview process that is artificially arduous Make your interviews less a

I mean, I don't even have to suggest; I can let the OP suggest instead. > Having an interview process that is artificially arduous Make your interviews less artificially arduous. > way outside the expectations of the job duties Re-design your interview questions to be more in line with the actual job. > leetcode monkeys who can barely deploy and manage k8s cluster on AWS See previous suggestion. If you want my personal suggestions on interviewing better: - Interview for problem-solving process, not just for correctness. A candidate's ability to solve an algo problem in 45 minutes is much less important than their ability to calmly, thoroughly, and clearly explain the way that they think. - Tune interviews to the role at hand. This should be obvious, but for some reason full-stack web devs still have to pretend like dynamic programming is a big part of their daily work. - More systems interviews. I find that it's much harder to bullshit/memorize here, at least not for very long. - Interviews based on actually building stuff. "Hey, here's a super simplified version of a feature someone in your role built last month. Can you walk us through how you would build the same thing?" Interviewing is hard. It's not that fucking hard. When someone is out here complaining about what they see as obvious flaws in their process, and then decide that the best course of action is to "gatekeep as long as others play too," it just reeks of laziness and self-interest. This does not get better unless individuals decide to start making it better. That's my biggest suggestion, really; don't become a cog in the machine. Every single interview that you, personally, conduct has a small but meaningful impact. It's up to you to have that impact be positive or negative.