I'm not sure I got the question correctly, but @chilimatic has a very good point: in many (most?) companies, DevOps is a buzzword but not real. I mean, HR realized that DevOps had much more traction than Sysadmin, so they just replaced sysadmin in their job posts.... but from what I see here the majority of 'DevOps' jobs are in fact sysadmin ones, with only ops and no dev.
When you want to hire a devops so that the engineers don't have to care about the ops, you got it wrong. DevOps is a philosophy first. You need a leader/heo/guru/whatever to lead that mutation/philosophy change, but doing devops can only be done if all the dev side is taking ops into account (I'm not saying they should manage the ops, but they should care about it.
True devops is achieved when the ops side (alerts, incidents, ...) in handled by specialized software engineers that also master the ops side (the real devops job), and when the software development is done by people understanding (at least the big picture) and taking care of the ops side (how will my software be run, what's the underlying infra, how is the system discovery working)
As long as it's used as a sysdamin-recruitement buzzword to hire a sysadmin to do the ops while the engineers to the dev, it will be nothing more than a buzzword. But some places got it right and really try to move forward and increase their velocity and resiliency by adopting - as a team - the philosophy.