Job Summary

The Project Manager – Observability will be responsible for end-to-end planning, governance, coordination, and delivery of enterprise Observability, APM, Event Management, and AIOps initiatives. The role will coordinate multiple technical and business stakeholders to drive implementation and adoption of capabilities across Splunk Observability Cloud, Splunk AppDynamics, Splunk ITSI, OpenTelemetry, ServiceNow, and related enterprise monitoring platforms. The Project Manager will own the delivery roadmap, milestones, dependencies, risks, governance, stakeholder communication, and measurable outcomes such as improved monitoring coverage, event-noise reduction, proactive detection, automation, and reduction in MTTD/MTTR.

Key Responsibilities

Key Responsibilities 1. Observability Program / Project Management Manage end-to-end delivery of Observability, APM, Event Management, and monitoring-modernization initiatives. Develop and manage project plans, schedules, milestones, resource requirements, dependencies, and deliverables. Coordinate implementation across applications, infrastructure, cloud, network, database, middleware, and Kubernetes/container platforms. Drive projects from discovery and assessment through design, implementation, onboarding, testing, production rollout, and operational handover. Ensure delivery aligns with agreed scope, timelines, quality standards, and business objectives. 2. Observability Transformation Drive initiatives covering: Application Performance Monitoring Infrastructure Monitoring Cloud and Kubernetes Observability Real User Monitoring Synthetic Monitoring Distributed Tracing OpenTelemetry adoption Log, metric, and trace correlation Event Management and correlation Service health monitoring AIOps and operational automation Partner with architects and engineering teams to establish an integrated: Applications → APM → Infrastructure/Cloud → Logs/Metrics/Traces → Event Correlation → ITSM → Automation operating model. 3. Tooling & Platform Coordination Coordinate delivery across platforms such as: Splunk Observability Cloud Splunk AppDynamics Splunk ITSI Splunk Enterprise OpenTelemetry ServiceNow Azure Monitor / Application Insights AWS CloudWatch Kubernetes monitoring Dynatrace / SolarWinds / SCOM or other incumbent monitoring platforms Ensure interfaces, dependencies, onboarding requirements, integrations, and ownership are clearly defined. 4. Stakeholder Management Act as the primary point of coordination between business, application, infrastructure, cloud, observability, DevOps/SRE, security, ITSM, and operations teams. Conduct project governance meetings and technical workstream reviews. Provide concise executive-level status reporting on progress, risks, issues, dependencies, and decisions required. Manage expectations across customer, delivery, product, engineering, and vendor stakeholders. Drive closure of cross-functional dependencies and escalations. 5. Application & Infrastructure Onboarding Establish a structured onboarding factory for applications and infrastructure services. Track discovery, instrumentation, agent deployment, telemetry configuration, dashboards, alerting, testing, and production enablement. Define onboarding waves based on application business criticality and technical dependencies. Maintain onboarding dashboards covering planned, in-progress, blocked, completed, and production-stabilization status. 6. Event Management & AIOps Coordinate implementation of Splunk ITSI event-management capabilities. Drive alert rationalization and event-noise reduction initiatives. Coordinate event normalization, enrichment, deduplication, suppression, and correlation activities. Facilitate integration between monitoring platforms and ServiceNow. Track automation and self-healing opportunities identified through observability and event-management data. 7. Project Governance & RAID Management Maintain robust program governance, including: Risks Actions Issues Dependencies Decisions Change requests Financial/resource considerations Milestone tracking Escalations Ensure risks and blockers have clear ownership, mitigation plans, and target closure dates. 8. Service Transition & Operational Readiness Coordinate production-readiness assessments before transitioning new monitoring capabilities into BAU. Ensure availability of architecture documentation, SOPs, runbooks, support models, escalation paths, dashboards, and knowledge-transfer materials. Define L1/L2/L3 support responsibilities and operational handoffs. Ensure teams are trained on newly implemented monitoring and observability capabilities. Coordinate hypercare following major production rollouts. 9. KPI & Benefits Tracking Establish measurable success criteria such as

Skill Requirements

Area Example KPICoverage % critical applications onboarded Telemetry % applications with metrics, logs and traces Event Management Reduction in non-actionable alerts Correlation % alerts correlated into actionable events/episodes Automation % eligible events automated Detection Improvement in MTTD Recovery Improvement in MTTR Reliability Reduction in repeat incidents Adoption Dashboard/observability capability utilization Delivery Milestones completed on schedule The Project Manager should ensure that technical implementation translates into measurable operational benefits, rather than treating tool deployment itself as project success.

 Required Skills Project / Program Management Project planning and delivery management Agile / Scrum / Waterfall methodologies RAID management Resource and capacity planning Financial / budget tracking Executive reporting Stakeholder and vendor management Change and release coordination Observability Domain Knowledge Strong conceptual knowledge of: Application Performance Monitoring Infrastructure Monitoring Observability Metrics, Logs and Traces Distributed Tracing OpenTelemetry Event Management AIOps Monitoring modernization Cloud and Kubernetes monitoring ITSM integration Incident / Major Incident / Problem Management Technology Exposure The PM does not need to be the deepest technical SME, but should be capable of effectively managing engineering workstreams involving: Splunk Observability Cloud Splunk AppDynamics Splunk ITSI Splunk Enterprise OpenTelemetry ServiceNow Microsoft Azure AWS Kubernetes CI/CD and DevOps environments

Other Requirements

Preferred Qualifications Bachelor\'s degree in Engineering, Computer Science, IT, or equivalent. PMP / PRINCE2 / equivalent Project Management certification. Agile / Scrum certification preferred. ITIL Foundation preferred. Cloud certifications such as Azure or AWS are advantageous. Splunk/AppDynamics/Observability platform exposure is strongly preferred. For a Pharma/Life Sciences account, experience working in regulated environments involving GxP, validated systems, audit requirements, controlled change management, and compliance governance would be highly desirable. Key Success Measures The role should ultimately demonstrate: Successful onboarding + Increased observability coverage + Reduced alert noise + Improved correlation + Increased automation + Reduced MTTD/MTTR + Effective operational transition