Director, Site Reliability Engineering — AI Accelerator Infrastructure

The Role

You will build and lead Our Client's Site Reliability Engineering function from the ground up — owning the infrastructure that development, validation, and customer-facing deployments run on. This spans colocation facilities, on-premises lab clusters, cloud environments (AWS, Azure, GCP), and the platform services customers use to collaborate with our Client on hardware and software deployments.

You are a hands-on engineering leader. You will establish SRE as a discipline at our client, hire and grow the team, set the technical direction, own SLOs for critical systems, and be the senior escalation point when things go wrong — all in parallel. You will partner closely with the Director of DevOps Engineering, whose pipelines and automation run on the infrastructure you own, and work directly with hardware and software development teams to ensure HPC infrastructure meets their workload requirements.

What You Will Do

Leadership & Organizational Build-Out

• Own the SRE function end-to-end: define the team’s charter, establish SRE as a discipline within our client's engineering culture, and drive buy-in across hardware, software, and executive stakeholders who have operated without a dedicated SRE team.
• Hire, develop, and retain a team of 3–5 SRE engineers; establish a culture of operational excellence, ownership, and continuous improvement from day one.
• Define the SRE technical roadmap: reliability architecture, automation priorities, capacity planning, and on-call model — and execute against it with your hands on the keyboard where needed.
• Serve as the senior technical escalation for critical incidents — guiding cross-team triage, driving RCA, and ensuring systemic fixes rather than point patches.
• Translate operational signals and infrastructure health into clear, actionable narratives for engineering leadership and executive stakeholders.
• Partner with the Director of DevOps Engineering to align infrastructure reliability with pipeline and automation delivery; the two functions must operate as a unified platform.
• Direct a dedicated Data Center & Lab Technician team — your hands and feet across on-premises and colocation facilities; set their work priorities, establish operational standards, and ensure physical infrastructure execution aligns with the SRE technical roadmap.

Reliability & Observability — Building From Scratch

• Establish SRE process from a zero baseline: define SLIs and SLOs, build error budgets, design on-call rotations, and create the incident management framework our client currently lacks.
• Own 24×7 reliability across colocation, on-premises lab clusters, cloud, and customer-facing platform services — designing for failure domains, progressive delivery, and strict change control at every tier.
• Own the full observability stack (metrics, traces, logs) and instrument it from the ground up — Prometheus, Grafana, and/or Datadog — with SLO visibility, alert design, and E2E signal quality.
• Evolve incident and problem management into a data-driven discipline: automated triage workflows, pattern detection across recurring failures, and every P0/P1 producing a written RCA with tracked systemic fixes.
• Own FinOps and capacity planning as a unified discipline across all three infrastructure tiers — cloud (AWS, Azure, GCP), colocation, and on-premises: establish spend visibility and attribution across every tier, model TCO comparatively, drive workload placement decisions based on cost and performance, and anticipate infrastructure needs for new silicon programs and customer deployments.
• Own the migration from ad-hoc JBOD-based storage and point-in-time snapshots to an enterprise-grade shared storage platform spanning on-premises, colocation, and cloud tiers — covering architecture, vendor selection, data protection design (snapshots, replication, DR), and integration with HPC workloads and development environments

Automation & Infrastructure as Code — Establishing the Baseline

There is no automation baseline today. You will build it.

• Drive IaC-first discipline across the team — Terraform, Ansible, and production-quality automation for all infrastructure provisioning and lifecycle management; this capability is currently absent and you will establish it.
• Build self-healing infrastructure platforms: host lifecycle automation, fleet auto-remediation, and AIOps-driven alerting that reduce manual intervention across the operational lifecycle.
• Instrument the team’s own development practices — runbooks, change governance, deployment pipelines for infrastructure code — establishing standards that scale as the team grows.

Documentation & Global Collaboration

• Build a documentation culture from scratch: runbooks, architecture diagrams, and operational playbooks maintained as living artifacts — not a one-time project.
• Design and scale a follow-the-sun on-call model as our client expands globally; the framework you build now will be the foundation the team inherits.
• Drive POC and POV evaluations for new infrastructure technologies, interconnect fabrics, and platform services relevant to our client's accelerator roadmap.

What You Will Bring

Required

• Bachelor’s or Master’s in Computer Science, Electrical Engineering, or related field; 15+ years in SRE, infrastructure engineering, or production engineering.
• 5+ years leading SRE or infrastructure engineering teams — including experience building or significantly rebuilding a function, not just managing a steady-state team.
• Demonstrated track record of establishing SRE as a discipline in an organization that lacked it: defining SLOs, creating on-call frameworks, standing up observability, and driving cultural change with engineering teams that came from a reactive ops background.
• Deep Linux systems expertise: networking (TCP/IP, RDMA, bonding), kernel tuning, and bare-metal operations; hands-on experience with enterprise shared storage platforms (NAS/SAN, NFS/SMB at scale, snapshot and replication architectures) and hybrid-cloud storage integration across on-prem and cloud tiers.
• Proven experience operating colocation and on-premises hardware at scale: server lifecycle, power and cooling awareness, rack-level networking.
• IaC fluency: Terraform and Ansible at production scale — module design, remote state, environment isolation, and change governance.
• Kubernetes cluster operations: lifecycle management, workload reliability, storage, and RBAC at scale.
• Full observability stack ownership: Prometheus, Grafana, and/or Datadog — SLO definition, alert design, and E2E signal quality.
• Strong Python and/or Go — production services, not just scripts; automation that touches real infrastructure safely.
• Executive communication: translating infrastructure health and operational risk into clear narratives for senior leadership, including stakeholders with no infrastructure background.
• Ability to operate in a high-ambiguity, low-process environment — you build the structure, you don’t inherit it.

Strongly Preferred

• Experience operating customer-facing infrastructure or platform services — reliability expectations beyond internal tooling.
• Knowledge of high-speed interconnect fabrics: InfiniBand, RoCE, or NVLink — setup, troubleshooting, and performance tuning.
• HPC job scheduler experience: Slurm, LSF, or equivalent — setup, tuning, and integration with infrastructure automation.
• Multi-cloud hybrid operations: AWS, Azure, GCP alongside on-prem/colo — unified observability and IaC across all tiers.
• FinOps: cloud spend attribution, TCO modeling across cloud vs. on-prem vs. colo, and translating cost data into workload placement recommendations.
• ITIL knowledge or equivalent structured incident/problem/change management framework.
• Published technical writing, conference talks, or open-source contributions in reliability, observability, or HPC infrastructure.