Skip to main content
JobDescription.orgSearch

Information Technology

IT Service Manager II Job Description

An IT Service Manager II owns the end-to-end delivery of IT services to internal or external customers — managing incident queues, enforcing SLA compliance, running change advisory processes, and aligning service desk operations with business expectations. They sit between technical teams and the business stakeholders who depend on those services, translating operational metrics into decisions that affect uptime, user satisfaction, and IT budget performance.

Last updated

Role at a glance

Typical education
Bachelor's degree in IS, CS, or Business Administration or equivalent experience
Typical experience
4-7 years
Key certifications
ITIL 4 Foundation, ITIL 4 Managing Professional, PMP, ServiceNow CSA
Top employer types
Large enterprises, Managed Service Providers (MSPs), SaaS vendors, IT consulting firms
Growth outlook
Steady demand driven by increasing enterprise complexity in hybrid and multi-cloud environments
AI impact (through 2030)
Augmentation — AI-assisted triage and automated resolution compress lower-tier roles, but increase demand for managers to govern automation logic and manage complex exceptions.

Duties and responsibilities

  • Own SLA compliance across incident, problem, and change management processes, reporting weekly metrics to IT leadership and business stakeholders
  • Manage escalated P1 and P2 incidents end-to-end — coordinate bridge calls, drive technical resolution, and produce post-incident reviews within 48 hours
  • Facilitate weekly Change Advisory Board (CAB) meetings, reviewing RFC submissions for risk, impact, and scheduling conflicts before approval
  • Develop and maintain service catalog entries, ensuring accurate service descriptions, ownership assignments, and fulfillment SLAs for each offering
  • Analyze ticket trend data and repeat incident patterns to identify problem candidates and submit problem records for root cause investigation
  • Manage vendor performance against contracted OLAs — track SLA credits, run quarterly business reviews, and escalate persistent misses to contract owners
  • Build and maintain operational runbooks, escalation matrices, and knowledge base articles that reduce mean time to resolve across the service desk
  • Lead service improvement initiatives using CSI register tracking, documenting baselines, targets, corrective actions, and outcome measurements
  • Conduct monthly SLA review meetings with business unit leads, presenting incident volume trends, unresolved problems, and planned service changes
  • Mentor junior service desk analysts and team leads on ITIL process discipline, ticket hygiene, and customer communication standards

Overview

An IT Service Manager II is the operational owner of service quality — not the person fixing the server, but the person accountable for whether the server was fixed within SLA, whether the right people were notified, whether the root cause was properly investigated, and whether the next outage of the same type gets prevented.

In practice, the role is split across reactive and proactive work. On the reactive side: when a critical application goes down, the IT Service Manager II opens the major incident process, bridges the right resolver groups, owns the communication cadence to affected business units, drives toward resolution, and closes the incident with a post-incident review that identifies what actually failed and what needs to change. None of that requires knowing how to code or configure the failed system — it requires knowing how to run a structured, time-pressured coordination process without losing track of the stakeholder communication thread.

On the proactive side: reviewing ticket trend data weekly to spot repeat incidents that should be promoted to problem records, running the Change Advisory Board to ensure that planned changes don't introduce new risk without review, maintaining the service catalog so users know what IT actually offers and how to request it, and tracking service improvement initiatives against committed baselines.

Vendor management is increasingly central to the role. Most enterprise IT organizations have outsourced significant service delivery — managed service providers, SaaS vendors, hardware maintenance contracts. The IT Service Manager II is often the person who holds vendors accountable to OLAs, runs quarterly business reviews, and decides whether a persistent SLA miss warrants escalation to the contract owner.

The role demands a particular combination of skills: process discipline, data fluency, and the ability to communicate clearly under pressure to both technical teams and business executives. The people who thrive are typically organized thinkers who can absorb a complex operational situation quickly and start asking the right questions — not the people who need to personally solve every problem.

Qualifications

