Probably the first impression about the company you get out of your interaction with a recruiter. The person that guided me through the process wasn't extremely accurate and punctual. I have to send a couple of reminders during the process and an interview was also being rescheduled once. Overall nothing that critical but might give you a wrong impression about the company. The process looks like that: 1) Screening with a recruiter Just a general chit-chat about your experience and the company, a couple of questions about what are you doing in your current position, what they a looking for, etc. Gets somewhat technical towards the end of the interview as the recruiter asks questions regarding SRE, if you read the "sre" books by Google, you know the answers. 2) Technical assignment A good approach as they don't ask you to do it in your free time and it could be done as a "pair-programming" exercise during the technical interview. So either do it at home if you have time and desire or leave it until the interview but you know what to expect. It's a small service you need to instrument and the thing revolves around observability. 3) Interviews They have 3 interviews back-to-back, "pair coding" for the tech assignment , technical and behavioral. The first one I enjoyed a lot since it looked like I was on the same page with the interviewers and it went pretty smoothly. Bunch of questions on monitoring, SLI/SLO/SLA and kubernetes but nothing really hard. The next interview was a technical one with 2 future peers. The opening question was "so please tell me how the dns works". Honestly I lost it here. Why the hell would you ask questions like "how dns works/how a request to google.com works/other junior level questions" for a senior role? The full and proper answer for that question easily takes solid 20 minutes to reply. You want to know, if a candidate knows DNS ins and outs? I don't know, ask how to delegate a zone, ask about DNSSEC, ask about the historical design or DNS alternatives. These will take up way less time and with a couple of follow ups could be a good gauge for the candidate's depth of knowledge. Instead you waste 1/3 of the interview to that nonsense. Another interviewer did ask more deep questions afterwards but it was already a miss. Interview finished with a "whiteboard" system design question : nothing special, but rather vague requirements from the interviewer(the same one asking that "how dns works" question) so you have to ask a lot of questions. Third and final interview with your hiring manager and a junior peer. Was a bit surprised, but they asked a lot of mentorship questions, e.g "how would you help a fresh starter to learn something new, how would you approach a negative feedback to a junior, etc" to which I wasn't prepared as it wasn't mentioned during the interview process that this roles involves a lot of training and menthorship from your side. Maybe it's obvious when you apply for a senior position but please articulate it during the process, that you expect me to grow a new gen of engineers. Overall: sloppy recruiters, interviewers that ask you irrelevant questions. Wouldn't recommend.