Senior Software Engineer, Cloud Spanner Platform

Google•Sunnyvale, CA

7h•$174,000 - $252,000

About The Position

As a Senior Software Engineer on Google Cloud Spanner, you will work on a globally distributed relational database service operating at industry-leading scale and reliability. Cloud Spanner is a fully managed, cloud-native database with unlimited scale, strong consistency, and up to 99.999% availability, and is used by many Google products and services. As part of the service health team, you will help provide customers with a predictable, robust experience across workloads of all sizes. The team focuses on scale, isolation, and resiliency. Google software engineers work on projects critical to Google's needs, develop technologies used at massive scale, and are expected to bring fresh ideas, versatility, leadership, and enthusiasm for solving new problems.

Requirements

Bachelor’s degree or equivalent practical experience.
5 years of experience with software development in one or more programming languages.
3 years of experience developing large-scale infrastructure, distributed systems or networks, or experience with compute technologies, storage, or hardware architecture.
3 years of experience testing, maintaining, or launching software products.
1 year of experience with software design and architecture.
Experience with distributed systems and backend development.

Nice To Haves

Master's degree or PhD in Computer Science or a related technical field.
Experience programming in C++.
Experience solving problems at scale.
Experience with database core concepts, consistency, and isolation.

Responsibilities

Address ambiguous challenges at scale for Google's largest Cloud customers.
Design and develop features that support future scale and increase resiliency and isolation.
Identify future bottlenecks through monitoring, experimentation, and other signals, and propose solutions.
Collaborate with Site Reliability Engineering (SRE) and partner teams to deliver holistic solutions, often spanning multiple quarters and requiring cross-team influence and strong communication.
Lead architectural changes in a massively distributed system.