In-house recruiter reached out to me and within a few days, we did a phone screen. Lots of confusion and rescheduling. Interviewer was late to the interview. A quick intro about the position and the expectation, some technical questions, nothing really difficult. Code pairing, which really wasn't code pairing it was more like something that could be done with a command in shell. I got rather annoyed, knowing that in the role of an SRE, there is so little coding that is actually done by the SRE and if it is done it's to automate a process.
I realized that the entire interview was going to be judged on that exercise and I just went ahead and basically blew it. Yep, I can code. Nope, it's not a major part of what an SRE does. Thirty minutes was the scheduled time.
Write a program in whatever language you want that will add users and then add users to groups.
The following metrics were computed from 1 interview experience for the X SRE role in San Francisco, California.
X's interview process for their SRE roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for X's SRE interview process in San Francisco, California.