Google Site Reliability Engineer interview questions

Recruiter screen with a list of canned questions, followed by a phone screen with an engineer. 5 onsite interviews with engineers (in one day). Onsite topics: shell scripting, networking, system internals, coding (C), troubleshooting. One follow up on NALSD (Non-Abstract Large System Design), because they forgot it at the on-site. Got an offer ~2 weeks after the last interview.

The interview process was containing several parts: 1. Phone screening with HR. 2. General Linux interview with one of the team members. 3. Live coding interview. 4. Troubleshooting interview. 5. System design interview. There was an option to choose how to make 2 rounds of 2 hourly interview or 1 round of 4 hour inverview. I decided 2 rounds. Google gives time to prepare to the interview, average is 2 weeks, so I took 2 weeks, however now I understand that it would be better to take 1 month. The live coding interview question was: find mostly repeated words in the text file, list them, sort and show number of repeatings. The system design was to design some system of getting reports and saving them. It was my first system design interview, so I didn't ask basic questions: how many users, how much space each file or record, how many per hour and so on.