DevOps IT Service Management (ITSM) Engineer

When a large organization needs to track how infrastructure changes move through approval processes, measure the SLA on incident resolution, and prove to an auditor that every production change was authorized, it needs ITSM infrastructure. When that same organization also wants to deploy software multiple times per day, those ITSM requirements need to be met without becoming a bottleneck. A DevOps ITSM Engineer's job is to solve both problems at once.

The change management challenge is the most characteristic of the role. Legacy ITIL change management assumed changes were rare, risky, and required human review of each one. Modern DevOps reframes change as frequent, well-tested, and automatable. The ITSM engineer designs the framework that reconciles these perspectives: defining which change types can be pre-authorized and deployed automatically, which require lightweight asynchronous approval, and which genuinely need CAB review. Getting that categorization right allows engineering teams to deploy without friction while maintaining the audit trail that compliance requires.

ServiceNow or Jira Service Management configuration is the technical foundation. These platforms are complex — workflows, approval logic, integration APIs, reporting dashboards, service catalog items. An ITSM engineer who can configure these platforms programmatically (through code, rather than only through GUIs) and integrate them with external systems via APIs is significantly more effective than one who can only work through the admin interface.

The integration layer is where DevOps principles apply most directly. A GitHub Actions workflow that creates a change record in ServiceNow on deployment, links it to the relevant Jira tickets, and marks it resolved on successful completion — built and maintained by code — is more reliable than a manual process and produces better audit data than manual entry.

Education:

• Bachelor's degree in information technology, computer science, or information systems
• ITIL certification is often more directly relevant than the degree in this role

Certifications (valued):

• ITIL 4 Foundation — widely required; table stakes for this role at most organizations
• ITIL 4 Managing Professional — valued for senior roles with process design scope
• ServiceNow Certified System Administrator (CSA) — required for ServiceNow-focused roles
• ServiceNow Certified Implementation Specialist — for roles implementing ServiceNow modules
• DORA DevOps Certificate — demonstrates understanding of DevOps integration with ITSM

Technical skills:

• ITSM platforms: ServiceNow (dominant at enterprises), Jira Service Management, Freshservice, Remedy
• ServiceNow development: workflows, business rules, script includes, Flow Designer, REST API integration
• API integration: connecting ITSM platforms to DevOps tools (GitHub, GitLab, PagerDuty, Datadog) via webhooks and REST
• Automation: scripting approvals, fulfillment workflows, and notification logic within ITSM platforms
• Reporting: building service desk dashboards, SLA reports, and change advisory board metrics
• Process design: change models, incident severity matrices, escalation paths, problem management workflows

Process knowledge:

• ITIL 4 service value system, value chain, and four dimensions
• Standard/normal/emergency change classification and associated workflows
• Problem management and known error database management
• Service request fulfillment design patterns

Experience benchmarks:

• Mid-level: 3–5 years in ITSM administration; has integrated ITSM with at least one DevOps tool
• Senior: 6+ years; has redesigned ITSM processes for DevOps compatibility; leads ITSM transformation programs

ITSM remains a significant function at mid-to-large enterprises, and the intersection with DevOps practices is creating demand for a distinct skill combination that relatively few practitioners have. Organizations that are advanced in DevOps delivery practices but still subject to regulated change management requirements need engineers who can bridge both worlds.

ServiceNow's dominant market position in enterprise ITSM, and its continued investment in AI, platform expansion, and developer tooling, means that ServiceNow expertise specifically is a career investment with strong market value. ServiceNow architects and senior developers consistently earn above the general ITSM engineering range.

The ITIL 4 framework's incorporation of DevOps, Agile, and Lean concepts has reduced the philosophical tension between ITSM and DevOps — a tension that previously made it difficult to discuss both in the same organization. ITIL 4-trained ITSM engineers who understand DevOps are better positioned to drive the integration work that mature organizations need.

AI features in ITSM platforms are shifting the work from manual configuration to training and evaluating AI behavior. Ticket routing models, AI-assisted change risk scoring, and self-service answer generation all require ITSM engineers who can assess AI output quality and calibrate platform settings. This adds a new skill requirement without eliminating the traditional configuration work.

Regulated industries show the strongest demand growth for this specialization. Financial services firms subject to SOX, DORA, and bank regulatory change management requirements, healthcare organizations under HIPAA, and government agencies under FISMA all need the auditability that ITSM provides alongside the delivery speed that DevOps enables. The combination is a durable market.

Career paths from this role include ITSM platform architect, IT service management director, and ServiceNow platform product management.

Dear Hiring Manager,

I'm applying for the DevOps ITSM Engineer position at [Company]. I've spent four years as the ITSM platform engineer at [Company], a financial services firm with stringent change management requirements and a development organization that was trying to move to continuous delivery.

The core challenge I was hired to solve was real: our change management process required CAB approval for every production deployment, which was meeting weekly, which meant development teams batched changes and deployed monthly. I redesigned the change model from scratch, working with compliance, the CAB, and engineering leadership. We defined three categories of standard changes — routine deployments meeting automated test criteria, infrastructure changes within pre-approved patterns, and hotfixes meeting specific criteria — and pre-authorized them for automated deployment without CAB review. Emergency and significant changes still go through review. Deployment frequency went from monthly to multiple times weekly within six months.

I did all of this in ServiceNow — configuring the change models, building the automated change record creation workflow integrated with our GitHub Actions pipelines, and setting up the approval routing for non-standard changes. I also built the compliance reporting dashboard that shows auditors exactly how many changes deployed in each category, which pre-approvals were invoked, and what evidence supports each category definition.

I hold ITIL 4 Managing Professional and ServiceNow CSA certifications. The combination of ITSM process knowledge and DevOps technical understanding is something I've built deliberately — it's a combination that seems rarer than it should be.

I'd welcome the opportunity to discuss how your organization currently handles the tension between change management governance and delivery velocity.

[Your Name]