Incident and Problem Manager
-
IT/Tech
Job Description & How to Apply Below
The Incident and Problem Manager owns restoration and prevention: coordinating major incidents to resolution, running post-incident reviews, and managing problems through root cause analysis, known errors and permanent fixes. They report incident trends and problem backlog to IT leadership.
What you ownThe Incident and Problem Manager owns restoration and prevention: coordinating major incidents to resolution, running post-incident reviews, and managing problems through root cause analysis, known errors and permanent fixes.
- Coordinate major incidents and communications to resolution
- Own the incident process, priorities and escalation
- Run post-incident reviews and track actions
- Manage problem records, root cause analysis and known errors
- Drive permanent fixes through change
- Report incident trends and problem backlog
Who this role reports to, who reports to them, and the peers they work with most.
Reports to- IT Service Manager
- Service Desk Manager
- Change and Release Manager
- Security Operations Manager
- IT Operations Director
The Incident and Problem Manager owns restoration and prevention, and the IT Service Manager, business customers and regulators with staged reporting deadlines expect a clear record of every major incident. Smart Suite keeps one timeline from alert to permanent fix, so coordination, communication and root cause analysis live in the same record instead of three tools.
Own the incident process from priority to review Priorities and escalation rules applied consistentlyStandardized categories, priorities, ownership and queues mean a P1 is a P1 on every shift, and the escalation path you defined fires automatically on category and urgency rather than on who happens to be on duty.
Stakeholder updates from the incident recordReal-time status communication keeps affected users, the Service Desk Manager and leadership informed from the same incident record, so the bridge call is spent on restoration rather than on repeating where things stand.
Post-incident actions that do not evaporateEach post-incident review produces actions with owners and due dates tracked in the same workspace, so the improvements agreed after a major incident are followed through rather than filed with the report.
Stay connected to the service desk, change and security The pattern behind repeat ticketsProblem Management links repeat incidents to a single root cause and known error, so the Service Desk Manager's analysts see the workaround on the ticket and you see the pattern building rather than another isolated ticket.
SLA breaches visible before they happenSLA and OLA enforcement tracks response and resolution clocks with escalations, so a ticket approaching breach reaches you and the Service Desk Manager while there is still time to act on it.
Security incidents and outages on one recordWhen the Security Operations Manager's incident is also an outage, one record holds both work streams with shared tasks and one timeline, so containment and restoration do not run on separate clocks.
Show IT leadership the trend, not the ticket An audit-ready incident timelineEvery action, decision and approval on a major incident is recorded with its timestamp, so the staged reports DORA and NIS2 require, or an internal review, come from the record rather than from memory.
Reliability trends that justify the fixContinuous improvement insights analyze incident trends over time, so when you ask the IT Service Manager to fund a permanent fix the case rests on recurrence data rather than on the last bad week.
Knowledge articles born from known errorsKnown errors and workarounds feed Knowledge…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction