I applied through a recruiter. The process took 1 day. I interviewed at Google
Interview
As others already mentioned, recruiter is gonna ask you some basic questions like how many ip addresses are in /23 subnet, inode definition, system calls name for getting the file path, how to make an executable suid. I was put off by the fact they really want you to have this information memorized instead of being able to look it up but maybe it is just me with my lazy memory. So we did not move forward.
Interview questions [1]
Question 1
They really want you to have memorised the answer rather than being able to find out in few seconds using google!
I applied through a recruiter. The process took 2 weeks. I interviewed at Google in Jul 2012
Interview
Got through the initial recruiter interview. They will ask you to rate yourself in different technical areas of expertise. Don't exaggerate! The recruiters are not technical, but they will close with asking you questions from a sheet they have based on your answers to the expertise question. The higher you rate yourself, the tougher the questions.
Did that fine. Got to the first one-on-one technical interview, also over the phone. VERY technical, not much small talk. Questions were about explaining how traceroute work and displays timing numbers. Forgot the second one, but not too hard.
Interview questions [1]
Question 1
Got into the filesystem inode structure (which I had anticpated), spent a lot of time talking about directory entries and symbolic links versus hard links.
I applied through an employee referral. The process took 1 week. I interviewed at Google (Dublin, Dublin) in Jul 2012
Interview
From very beginning process started out a bit messy as recruiters somehow switched my position to different one. In the end they managed to sort it out with my preparing for different position half of my "preparation time".
Interview itself didn't last very long which I took as a bad sign. Interviewer was asking me questions based on what he saw on the resume, thus most of the questions were Linux and Networking. From how TCP/IP work, to what's a three way handsake to inodes and symbolic/hard links.
However, as some interviews suggest interviewer didn't lead me to find an answer even when I didn't have one. Unfortunately for me whole process was based on whether you knew the question or not, with little or none involvement from the interviewer regarding my answers.
Couple of days later I got an email that we won't be continuing the process.
Interview questions [1]
Question 1
While explaining differences between TCP and UDP, when I mentioned that UDP is more convenient for video streaming websites as video will keep streaming even if packages get dropped. Interviewer asked me isn't that the opposite of what we want as this could hamper the video quality.