Address
Form of workAt Google, we have a vision of empowerment and equitable opportunity for all Aboriginal and Torres Strait Islander peoples and commit to building reconciliation through Google’s technology, platforms and people and we welcome Indigenous applicants. Please see our Reconciliation Action Plan for more information.
Minimum qualifications:
- Bachelor’s degree in Computer Science, a related field, or equivalent practical experience.
- 10 years of experience with software development in one or more programming languages.
- 10 years of experience with data structures or algorithms.
- 8 years of experience leading projects and designing, analyzing, and troubleshooting distributed systems.
Preferred qualifications:
- Experience in designing, analyzing, and troubleshooting distributed systems at planet scale, ideally in stateful storage systems.
- Expertise in distributed systems monitoring architectures and configuration.
- Experience in large scale incident response and debugging.
- Experience in automating all operational aspects of systems in production.
- Systematic problem-solving approach, coupled with effective verbal and written communication skills.
- Experience working with Cloud Firestore, and Java, and Google internal services including Spanner, Borg, Bigtable, and Monarch.
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's services—both our internally critical and our externally-visible systems—have reliability, uptime appropriate to users' 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, while using your expertise in coding, algorithms, complexity analysis and large-scale system design.
SRE's culture of diversity, 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.
To learn more: check out our books on Site Reliability Engineering or read a career profile about why a Software Engineer chose to join SRE.
Firestore is a flexible, scalable database for mobile, web, and server development from Firebase and Google Cloud. Firestore keeps your data in sync across client apps through realtime listeners and offers offline support for mobile and web so you can build responsive apps that work regardless of network latency or Internet connectivity.
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.
Responsibilities
- Engage in and improve the whole lifecycle of services—from inception and design, through to deployment, operation and refinement.
- Review and act as approver for software designs from team members and from other engineering teams, in APAC and the US.
- Identify new features, produce designs, and lead more junior team members through the implementation of those designs, including the monitoring systems, capacity planning and launch reviews required to launch new features.
- Scale systems sustainably to planet scale through mechanisms like automation, and evolve systems by pushing for changes that improve reliability and velocity.
- Lead the team through incident response, and lead through incident postmortems, acting as an approver for resulting engineering plans.
