You have to understand the context of the interviewers. The person may not have really cared. They probably weren't interviewing for their own team. They may have their head in the middle of some problem they are thinking about.
Google is hiring 10's of thousands of engineers a year. It's really hard to do well. Most of the questions are deliberately scripted because they are known to be good questions on some dimension.
So... work with them. Most of them actually want you to do well. Most of them are smart. Some of the questions are an open invitation to just talk and show that you can behave like someone they'd want to work with.
Your answer of "dinosaurs" etc, while the result of frustration more than anything, just said to the interviewer "not someone i want to work with".
In which case they should have teams dedicated purely to technical interviewing, with members regularly rotated in and out to keep them fresh.
When I did technical interviewing for my company for a period, granted it was still on top of my 'day job ' but I had the scope to get really invested in the process, and wrote guidelines for other reviewers. Treat technical interviewing as a respected role in its own right and not as a chore that interferes with 'real' work and it's a better outcome for all parties
That might well be a good idea. I can imagine downsides to it, but it might work.
The long and short of it is though - one has to face the reality of the situation they are in. If you go interview at Google (or any FAANG I would guess), you have to understand what you are in for and do your best to get through. Or, just don't interview there.
One company I interviewed at in late 2019 referred me to an interviewing-as-a-service. I forget the name, but the gist was that this service hired and interview-trained software engineers (at least part-time, maybe full-time) who then conducted interviews and provided feedback to the companies purchasing the interview-as-a-service.
From my perspective as a candidate, it was fine (the interviewer was friendly and asked industry-standard questions) but I do wonder how it goes for companies that essentially outsource their hiring bar.
On the other hand, you'd need to be doing a lot of hiring to make it worth dedicating a software engineer to just interviewing people. Or you have someone who doesn't really understand code—like a recruiter—run the interview, with all the difficulties that creates.
Google is hiring 10's of thousands of engineers a year. It's really hard to do well. Most of the questions are deliberately scripted because they are known to be good questions on some dimension.
So... work with them. Most of them actually want you to do well. Most of them are smart. Some of the questions are an open invitation to just talk and show that you can behave like someone they'd want to work with.
Your answer of "dinosaurs" etc, while the result of frustration more than anything, just said to the interviewer "not someone i want to work with".
It sucks, but you have to know your audience.