Senior Observability & SRE Leader

Senior Observability & SRE Leader

Marsh is seeking a visionary, transformational leader to reimagine and rebuild our Observability and Site Reliability Engineering function from the ground up. This is not a role for someone who wants to maintain the status quo. We need a leader who will fundamentally shift this function to a predictive, data‑driven engineering discipline that prevents outages before they happen, embeds reliability into every system from design through production, and treats observability data as a strategic asset - not just an operational tool.

This is a career‑defining opportunity to build a world‑class observability and SRE organization at Fortune 500 scale.

• Define and execute an observability and SRE strategy that shifts the organization from reactive operations to predictive reliability engineering.
• Architect and deliver a unified, full‑stack observability platform covering metrics, traces, logs, real‑user monitoring (RUM), synthetic monitoring, and business‑level KPIs - across on‑prem, multi‑cloud (AWS/Azure), containers, and SaaS integrations.
• Rationalize and consolidate the current fragmented tooling landscape into a cohesive, cost‑optimized platform. Eliminate redundant tools, reduce alert noise by 80%+, and establish a single pane of glass for system health.
• Drive adoption of Open Telemetry as the standard instrumentation framework, ensuring vendor‑agnostic telemetry collection and future portability.

• Build and operationalize AIOps and ML‑driven capabilities to detect anomalies, predict failures, and surface emerging risks before they impact customers. Move beyond threshold‑based alerting to intelligent, context‑aware detection.
• Establish automated correlation engines that link infrastructure signals, application traces, deployment events, and change records to dramatically reduce diagnostic time and identify root cause automatically.
• Design and implement self‑healing automation that detects, diagnoses, and remediates common failure patterns without human intervention - targeting 40%+ of recurring incidents for autonomous resolution.
• Introduce chaos engineering and reliability testing programs (Game Days, fault injection, load testing) to proactively discover weaknesses before production incidents reveal them.

• Transform the existing operations‑centric team into a modern SRE organization with embedded reliability engineers across product and platform squads, operating under a "you build it, you own it" model.
• Define and implement SLO/SLI/Error Budget frameworks across critical services, creating a shared language between engineering, product, and business stakeholders for reliability decisions.
• Drive the adoption of Dev Ops practices, CI/CD pipelines, and infrastructure as code using tools like Terraform or Cloud Formation to manage infrastructure.
• Champion reliability‑first design principles - ensuring observability, graceful degradation, circuit breaking, and failure isolation are architected into every system from day one, not bolted on after launch.

• Partner with Major Incident Management and Problem Management to build closed‑loop feedback systems - every incident produces a reliability improvement, not just a postmortem document.
• Drive MTTR toward minutes (not hours) through automated diagnostics, pre‑built remediation playbooks, and intelligent correlation that tells responders what is wrong, not just that something is wrong.
• Establish "Incidents Prevented" as a primary success metric alongside traditional MTTR/MTTD measures.

• Elevate observability from infrastructure metrics to business outcomes. Build real‑time dashboards that connect system health to revenue impact, customer experience scores, and SLA compliance.
• Integrate observability insights into ITSM (Service Now), data platforms, and executive reporting - making reliability data a first‑class input to business and technology decision‑making.

• Own the total cost of ownership of the…