18 years of work experience.
10 years managing and technically leading SRE teams at Google.
Recruited, mentored and grew technical managers, functional managers, and senior leaders including software engineers, systems engineers and technical program managers.
Responsible for the reliability and scalability of product launches such as Cloud Identity, Compute Engine, Hangouts Chat and Hangouts Meet.
Proposed, reorganized and scaled shared infrastructure teams responsible for software development related to datacenter services/cluster turnups, incident management and chaos engineering.
SRE, DevOps and Dev
SRE is an implementation of DevOps.
Google "dev" as in Software Engineers focusing on feature [dev]elopment (as opposed to security, privacy or reliability) work "de facto" as DevOps. In the absence of SRE support, devs at Google get to operate their systems themselves. SREs are generally in high demand.
Keeping me Busy
I'm a member of the CRE team within Google SRE. CREs are responsible for bringing SRE best practices including processes and software to the world. While we've been prioritizing working with Google Cloud Platform customers, we are also very much interested in enabling SRE everywhere.
I'd highly recommend reading the second SRE book, The Site Reliability Workbook which contains concrete implementation examples. Google SRE's first book was a broader reference title without as many concrete examples of how to implement our recommendations.