In my experience, that is completely different. If you interview for a DevOps role, you will be asked a laundry list of programs like Puppet, Chef, Ansible, Bamboo, Jenkins, TeamCity, Vagrant, Terraform, Saltstack, Kubernates, Katello, Foreman, and Rake. If you don't know one of those programs (say you know the ins and outs of GitHub Enterprise, but not BitBucket), the interview stops -right there-, you are shown the door, and they call for the next candidate.
*sigh* - it's a troll, but I'm currently waiting for something, so...
I can count only a few companies that interview that way, and you're right... the interview would stop right there, because *I* would walk out of it, telling them in so many kind words to go fuck themselves on my way out. What you described is a laundry-lister, and any company which still (in this century!) interviews like that is either going to hire an incompetent or a liar.
Let me explain for the studio audience why your premise is bullshit and pick through a few of these: Puppet/Chef(or cfengine)/Salt are similar enough that finding experience in one means you can quickly train your candidate in the others at very little cost if they have the skills/drive to learn them. Bamboo/Jenkins/TeamCity? Same-same (though SCM tasks are more and more being automated into oblivion, handed off to the dev teams to do their own housekeeping, or still run by a dedicated team as a service to the devs). Few folks use Foreman anymore (you get what you pay for, no?), Kubernetes (- note proper spelling) is primarily for Docker (which curiously you did not mention), and Fleet (which you also did not list) still competes with it. You only list one language of sorts, and it's an extension set to Ruby, which you did not list. You also left out service discovery (e.g. Consul), process security (e.g. Vault, also a Hashicorp product), and totally left out deployment methodologies (though you did casually mention CI/CD), which is fucking *primary* if you want to fit into a new company (e.g. a company that is still religious about gitflow isn't going to cotton so well towards the GitHub feature/master branching model). Also left out are process methodologies, which often are akin to religion in the dev world.
TL;DR, you have no idea how this whole thing works, do you?