hackajob
Service Governance, ITSM & Incident Lead - BPL
How your CV stacks up
Upload your CV to see how well it fits this job role
?%
Hackajob is collaborating with Barclays to connect them with exceptional professionals for this role.
Service Governance, ITSM & Incident Lead, BPL
Hackajob is collaborating with Barclays to connect them with exceptional professionals for this role.
About the Role
The Service Governance, ITSM & Incident Lead, BPL, is accountable for establishing and running the service-management control plane for BPL Technology Operations. The role will convert the Tech Ops operating model into practical Day 0 and Day 1+ ways of working across incident management, major incident command, problem management, change enablement, service catalogue, operational reporting, and service readiness. The role exists to make new BPL technology services safe to launch, clear to operate, and measurable once live, while avoiding the creation of a traditional “throw it over the wall” operations silo.
Working as part of the Technology Operations leadership capability, the role will partner closely with Engineering, Product, Customer Operations, CISO, Controls, GTSM / TC07, suppliers, and the wider BPL transformation programme. Engineering remains accountable for production ownership under a “you build it, you run it” model; this role provides the governance, orchestration, standards, reporting, and command structure that enables services to operate reliably at scale.
Organisational Context
BPL is building a lean, AI-first, and service-led Technology Operations capability to support the Gaia programme, Q3 MVP launches, and the progressive transition from current Barclays / TC07 operating arrangements to a standalone BPL service model. Tech Ops is intended to act as the horizontal operational backbone across internal teams, product value streams, and provider-delivered services. Its focus is reliability, operability, resilience, and control — not feature delivery.
The immediate priority is to make the Next Generation Gateway, Service Portal, and associated launch capabilities safe to run at Day 0, with clear ownership, operational readiness gates, service hand-offs, incident command, tooling routes, controls evidence, and reporting in place. Over time, the role will mature this into a repeatable, scalable service model across BPL services, integrating ITSM, AIOps, service reporting, SLOs, problem management, resilience, and supplier operations into a single operating loop.
Scope
The role owns the design, implementation, and ongoing operation of the core service-governance layer across Technology Operations. This includes ITSM processes, major incident command, service catalogue and ownership model, change enablement governance, operational readiness, service reporting, knowledge management, problem management, and the service-management interfaces with Engineering, Customer Operations, suppliers, CISO, Controls, and legacy / TC07 teams.
The role does not own product delivery, application development, engineering backlogs, vulnerability management, security policy, customer-service tooling, or traditional eyes-on-glass monitoring. It is accountable for ensuring that the operational process, governance, escalation, evidence, and reporting model is clear, adopted, and effective across those delivery and support boundaries.
Key Accountabilities
- Establish and operate the BPL ITSM framework across incident, major incident, problem, change enablement, request, knowledge, and service catalogue processes, ensuring the model is pragmatic, lean, and appropriate for a fintech-scale organisation.
- Lead the major incident management capability, including incident command, war-room execution, escalation paths, communications routines, post-incident review, and follow-through on systemic actions.
- Define the service catalogue, ownership model, and service criticality approach, ensuring every launch service has clear service ownership, support boundaries, routing, on-call / escalation arrangements, runbooks, and readiness evidence.
- Shape change enablement governance for BPL services, balancing control and speed through risk-based change thresholds, standard change patterns, release readiness, rollback criteria, audit evidence, and alignment to Barclays control requirements where applicable.
- Drive problem management and continuous improvement, ensuring recurring incidents, service instability, and launch learnings are converted into accountable actions, engineering backlogs, service improvements, and measurable reduction in repeat failure demand.
- Own operational readiness criteria for Day 0 launches, including runbooks, service records, escalation contacts, tooling routes, monitoring / signal inputs, customer and supplier hand-offs, comms routes, controls evidence, and go / no-go support.
- Develop service reporting and executive MI across incidents, service performance, SLAs / KPIs, SLOs, DORA indicators where relevant, change performance, control posture, resilience readiness, risk, decisions, and operational confidence.
- Partner with SRE, Platform, Engineering, and AIOps capabilities to improve alert quality, incident detection, event correlation, automation, toil reduction, operational telemetry, and post-incident learning without diluting engineering accountability.
- Manage service-governance interfaces with suppliers and legacy service providers, ensuring clear escalation models, support obligations, operational hand-offs, evidence expectations, and transition readiness gates as capabilities move towards the BPL target model.
- Build a practical service-management culture across BPL Technology Operations: clear ownership, blameless learning, data-led prioritisation, automation before headcount, strong control evidence, and concise senior stakeholder communication.
Reasons to use Rodeo
Start with a chat, not a search bar
Grad scheme, placement, apprenticeship? Not sure what you want yet — that's fine. Your agent talks it through with you and turns "I have no idea" into a shortlist.
It searches the market for you
Every day your agent scans the market matching roles against what actually matters to you, not just keywords on a CV.
Only hits
No noise. No "maybe this fits." Just roles with a clear explanation of why they're right — and where to focus when applying.
Key Responsibilities
- Translate the Tech Ops operating model into executable service-management processes, role clarity, RACI / ownership maps, governance routines, workflow requirements, and adoption artefacts.
- Stand up the Day 0 incident model for launch services, including named incident roles, severity definitions, escalation triggers, war-room protocols, communications templates, decision logs, and post-incident review process.
- Work with Engineering and Platform teams to define minimum operational readiness requirements for each service, including observability, alerting, ownership, runbooks, rollback, support coverage, and service-level expectations.
- Configure and continuously improve the service-management operating model across Jira Service Management or agreed tooling, ensuring workflow design supports routing, evidence capture, reporting, and scale.
- Establish a lightweight service catalogue / CMDB-lite approach covering service owner, technical owner, criticality, dependencies, support model, supplier interfaces, and operational evidence requirements.
- Lead operational engagement for launches and transitions, ensuring product, engineering, customer operations, support, supplier, and control teams understand how services will run once live.
- Produce concise, senior-ready updates on launch readiness, service risk, incident trends, operational decisions, control posture, and confidence to proceed.
Key Deliverables
- Day 0 service-governance model for launch services, including incident, problem, change, request, knowledge, service catalogue, and reporting processes.
- Major incident management playbook, covering command model, severity levels, escalation, communications, decision logging, post-incident review, and action tracking.
- Operational readiness checklist and evidence pack for each launch service, aligned to go / no-go decisions and Day 1+ stabilisation.
- Service catalogue / CMDB-lite baseline with clear ownership, criticality, dependencies, routing, on-call / escalation contacts, and support boundaries.
- Service reporting pack covering incidents, MTTR, repeat incidents, change performance, service health, SLA / KPI performance, operational risks, controls evidence, and decisions required.
- Day 1+ service maturity roadmap showing how the model evolves from people-led launch control to a standardised, tool-assisted, and AI-enabled cross-provider service model.
Get help with your application
Your very own career expert that helps elevate your application to the next level.
Candidate Profile
The successful candidate will be an experienced service-management and technology-operations leader with a strong track record of standing up or materially improving ITSM, incident management, and operational governance in complex, regulated technology environments. They will be comfortable operating hands-on in an immature / build environment while also creating the repeatable standards, artefacts, and routines required for scale.
They must be able to lead calmly during major incidents, create clarity across ambiguous ownership boundaries, challenge over-heavy process where it slows delivery, and build credibility with engineering, product, customer operations, supplier, and executive stakeholders. The role requires strong judgement: enough control to protect service reliability and regulatory confidence, without importing unnecessary legacy process overhead.
Essential Knowledge, Skills And Experience
- Significant experience in IT service management, service operations, or technology operations within a complex fintech, payments, payment acquiring company.
- Proven experience leading major incident management, incident command, crisis coordination, stakeholder communications, and post-incident improvement in high-availability services.
- Strong practical knowledge of ITSM processes, including incident, problem, change, request, knowledge, service catalogue, SLA / KPI management, and operational reporting.
- Experience designing or improving service-management tooling and workflows, ideally including Jira Service Management, ServiceNow, or equivalent ITSM platforms.
- Ability to define operational readiness criteria, service runbooks, escalation models, support boundaries, service-level expectations, and evidence packs for technology launches.
- Strong understanding of SRE, observability, alert hygiene, service ownership, SLOs, error budgets, postmortems, and automation-led service improvement.
- Experience working across engineering, product, customer operations, suppliers, control teams, and senior technology leadership to resolve ambiguity and drive adoption.
- Excellent written and verbal communication skills, with the ability to produce clear executive-ready updates, incident communications, decision papers, and service-readiness reporting.
- Experience in merchant acquiring, payments, gateway, servicing portal, digital channels, or high-volume transaction-processing environments.
- Familiarity with operational resilience, business continuity, disaster recovery, technology controls, audit evidence, and regulated outsourcing / supplier management expectations.
- Experience operating in a carve-out, new-entity build, platform migration, service transition, or large-scale transformation environment.
- Understanding of AIOps, event correlation, service telemetry, automated evidence capture, and AI-enabled service-management patterns.
“It took my CV and asked me questions relevant to understanding what kind of jobs to suggest for me. Suggestions were almost perfect. Jobs were exactly what I’ve been looking for.”
Jessica, London
Skills
Location