News for hackers. Stuff that matters.
Re:How to get a job at Google, interview questions & process by zppx on Tuesday September 14, 2010 @06:12PM (#1692532)
SRE (Site Reliability Engineers) according to Tom Limoncelli (a Google's SRE) is a kind of sysadmin, I doubt that this would ever be the case.
Re:How to get a job at Google, interview questions & process by illumin8 on Tuesday September 14, 2010 @08:35PM (#1692855)
Right. I interviewed for SRE at Google. It's basically a sysadmin job. You're expected to be proficient at scripting in some language (Python, Perl, bash, etc), but I would assume you're not expected to write code for most Google applications.

I would think the senior SRE engineers know enough about the code base to poke around and make suggestions ("found a bug in module.py at line XYZ that causes bad performance when thousands of users hit it"), but I got the impression that most of their top developers probably would be bored in SRE.

The thing that is ironic is that most of the people interviewing me were not in SRE, but were pure developers. How many companies do you know that let the developers interview sysadmins? I had guys asking me CompSci questions I hadn't heard since college. If the tables were turned, do you think I'd be asking a prospective developer a question about how to configure DRBD replication and heartbeat from one Linux server to another? Even though some devs might know these things from hobby-like experimentation in their free time, they are not going to be doing it on a day to day basis.

It just strikes me as a very broken interviewing system when you have developers interviewing sysadmins.

Re:How to get a job at Google, interview questions & process by mkelly on Tuesday September 14, 2010 @11:03PM (#1693140)
An important distinction that's missing in this discussion is that you can be either an SA-SRE or a SWE-SRE. You can figure out which is which from how the SRE job postings on google.com are phrased.

SWE-SREs have to pass SWE interviews. I work down the hall from Tim. Nobody keeps track of who came in through which side (SA or SWE), but some of the SREs I work with wrote large parts of the services they support.

Re:How to get a job at Google, interview questions & process by 124816 on Wednesday September 15, 2010 @02:05AM (#1693466)
> It just strikes me as a very broken interviewing system when you have developers interviewing sysadmins.

Sounds like your recruiter messed up.

Re:How to get a job at Google, interview questions & process by nolite on Wednesday September 15, 2010 @12:19PM (#1694751)
I had the same issue.. was kinda like, wtf..?
Re:How to get a job at Google, interview questions & process by X-Istence on Tuesday September 14, 2010 @11:31PM (#1693211)
Not entirely true. There are two sides to the SRE positions. The sysadmin side is indeed what you say they are, they work on the systems keep them running and do hardware related tasks as well as UNIX level tasks.

The software engineering SRE's work on products to make sure they are ready to scale or if something fails to fix the point of failure. They work alongside the product development teams to make sure the product is stable in production.

The two positions require two different skill-sets (I was interviewed for both sides of SRE). One requires very much computer science, data structures, programming languages, and all of those, the other sysadmin requires more knowledge about Linux, its internals, and the command line interface.

Re:How to get a job at Google, interview questions & process by mkelly on Tuesday September 14, 2010 @11:05PM (#1693147)
And how many systems does a google sysadmin administer? :)

(Answer: a lot.)