Google Site Reliability Engineer interview questions

Interview was a fairly long process. Started with an online application, sent my resume not expecting very much. Got a response, was requested to complete an online survey plus timed coding exercise. The exercise was pretty straightforward, some strings manipulation and 1D array manipulation (fruit basket leetcode). Made it to the next round, phone interview over Google Docs with an engineer. This part I was shocked at how simple the questions were, delete every other elem from a linked list and some really easy strings question. I felt pretty confident afterwards, had to follow up with my recruiter a couple times to help advance things along. Finally, the onsite in Pittsburgh, had to do 4 whiteboarding technical interviews with lunch in between. For me at least I wasn't asked any system design questions or anything related to my resume, just straight up questions out of leetcode or ICPC. I felt like I nailed two but encountered turbulence doing the other two, managed a satisfactory coded solution on all but one. They give you the option to do it either on the whiteboard or on a chromebook connected to a projector. One of the questions was really poorly formed and I had trouble communicating with the engineer who asked it of me, but the others were all well understood and clear problems. I don't recommend taking bathroom breaks mid interview like I did or you will feel short on time (45 min per.) Two weeks later I got a phone call stating I wasn't a "good match". Overall a pretty long process, but that's what this type of job at this type of company presupposes I guess.