Senior Manager, Platform Continuity

Required

• We're seeking an Engineering Manager to lead Platform Continuity, a newly formed team within Cloud Platform Engineering that serves as the operational backbone of our multi-cloud infrastructure organization. This is a build-from-the-ground-up leadership role for someone who thrives at the intersection of operational discipline and engineering rigor.
• Platform Continuity exists to execute the engineering work that keeps systems healthy and unblocked work that requires privileged access and platform judgment, but does not belong to a single product vertical and is not net-new design. Your team handles IaC drift remediation, VDI operations, monitoring and alerting hygiene, cloud cost management, and SRE-tier application support across Datavant's AWS and Azure environments.
• The ideal candidate understands the difference between operational work and infrastructure engineering and holds the line between them. You build teams that work from playbooks, not ad hoc, and you're relentlessly focused on eliminating the work your team does by hand. You measure success not by ticket volume, but by how much repeatable work has been handed off to automation or back to accountable teams with runbooks that actually work.
• 5+ years of engineering management experience, including managing distributed or international teams across multiple time zones.
• Strong technical foundation in cloud infrastructure operations sufficient to establish credibility with Staff-level SREs and make sound judgment calls on scope and escalation.
• Knowledge of Terraform/IaC; hands-on experience managing infrastructure state, module versioning, and workspace hygiene at scale.
• Solid Kubernetes operational knowledge (EKS and/or AKS) cluster health, workload troubleshooting, and node management.
• Experience with AWS (required) and Azure (strong plus) in regulated or compliance-sensitive environments.
• Hands-on experience with observability platforms Datadog preferred including monitor management, alerting configuration, and dashboard governance.
• Demonstrated ability to build operational discipline: runbooks, SLAs, intake processes, escalation paths, and shift-left frameworks.
• Clear communication skills for defining scope boundaries, managing cross-team expectations, and explaining operational tradeoffs to both technical and non-technical audiences.
• Comfort with ambiguity this is a new team with a deliberately bounded scope, and you'll be defining the operating model in parallel with executing it.