Advanced Specialist , Technology Delivery

Role: Advanced Specialist, Technology Delivery

Location: Bengaluru, India - Hybrid (3 days in office per week)

We are looking for an experienced Technology Delivery Manager to drive the delivery, coordination and operationalization of Pearson's Observability Engineering and Command Center/NOC capabilities.

This is a senior individual-contributor role responsible for orchestrating complex, cross-functional technology initiatives across Observability Engineering, SRE, Platform Engineering, Cloud Engineering, application/product teams, service management and operational partners.

The role will provide end-to-end delivery leadership across the Observability Engineering roadmap and the establishment and evolution of the Command Center/NOC operating model.

The Technology Delivery Manager will ensure that initiatives progress from strategy and roadmap through implementation, onboarding and operational readiness, while proactively managing risks, dependencies, stakeholders and delivery commitments.

At IC25 , the role is expected to operate with a high degree of autonomy, take ownership of complex workstreams, identify systemic delivery challenges, propose solutions rather than simply escalate problems, influence cross-functional stakeholders, improve delivery practices and mentor others.

Own and coordinate delivery of the Observability Engineering roadmap across Platform Engineering, SRE, Cloud Engineering and application teams.

This is aligned with Pearson's stated direction of centralized governance with distributed execution for observability, including publishing consistent monitoring, alerting and operational-readiness standards.

Your current roadmap also includes platform instrumentation, self-service telemetry onboarding, APM/OTEL rollout, New Relic/Grafana access governance, AI-assisted alert triage and SLI/SLO tracking.

Drive the establishment, onboarding and continuous evolution of the Command Center/NOC operating model.

Pearson's current Command Center Model describes the target model as Observe → Triage → Act → Escalate , incorporating monitoring, prioritization and enrichment, runbook-based L1 actions, incident creation/routing and escalation to appropriate technical or incident-management functions.

We position the NOC as the first line for proactive monitoring alerts, initially supporting Platform Engineering applications and potentially expanding later.

Independently own complex delivery across multiple interconnected workstreams.

This is particularly relevant to your intended model because you have already identified sprint planning and ongoing Observability/NOC delivery as responsibilities appropriate for the TDM.

Establish a predictable delivery process for onboarding services into Observability Engineering and the Command Center/NOC.

Pearson's documented Observability BAU scope already includes New Relic/Grafana access and administration, wallboard onboarding, data-source connectivity validation, synthetic checks, dashboard verification, platform health checks, initial incident triage and standard platform onboarding requests.

Create strong visibility of delivery health and progress across Observability Engineering and NOC initiatives.

Delivery metrics and dashboards have already been identified as an important consideration in Pearson's broader Platform Engineering operating-model discussions.

The Observability and NOC initiatives are also being incorporated into the longer-term technology roadmap.

Act as a central delivery coordination point across the technology organization.

Build strong working relationships across:

The role will translate strategy and technical objectives into coordinated delivery activities and ensure stakeholders understand status, dependencies, decisions and risks.

The position should be capable of facilitating difficult cross-team conversations and resolving coordination gaps without needing formal organizational authority.

Coordinate delivery activities involving strategic partners supporting the Command Center/NOC and Observability operating model.

This is highly relevant to the current role because Pearson has been working through Command Center scope, sizing, workload inputs, operating-model boundaries and commercial considerations with its external partner.

Ensure new capabilities move cleanly from project delivery into sustainable operations.

The current Observability BAU model includes platform health validation, synthetic validation, initial incident triage, alert acknowledgment, basic root-cause identification, log collection, documentation and escalation to appropriate teams.

Expectations

The Technology Delivery Manager is expected to demonstrate:

Autonomous Ownership

Take end-to-end ownership of complex delivery areas with minimal supervision.

Complexity Management

Manage interconnected technology initiatives involving multiple teams, systems, stakeholders and dependencies.

Outcome Orientation

Focus on measurable delivery outcomes rather than simply tracking activities.

Problem Solving

Identify root causes, formulate options and drive resolution rather than acting only as an escalation mechanism.

Cross-Functional Influence

Influence priorities and outcomes across teams without relying on direct reporting authority.

Strategic Context

Understand how individual initiatives contribute to wider technology, reliability and operational objectives.

Continuous Improvement

Improve delivery processes, governance and operating practices rather than simply following established processes.

Mentoring & Knowledge Sharing

Support and mentor less-experienced delivery practitioners and help increase delivery capability across the organization.

Stakeholder Credibility

Communicate confidently with engineers, delivery leaders, business stakeholders, partners and senior technology leadership.

Experience & Qualifications

Required

Pearson's environment currently uses New Relic as a centralized observability service, alongside other technologies including Datadog, Splunk and native hyperscaler alerting, with Jira Service Management and ServiceNow forming part of the service-management landscape.

What Success Looks Like

Success in this role means:

Predictable Delivery

Observability Engineering and NOC initiatives have clear ownership, plans, dependencies and measurable progress.

Scalable Onboarding

Services move through Observability and operational-readiness onboarding using repeatable processes rather than ad-hoc coordination.

Operational Readiness

Observability signals translate into well-defined triage, action and escalation pathways.

Reduced Delivery Friction

Cross-functional dependencies and blockers are identified early and resolved before they materially impact commitments.

Executive Visibility

Leadership has concise, accurate and actionable visibility of delivery progress, risks and decisions.

Continuous Improvement

The role leaves processes, governance and operating practices stronger than it found them.

Trusted Delivery Leadership

Engineering teams and leadership see the Technology Delivery Manager as the person who brings structure to complex initiatives and arrives with options when delivery problems emerge.

#LI-AK1