Lately there have been a lot of organizations trying to hire a DevOps engineer. I myself have been asked to fill in DevOps roles. There are a number of issues with that.
The biggest problem is that I always have to ask what exactly the organisation is looking for.
So you want a devops engineer with experience in Linux, MongoDB, MySQL and Java -- does that mean you want a Java developer who is familiar with MySQL and Linux and breathes a DevOps culture? Or a Linux expert who understands Java developers and knows how to tune Mongo and MySQL?
It's absolutely unclear what you want when you are hiring "a devops engineer."
The second problem is that you are trying to hire people who are knowledgeable about DevOps, yet a lot of those people know that you can't do devops on your own. DevOps is not a job title. DevOps is not a new team you create.
To some of them you are even making a fool out of yourself, showing them that you don't understand DevOps.
On top of this, the ones that do apply for this fancy new devops role are the ones that might not get the fact that the problem isn't about tooling but about people working together and helping each other, so you end up hiring the wrong people.
Even in today's devops culture a system engineer is still a system engineer, and a developer is still a developer. You might have developers supporting the build tool chain, or system engineers focussing on infrastructure automation. But as John said almost 3 years ago they are good at their job.
Devops is not a word you slap onto a tool, a team or a person and expect magic to happen.
Let's face it: devops is hard, you can't do this on your own. You need to find the right people.