> Markdown version of [/jobs/ext/3665199-it-service-management-lead](https://www.wearedevelopers.com/jobs/ext/3665199-it-service-management-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# IT Service Management Lead

- **Company:** Hargreaves Lansdown
- **Location:** Bristol, UK
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Software as a Service, Cloud Computing, Configuration Management, System Configuration, Servicenow
- **Published:** October 10, 2026
- **Apply:** https://www.totaljobs.com/job/service-management-lead/hargreaves-lansdown-job108122176

## About the Role

* Has led an ITSM process or service management team in a complex environment with several platforms.
 * Has owned major incident management, including keeping the business informed under pressure.
 * Knows ITIL 4 practices across Incident, Problem, Change and Release, Knowledge, and Service Configuration Management.
 * Has worked in a regulated environment and given control evidence to risk and audit.
 * Has defined process requirements for an enterprise ITSM platform, ideally ServiceNow.
 * Has held internal teams and third-party and SaaS suppliers to process, including teams outside their line management.
 * Uses data and metrics to make decisions.

Desirable

 * ITIL 4 Managing Professional or Strategic Leader.
 * Working knowledge of ISO/IEC 20000-1 and its audit requirements.
 * Experience of operational resilience rules in financial services.

## Description

The IT Service Management Lead owns the IT service management practice across IT Service Operations and must show that it works. The role leads the Service Management team, sets how incident, problem, change and release, knowledge and configuration management are run, and gives risk, audit, and the regulator evidence that service controls are working.

The role owns the processes, and the Service Management team runs them day to day: coordinating major incidents, running change approval, leading problem investigations, and keeping configuration data accurate. Cloud Operations, Application Support, and the engineering teams run and support the services themselves. The job is making that split work in practice across heritage, cloud-native and SaaS platforms.

What you'll be doing

 * The Service Management team. Its capability, performance, and resilience, so the practice holds up reliably.
 * Fit-for-purpose ITSM processes. Incident, Problem, Change and Release, Knowledge, and Service Asset and Configuration Management work as designed, apply the same way across heritage, cloud-native and SaaS platforms, and are codified in the ITSM platform. The teams that use them understand why they matter and see regularly how they are performing with this role as the processes' visible champion and SME
 * Major incident response. The business is kept informed during major incidents, and every one leads to a review with actions that get closed.
 * Fewer repeat incidents. The causes of recurring incidents are found and removed, and what's learned is captured as knowledge that support teams reuse.
 * Safe change. Change and release risk is understood and controlled before changes go live, and outcomes are reviewed after.
 * Trusted configuration data. Configuration and asset data is accurate enough for incident, change and risk decisions to rely on it.
 * Evidenced controls. Service management controls can be evidenced to risk, audit and the regulator at any time; audit findings get fixed, and both internal teams and suppliers follow the process.
 * A practice that improves. KPIs give leadership an honest view of service stability, and the improvement roadmap delivers measurable progress against the maturity baseline.
 * Clear responsibilities. An agreed split of responsibilities with all stakeholders, which everyone works to.