Director of Site Reliability Engineering

At The ReWork Group, we partner with high-growth startups and forward-thinking companies to build the future.

We are looking for a Director of Site Reliability Engineerin
g to lead one of our clients. This is a senior engineering leadership role reporting directly to the CTO. You will set the vision, operating model, and culture for SRE, and you will own the core infrastructure that lets engineering teams build, deploy, observe, and run software with confidence.

The model here is deliberate.

Engineering teams own the services they build. SRE provides the frameworks, standards, shared infrastructure, tooling, observability practices, and enablement that make strong ownership possible. You are not the safety net under every team. You are the reason they do not need one.

That means leverage matters more than headcount, judgment matters more than process, and the ability to influence through trust, clarity, and execution matters more than authority on an org chart. If you reach for credibility and outcomes before you reach for a new process, you will do well here.

• Build and lead the team. Lead, coach, and develop a distributed SRE team. Set a clear charter, operating model, priorities, and success measures, and hold the line on what SRE is and is not responsible for.
• Define service ownership at scale. Create and roll out a Service Ownership and Maturity Framework across engineering, with expectations that scale appropriately to service criticality rather than applying one heavy standard to everything.
• Run the core infrastructure. Own and improve cloud foundations, Kubernetes and compute patterns, CI/CD, observability, secrets management, Git Hub workflows, and infrastructure automation.
• Make teams better operators. Help engineering teams strengthen their own service ownership through better standards, dashboards, runbooks, alerting, escalation paths, operational readiness, and deployment practices.
• Make reliability measurable. Turn reliability, operational maturity, infrastructure health, and developer productivity into trusted metrics and practical operational intelligence, not vanity dashboards.
• Engineer for resilience. Improve deployment automation, self-healing patterns, disaster recovery readiness, and service reliability based on real impact and risk, not theoretical failure modes.
• Mature incident response. Level up incident response, escalation, postmortems, and on‑call health across a geographically distributed team.
• Pave the road. Build paved paths and self‑service infrastructure that reduce toil, lower cognitive load, and help teams move faster while strengthening ownership and reliability.
• Partner across the org. Work closely with Security, Compliance, Legal, Finance, Procurement, and Corporate IT wherever infrastructure, access management, cloud operations, vendor review, or controls intersect with engineering.
• Use AI where it earns its place. Pragmatically evaluate AI‑assisted and agentic workflows where they genuinely improve infrastructure operations, service ownership, developer workflows, or toil reduction.

You have spent your career closer to production than to slideware. You have led teams, but you can still reason about a reliability tradeoff in detail. You know when to build, buy, adapt, simplify, or retire a system based on the actual problem in front of you, and you are comfortable being the person who says a process is not worth its weight.

You operate well where influence comes from judgment and results rather than bureaucracy, and you can sit across from a CTO and senior engineering leaders as a peer.

• 10+ years in SRE, infrastructure engineering, platform engineering, cloud infrastructure, production operations, or closely related engineering work.
• 5+ years leading, managing, or formally developing infrastructure, SRE, platform, or reliability engineers.
• Proven experience defining team charters, operating models, roadmaps, success measures, and engineering practices for infrastructure or reliability teams.
• Deep technical judgment across cloud infrastructure, production operations, distributed systems, reliability tradeoffs, automation, and operational risk.
• 3+ years with modern cloud infrastructure in AWS, GCP, or similar environments.
• 3+ years with Kubernetes, container orchestration, infrastructure‑as‑code, declarative systems, CI/CD, and deployment safety.