Director, Engineering, Sovereign Environments, SRE, Cloud

Minimum qualifications:

• Bachelor's degree in Computer Science, a related technical field, or equivalent practical experience.

• 15 years of experience with system design, algorithms, data structures, complexity analysis and software design or with Unix/Linux systems, IP networking, performance and application issues.

• Experience with container orchestration (Kubernetes/GKE) operating outside of public cloud data centers.

Preferred qualifications:

• Capable of technical deep-dives into code, operating systems and storage, yet verbally and cognitively agile enough to hold your own in a strategy discussion with Google’s executive team.

• Fluency in AI/GenAI product integration and operational automation.

• Proven track record of converting high-touch operational procedures into self-service, automated software solutions.

• Demonstrated expertise in managing a distributed team of experienced software engineers of large-scale projects.

• Proven track record of growing and building highly effective teams, as well as working with stakeholders and collaborating across organizational boundaries.

About the job:

As part of Technical Infrastructure, Google’s Site Reliability Engineering (SRE) is an engineering discipline for building and running large-scale, massively distributed, fault-tolerant systems. Our Site Reliability Engineers (SREs) come from both software engineering and systems engineering backgrounds and specialize in designing, building and maintaining large-scale production services. SRE ensures that Google’s services - both our internally critical and our externally visible systems - have reliability and uptime appropriate to users’ needs and a fast rate of improvement while keeping an ever-watchful eye on capacity and performance. Along with a set of engineering approaches, SRE is a mindset of running better production systems. We build our own creative engineering solutions to operations problems. Much of our software development focuses on optimizing existing systems, building infrastructure and eliminating work through automation. SRE is responsible for the big picture, determining how our systems relate to each other, using a breadth of tools and approaches to solve a broad spectrum of problems. Practices, such as limiting time spent on operational work, blameless postmortems and proactive identification of potential outages, factor into iterative improvement that is key to both product quality and interesting, dynamic day-to-day work. SRE’s culture of intellectual curiosity, problem solving and openness is key to its success.

Behind everything our users see online is the architecture built by the Technical Infrastructure team to keep it running. From developing and maintaining our data centers to building the next generation of Google platforms, we make Google's product portfolio possible. We're proud to be our engineers' engineers and love voiding warranties by taking things apart so we can rebuild them. We keep our networks up and running, ensuring our users have the best and fastest experience possible.

Individual pay is determined by factors including job-related skills, experience, and relevant education or training.

US: $307000 - $427000 (USD) + 30% bonus target + equity + benefits

Learn more about benefits at Google. Responsibilities:

• Drive the transformation of Google’s internal operational processes, tools, and practices to enable partners to operate the cloud autonomously while maintaining service parity and Google rollout velocity.

• Ensure that SRE principles (SLOs, alerting, runbooks, diagnostics) are built directly into the shipped software so external infrastructure operators can operate it reliably without Google's intervention.

• Redesign incident response, monitoring, and debugging paradigms for universes where Google SREs do not have ambient access.

• Oversee support tiers, including extended workforce who act as Level 3 support or manage canonical pre-production/staging environments.

• Manage reliability for a massive, globally distributed "fleet of fleets." This includes managing lifecycle operations (Day 0 turnup, Day 1 install, Day 2 repairs) in addition to software reliability.