You have DEVops... think of a web developer who also knows linux.
Then you have devOPS... think of a sysadmin who knows bash and python.
The former is where I think the value comes.. they find ways to automate your infrastructure and do lots of cool things. The later tend to make webs of bash scripts that you have to delete when they quit because no one understands them.
All that because the webdev was learning new Csharp.JS framework like dozen before, being too busy to learn how package system or daemonization or networking or RPC or SSH or push vs. pull architectures worked and what they are good at, or what tools and why a seasoned sysadmin uses for automation.
What you really need is not a dilletante armed with sharp and pointy PHP-du-jour, but a system programmer. There used to be such a profession, the guys who wrote syslog, init, bash, grep, awk, libnss, and tons of other goods people today either use without much thinking or don't know existence of at all.
Maybe it's good vs bad but it happens. In the puppet/chef era I'd have said you needed to have a background in coding to be a good devop, but ansible has changed that now I think.