Minimum qualifications:
- Bachelor’s degree in Computer Science, a related field, or equivalent practical experience.
- 1 year of experience in coding in one or more of the following programming languages: C, C++, Java, Python, Go.
- Experience in optimizing code for stability, functionality and scalability (e.g., crawling, search, troubleshooting).
Preferred qualifications:
- 1 year of experience in coding in one or more of the following programming languages: C, C++, Java, Python, Go.
- Experience in one or more of the following: C++, TyperScript, and Go
- Experience in analyzing and troubleshooting large-scale distributed systems.
- Ability to manage periodic on-call duty as well as out-of-band requests.
About the job
Site Reliability Engineering (SRE) combines software and systems engineering to build and run large-scale, massively distributed, fault-tolerant systems. SRE ensures that Google Cloud's services—both our internally critical and our externally-visible systems—have reliability, uptime appropriate to customer's needs and a fast rate of improvement. Additionally SRE’s will keep an ever-watchful eye on our systems capacity and performance.
Much of our software development focuses on optimizing existing systems, building infrastructure and eliminating work through automation. On the SRE team, you’ll have the opportunity to manage the complex challenges of scale which are unique to Google Cloud, while using your expertise in coding, algorithms, complexity analysis and large-scale system design. SRE's culture of intellectual curiosity, problem solving and openness is key to its success. Our organization brings together people with a wide variety of backgrounds, experiences and perspectives. We encourage them to collaborate, think big and take risks in a blame-free environment. We promote self-direction to work on meaningful projects, while we also strive to create an environment that provides the support and mentorship needed to learn and grow.Responsibilities
- Manage Spanner SRE and deliver critical projects.
- Oversee Spanner customers help themselves with debugging and mitigation.
- Expand Spanner to serve customers in new ways under new conditions and restrictions.
- Improve the overall Spanner observability.