Education:

  • Bachelor's degree in information systems, computer science, or business administration (standard expectation at most enterprise employers)
  • Equivalent experience accepted at many organizations, particularly if ITIL certifications are current
  • MBA or graduate work in technology management is present at the director level but uncommon at Service Manager II

Certifications — baseline:

  • ITIL 4 Foundation (table stakes at most organizations; candidates without it are frequently screened out)
  • ITIL 4 Managing Professional designation (strong differentiator for Level II roles)
  • PMP or CAPM (common at organizations where service management and project delivery overlap)

Certifications — supplemental:

  • HDI Support Center Manager (service desk-heavy environments)
  • ServiceNow Certified System Administrator (CSA) or Certified Implementation Specialist (ITSM module)
  • Six Sigma Green Belt for organizations using process improvement frameworks alongside ITIL

Platform experience:

  • ServiceNow: workflow configuration, SLA policy setup, report and dashboard creation, CMDB hygiene
  • Jira Service Management: project configuration, SLA schemes, queue management
  • BMC Helix or Ivanti (legacy enterprise environments)
  • SIEM and monitoring platforms for major incident awareness: Splunk, Dynatrace, PagerDuty

Experience benchmarks:

  • 4–7 years in IT service delivery, with at least 2 years in a process owner or service management role
  • Documented experience managing P1/P2 incidents with business-facing communication responsibility
  • Experience presenting SLA reports and service reviews to non-technical stakeholders
  • Vendor management or contract performance tracking experience strongly preferred

Soft skills that differentiate:

  • Communication under pressure — the ability to deliver a clear, accurate status update to a VP at minute 15 of a major incident
  • Data interpretation — reading metric trends and surfacing actionable conclusions, not just charts
  • Process persuasion — getting resolver teams to follow change and incident processes without formal authority over them

Career outlook

IT service management is a mature discipline, and the IT Service Manager II role reflects that maturity: demand is steady, the credential and experience bar is well-defined, and compensation is predictable. It is not a role that will triple in headcount overnight, but it is also not one at risk of disappearing.

Several structural factors are keeping demand healthy. Enterprise IT environments are getting more complex — hybrid infrastructure, multi-cloud deployments, SaaS sprawl, and distributed workforces all generate more service dependencies and more potential failure points. Each added dependency is another thing that can go wrong and another thing that needs to be managed, documented, and governed. Organizations that underinvest in service management feel it in SLA misses, repeat outages, and change-related incidents that erode trust between IT and the business.

The AI and automation wave is reshaping the role rather than eliminating it. Tier 1 service desk positions are being compressed by AI-assisted triage, chatbots, and automated resolution of common request types. The IT Service Manager II sits above that compression — governing the tools, analyzing outcomes, and managing the exception queues that automation doesn't handle. Organizations that implement these tools well need managers who understand both the process side and the configuration logic of the platforms. That intersection is currently undersupplied.

Career progression from IT Service Manager II typically runs toward IT Service Management Director, IT Operations Manager, or ITSM Platform Product Owner. Some move laterally into IT program management or vendor management director roles. The ITIL Managing Professional to ITIL Strategic Leader path supports advancement into senior service strategy and governance positions at large enterprises.

Geographically, the strongest markets are major metro areas with high enterprise IT concentration — New York, Chicago, Dallas, Atlanta, and the Bay Area — but remote and hybrid arrangements are common for this role, which has expanded the competitive pool in both directions. Strong candidates can access opportunities in higher-paying markets from lower cost-of-living locations, and employers can recruit from a national pool for mid-tier positions.

For candidates currently at Service Manager I or Help Desk Manager level, the move to Level II requires demonstrating cross-process ownership, SLA accountability experience, and comfort presenting to business stakeholders. That transition is the most common bottleneck — many managers are comfortable in the service desk environment but haven't built the change and problem management exposure that Level II roles expect.

Sample cover letter

Dear Hiring Manager,

I'm applying for the IT Service Manager II position at [Company]. I've spent six years in IT service delivery, the last three as a service management process owner at [Company] — a 4,500-employee financial services firm running ServiceNow as our primary ITSM platform.

