Google Site Reliability Engineer Interview Questions

I would first determine whether the issue is local to one host, one region, or the whole network path. Then I would check DNS, routing, MTU, retransmissions, connection resets, and any recent infrastructure changes. The reason I choose this approach is that network issues often show up as symptoms in several layers, so I want evidence before making a guess. I would also think about whether the problem is load-related, hardware-related, or due to a bad deploy. If needed, I would explain how I would use tracing or packet captures to narrow it down.

I would first compare the new version against the previous one and identify whether the latency issue is isolated to a specific endpoint or dependency. If the problem is severe, I would consider rollback or disabling the risky feature while I investigate. The reason I choose this approach is that deployment-related latency regressions are often caused by one behavior change that can be reverted quickly. I would also inspect traces, resource usage, and any changed query or code path. If the interviewer wants more detail, I would talk about canary analysis and post-deploy validation.

I would compare new builds against a stable baseline using key metrics such as latency, error rate, and throughput. I would also run synthetic checks or canary traffic so regressions show up before a full rollout. The reason I choose this approach is that automated regression detection helps catch issues faster than waiting for user reports. I would think about thresholds, false positives, and how to route the signal to the right owners. If needed, I would mention that the detection should be tied to actionable rollback or escalation paths.

I would describe a situation where the goal or requirements were not fully defined and explain how I clarified the problem. Then I would show how I gathered information, made assumptions explicit, and kept the project moving. The reason I choose this style is that SRE work often involves incomplete information during incidents or planning. I would also mention how I communicated uncertainty without slowing the team down. If the interviewer wants more detail, I would explain the final outcome and what I learned.

I would say I try to listen carefully, ask clarifying questions, and separate the feedback from my initial reaction. Then I would decide what specific action to take and follow up later to show that I took it seriously. The reason I choose this approach is that SRE work depends on trust, and feedback is part of building that trust. I would also mention a case where feedback helped me improve a process or technical decision. If the interviewer wants more detail, I would focus on how I turned that feedback into a measurable change.