Let's sit down at a specific problem I am working on. Let me tell you what I'm doing with the tools that I have. Your past work was in some way similar, and you can relate to what I'm doing in some way. Either you can jump right in and take over the keyboard, or you can tell me how you solved a similar problem with your tools and frameworks. I can show you how it's done with my setup, and teach you a few things in the process - which you will easily pick up as you have related experience. You got either questions that are exciting, maybe challenging me how I am doing it, or maybe teach me just a keyboard shortcut I didn't know, proving the time and effort you spent on this. We are both excited to learn a lot in a short amount of time and I know I want you to work with us...
Here is what I think are some important skills in data science:
Can you understand the principles behind existing solutions and build a new solution from those principles?
(How fast) can you understand a new approach and apply it to a problem?
How long does it take you to translate a solution to working code? How optimal, readable and reusable is it?
Looking at your list of important skills in data science it seems we mostly agree on what is important...
It's far easier for the interviewer and the interviewee. Instead, it's all about covering yourself as the interviewer so you adopt the new garbage industry standard and pretend those are sound metrics. When the metrics are not that telling if a new hire is bad, you have an out that it's the process, not your mistake.
The problem is that the exact skills required for a job cannot be measured within the timespan of an interview, so instead closely related skills are measured. Until somebody solves this problem interview preparation makes a lot of sense.