Understanding DevOps as an Interface, Not a Job Role

Job titles usually define the tasks a person is expected to perform. A "software developer" develops software, a "system administrator" manages systems, and a "team lead" leads a team. Their performance can be evaluated based on the quality of task execution.

DevOps is different. DevOps is a way for a group of people with varied roles, skills, and responsibilities to work together toward common goals.

Unlike a "software developer", "system administrator", or "team lead", a "DevOps engineer" does not have a clearly defined set of tasks.

Do not imagine DevOps as the duties of a specific class of engineer; instead, think of DevOps as an interface implemented by many different types of engineers and other departments (senior leadership, marketing, information security, etc.) within an organization.

The idea can be expressed as follows:

/*
DevOps != Job
DevOps == Interface
*/
class DevOpsEngineer extends Job {
  // protocol + !directive
}
class Developer extends Job {
  // directive + !protocol
}
interface DevOps {
  // protocol
}
class Developer extends Job implements DevOps {
  // directive + protocol
}

This is a technical way of expressing the concept.

About the author: Ze Yang, a DevOps practitioner focusing on enterprise‑level DevOps operations and development, offers practical courses based on real‑world experience. The courses emphasize new Linux operations techniques and DevOps technology, aiming to provide useful skills recognized by many learners.