I feel this is why leetcode rules the roost in the tech industry. Maybe it used to be more about the "approach to the problem and the way the candidate communicates his/her/their thought process", but even when I'm interviewing I have a hard time convincing the others in the panel when the candidate does not present the exact solution even if it is clear they can code and are able to understand the problem.
So what started as a way for a team to gauge the abilities of the candidate and more importantly if the candidate will play well in the team is now an examination with right/wrong answers supplemented by a half-assed "behavioral" interview with some canned questions.
I've read the interview guides at some of my past organizations. The total outcome of the behavioural questions was essentially making sure they were not an ass. Interviewers frequently did not bother to write anything down for them.
Everything else hinged on the leetcode/Java or Python trivia.
So what started as a way for a team to gauge the abilities of the candidate and more importantly if the candidate will play well in the team is now an examination with right/wrong answers supplemented by a half-assed "behavioral" interview with some canned questions.