IT Support Manager

The IT Support Manager leads the IT support operations and owns major incident management end to end. This person keeps day to day support running well, acts as the senior escalation point, and takes command when an incident impacts a client or our agents. They own the incident management process we recently launched and mature it from a new process into a dependable practice. This is a working manager role: you lead people and process, and you go deep in the technical detail when an incident demands it. Why this role exists:  Support and incident work currently escalates to a single point. This role takes ownership of that work, matures the incident process, and gives the team an escalation path and a leader of its own.   KEY DUTIES AND RESPONSIBILITIES IT Support Operations • Own IT support operations end to end: queue health, escalation, and service quality against SLA and CSAT targets. • Own IT asset and device lifecycle: procurement, provisioning, tracking, and retirement of endpoints and support hardware. • Own support tooling and vendor spend, including the budget line for support tools and partners, and surface spend decisions to IT leadership. • Deliver a regular SLA, CSAT, and incident reporting cadence to IT leadership, with trends and improvement actions. Major Incident Management • Own incident command, coordination, stakeholder communication, and resolution for Sev1 and Sev2 events across our environment. • Own the incident process: Jira intake, severity definitions, on-call and paging criteria, and enforcement. • Run post incident reviews for every major incident, with actions tracked to closure, and recurring issues identified and solved through problem management. Incident Command This is the part of the role that separates a strong hire from a queue manager. When an impacting outage occurs, you are the person who: • Declares the incident and takes the incident commander seat, or assigns it clearly. • Runs the bridge and drives the technical response without doing all the hands on work yourself. • Owns clear, timely stakeholder and client communication, kept separate from the person doing the fix. • Makes the call on severity, mitigation risk, maintenance windows, and resolution. • Runs post incident review with actions and named owners. People Leadership • Lead the support team: coaching, one on ones, growth, and performance. • Manage our managed support partner as an extension of the team. Coordination and Documentation • Coordinate with Cybersecurity and Rapid7 MDR during security incidents. • Coordinate with Professional Services, who own the contact center tooling, during incidents that involve it. • Own documentation and self service in Confluence so the team resolves more without escalating, and knowledge does not live in one head.   SYSTEMS AND SERVICES You do not need deep hands on expertise in every tool below. You do need enough fluency to command an incident that involves any of them and to know who owns what. The security tooling is owned by our security team and the contact center tooling by our professional services team; you coordinate with those teams during incidents rather than administering their tools. Domain                                Systems and services Identity & access                 Okta and SCIM, Microsoft Entra ID Endpoint & device              Microsoft Intune, Microsoft Defender suite, SentinelOne, Secure Remote Worker Collaboration & email         Google Workspace, Microsoft Exchange Online, Zoom, Slack Contact center & voice        Five9, Nextiva, NICE Cloud & infrastructure         AWS, Microsoft Azure, Google Cloud, GitHub ITSM & people ops               Jira, Jira Service Management, Confluence, Rippling Security operations              Rapid7 InsightI