I agree with pjmlp, it's become a substitute for actually interviewing/evaluating the candidate. Especially if they are trying to hire for something they don't already have, it's a form of bikeshedding. For example, if they need a database expert because the team has been faking it until this point, they can either learn how to hire one, or they can focus on brain teasers and "culture fit", and feel good that whether or not the person is expert, they passed the test.

Ideal would be if the questions are actually job related, how many other professions do you think get these kind of stupid questions?

Since we are it, lets make Jeopardy for getting a job.

Companies are groups of people behaving a certain way, and jobs are behaving that way. As an outsider, you don't know what the job is. If the interview is a bunch of questions you think is stupid, then the job is probably doing a bunch of stuff you think is stupid. If you want the money and prestige anyway, then learn to do the stupid stuff.

Which is why, as mentioned, unless I am desperate for a job, I walk out.

Or maybe the job is about actually carrying golf balls into planes.

I bet it is about solving the daily brain teaser of working with unmaintainable code!

I thought we had Fable for that now.

So if somebody tried to solve the brainteaser with an impossibly high likelihood of being completely wrong. You get the signal that their values match yours, they are open minded and that they are good at writing great programs?

I do understand that these are stupid ways to achieve that goal.

Again, I’m not saying that job related questions are bad. I’m saying that these types of questions can be good. You can ask more than 1 type of question!

Mostly of the same basket and equally bad, on my experience, because usually it is some dude or gal, that rather be coding than doing interviews that gets dragged to question this guy that just dropped on reception for the interview.