While I'd argue that any good developer should have more than a passing understanding and empathy for operations, what is being described here is not DevOps. Let's steal a definition from Wikipedia: DevOps (a portmanteau of development and operations) is a software development method that stresses communication, collaboration and integration between software developers and information technology (IT) operations professionals. DevOps is a response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services.
DevOps is NOT A ROLE. DevOps is a methodology concerning increased communications between development and operations. For example, DevOps tools may help coordinate software releases across environments -- e.g., helping to ensure that the same software is deployed in the same way in Dev, QA and Production, thereby avoiding potential issues created due to different configurations or dependency combinations. Going the other way, a system monitoring tool which collects information on software failures may be augmented so that IT can choose to collect more detailed information (e.g. stack traces or memory dumps) and have all of that data attached to a bug report published into the developers' bug tracking system. Analytics are a growing area of interest in DevOps, facilitating the collection and consolidation of product and feature usage, making that available in a consumable format for business analysts.
That's what DevOps is in an established organization. It's a Really Good Thing, and once you've experienced it, it's hard to work anywhere that doesn't take DevOps seriously.