Job Offer: Google Site Reliability Engineering

And now, a word from one of our sponsors, Google. –Dirk Riehle


Do you want to work on a wide diversity of technologies? Do you enjoy working with both, systems and coding?

If so, then Google’s Site Reliability Engineering (SRE) role might be interesting for you. For our Site Reliability Engineering Team we are looking for students who will graduate in 2012 or who have recently graduated. They will bring fresh perspectives to solving problems, along with the technical and soft skills needed to keep Google’s services growing and reliable!

Site Reliability Engineering (SRE) is the engineering group responsible for the reliability of Google’s production systems and services. SRE takes care of Google’s most important user-visible applications as well as its core infrastructure and makes Google’s services fast and reliable for hundreds of millions of users. This mission critical team combines software development, networking, and systems engineering expertise to build and run large scale, massively distributed, fault-tolerant software systems and infrastructure.

Desired requirements:

  • Software Engineers: Python, Perl, C/C++, Java developers + Unix/Linux systems knowledge, IT infrastructure
  • Systems Engineers: Unix/Linux experts with scripting/coding skills (in C, C++, Perl, Python, Java)

What makes a good Software Engineer within SRE? How does this differ from other software development roles?

  • “Generalists”; people who like to work on a wide diversity of technologies, or those who haven’t yet decided where they want to specialize (versus those who know they wish to focus deeply on one or a few areas).
  • People who like problem solving, troubleshooting complex problems, optimization, and systems with many moving parts.

If you are interested in the Site Reliability Engineering role, please sign up on this form. You can find more information about the role here and here.

Google did not provide a form, however, we’ll help you get in touch, so just check in with Prof. Riehle.