In that role I owned incident, problem, and change management processes across a 12-person service desk and four resolver groups. I ran the CAB weekly, managed major incident response for P1 and P2 events, and presented monthly SLA reports to the CIO and three business unit heads. When I took over the change process, we were closing roughly 30% of RFCs without proper post-implementation review. Eighteen months later that number was under 5%, which we tracked through a ServiceNow report I built specifically to surface that gap.

The piece of service management I find most useful in practice is post-incident reviews done honestly. At my current organization we had a recurring issue with our core banking integration — five incidents in eight months, each closed as resolved, none promoted to a problem record. I pushed to open a problem, tracked it through root cause analysis, and the fix was a configuration change that took two hours. The incidents stopped. The process exists for exactly that reason, and the discipline to use it when teams are busy is where most service management programs fall short.

I hold ITIL 4 Managing Professional and ServiceNow CSA certifications and I'm comfortable presenting operational data to non-technical executives in terms of business impact rather than technical detail.

I'd welcome the opportunity to discuss how my background aligns with what your team needs.

[Your Name]

Frequently asked questions

What does an IT Service Manager II do?
An IT Service Manager II owns the end-to-end delivery of IT services to internal or external customers — managing incident queues, enforcing SLA compliance, running change advisory processes, and aligning service desk operations with business expectations. They sit between technical teams and the business stakeholders who depend on those services, translating operational metrics into decisions that affect uptime, user satisfaction, and IT budget performance.
What are the main duties of an IT Service Manager II?
Core duties include: own SLA compliance across incident, problem, and change management processes, reporting weekly metrics to IT leadership and business stakeholders; manage escalated P1 and P2 incidents end-to-end — coordinate bridge calls, drive technical resolution, and produce post-incident reviews within 48 hours; and facilitate weekly Change Advisory Board (CAB) meetings, reviewing RFC submissions for risk, impact, and scheduling conflicts before approval.
What separates an IT Service Manager II from a Service Manager I or a Help Desk Manager?
A Level I typically supervises a single team — the service desk — and focuses on queue management and analyst performance. An IT Service Manager II operates across the full ITSM process stack: incident, problem, change, and service catalog management, often without direct supervisory authority over every team involved. Help Desk Managers focus on people management; IT Service Manager II roles focus on process governance and SLA accountability across multiple teams and vendors.
Is ITIL certification required for this role?
ITIL 4 Foundation is effectively a baseline expectation at most organizations; candidates without it are frequently filtered before interview. ITIL 4 Managing Professional — which covers Create, Deliver and Support, Drive Stakeholder Value, and High-Velocity IT — is a meaningful differentiator for Level II roles. PMP or ScrumMaster credentials are occasionally listed as requirements at companies running IT projects through the same manager.
How is AI and automation changing IT service management in 2026?
AI-driven service desks — using large language models for ticket triage, auto-categorization, and first-contact resolution — are reducing L1 ticket volume by 20–40% at early-adopter organizations. IT Service Managers increasingly govern these tools rather than just people: setting routing logic, reviewing deflection rates, and auditing automated responses for accuracy. The role is shifting from queue supervisor to service quality engineer, with more time spent on analytics and process design.
What ITSM platforms should an IT Service Manager II know?
ServiceNow is the market-dominant platform and familiarity with it is close to mandatory at enterprise employers. Jira Service Management is common at DevOps-oriented organizations and mid-market companies. BMC Helix and Ivanti are present in large legacy enterprise and government environments. Knowing how to configure workflows and reports — not just submit tickets — is what distinguishes candidates who can operate effectively from day one.
What are the most common reasons IT Service Managers II fail in the role?
The two most frequent failure modes are over-reliance on technical problem-solving rather than process governance, and poor stakeholder communication during major incidents. Effective IT Service Managers know when to stop troubleshooting alongside engineers and start managing the communication stream. Business stakeholders tolerate outages; they don't tolerate silence or status updates that describe technology instead of business impact.

Related job descriptions

See all Information Technology jobs →