Also when people research interviewing styles, the "conversational" approach apparently ranks pretty badly. People can be good at BSing, reading the bold print etc.

And conversely, there are people who are not good at tech, but good at casual conversation about tech. Those people tend to become your boss :)

What types of interviewing styles rank well?

Would that not imply they aren't a good fit for the OP's workplace? And presumably, a lot of larger tech companies, since communication must be a large part of your job.

I am admittedly not good at talking on the fly if I haven't prepped for it. I try to make up for it by trying to focus on writing well.

Effective communication skills are also important.

IMHO, complaining about the status quo is easy and giving armchair hot takes about circumstances one does not understand is also easy. If one wants to play the smart game, there are some facts that can leverage to one's advantages:

1) job postings being above the fold vs long tail is a thing. There are tons of companies/roles you will never hear about from by perusing linkedin search.

2) following from that, interview criteria often needs to be adjusted based on various factors and plenty of companies have to make more streamlined funnels in order to have a fighting change of capturing any talent at all.

3) even for high visibility/demand companies, recruiters have incentives to think outside the box to find truly valuable talent, because these people are not even in the market for a new job, let alone willing to put up w/ bullshit. The catch that many people miss is that just accruing a high number of years of experience doesn't necessarily translate to being valuable, especially on the fast changing world of tech.

A recruiter without technical background will not be able to judge the answers other than „was able to form sentences“ or „couldn’t phrase anything“

Too many counter examples irl who had shit grades but were geniuses at actual work to discount.

Firstly because that's not their job, and secondly because recruiters aren't just there to hire for developers and they aren't going to be subject matter experts enough to judge between good answers to questions like that and bullshit.

Most companies I've interviewed at over the years (basically all but the smallest startups) have had dedicated recruiters for developers; different people hired sales or marketing or other roles. This doesn't mean that they should be expected to be technical experts, but I do think it's interesting that the box-checking type of interviews rather than just having a genuine conversation also seem to be more common the larger the company is. It's probably not surprising, since the need for standardizing interviews is higher when you have a larger number of people performing the interviews, but it's a little ironic that the most boilerplate interviews I've had were all with recruiters who specifically only interview developers.

Then again, I also tend to get bounced around to different recruiters far more frequently with the larger companies. There have been times I've been passed around to half a dozen recruiters within the span of a month or so; one makes the initial contact, then another talks to me on the phone, then another coordinates my technical interview schedule, and then another actually gives me the offer, who then refers me to one final other recruiter to actually respond yes or no (and maybe negotiate if possible). I know some of these are probably a more entry-level position that I've seen referred to as "recruiting coordinators" rather than full-fledged recruiters (meaning that they often handle the logistics like scheduling but don't perform interviews themselves), but it still feels absurd to have to talk to so many different people for basically the same thing. My impression is that it's somewhat intentionally trying to put me at a disadvantage by making it impossible for me to carry over any expectations from one step to the next (e.g. one recruiter might say something about compensation or benefits and then the next one conveniently doesn't know what I'm talking about and can claim that no one would have told me that).

YMMY, but I was once interviewed in this style days after Elon mentioned it's his go-to style of interviewing.

Was easily the worst, most pointless interview of my life.

As with everything, it probably depends on the person. A good interviewer can do almost anything and come away with a good signal. A bad interviewer can do the same thing and come away with noise.

The process is less important, I think.

Frequently experienced candidates with interview practice will simply ramble for many minutes - listing extensive contributions in excessive detail. Unfortunately when this happens it’s usually pretty awkward for everyone.

The ideal candidate will answer this question very gracefully and enable us to proceed directly into problem solving questions.

Gotta agree with your point about good/bad interviewers. I want to add that good interviewers/interviewees know how to manage the “risk” of such open-ended questions leading to a pointless interview.

The problem is, this initial funnels are just recruiters. They're technologically clueless. They're just putting words on paper and finding people that say those words with the right number of experience attached.

The real question is: Why don't the courts? Everything else is just to cover asses when the discrimination lawsuits appear.

If you need specific technical skills in React for an urgent project then retain a contractor or consultant, don't hire an employee.

Competent hiring managers look for folks with 10 years experience with React, C#, Java, DevOps, Embedded C++ Development, Mobile cross platform dev and ofc Rust for good measure, each.

We have long forgotten about doing one thing and doing it right.