That's fine if you can get a job after a few interviews, but when a talented job searcher has to go through that dozens of times to get a job offer, and much of the interview is "leetcode" questions that don't evaluate the skills you'll actually use, is it surprising people are frustrated by the hiring process?
I got fed up this about 8 years ago when it felt like this approach started.
I would go in for a front-end role and people would start asking me about .Net and show me .Net code and ask me see I could figure out why the code didn't work or troubleshoot some Python snippet.
I thought I would never walk out of an interview. When I walked out of three of them because of stuff like this, I kept asking myself if I was being unreasonable. I came to find out talking to other dev friends, this was becoming fairly common and I have no idea why.
All of the big corporations I worked at always focused on specialization. You a DB gyy? Then that's all you do and you're an expert. Front-end guy? Sure, know some design, but client side stuff you should be an expert. Now? Feels like, "How many roles can I hire one person for?" is the standard bearer.
> this was becoming fairly common and I have no idea why.
Too many chiefs, not enough braves. The length of the interview process has grown with the proliferation of scrum masters, project managers, project leads, business analysts and seemingly endless other roles.
I miss the simple days of direct lines of management and shorter, simpler interviews.
That's fine if you can get a job after a few interviews, but when a talented job searcher has to go through that dozens of times to get a job offer, and much of the interview is "leetcode" questions that don't evaluate the skills you'll actually use, is it surprising people are frustrated by the hiring process?