There were two rounds: - Coding - System Design Coding - Mildly positive experience: - Had to write a working code to solve that problem and the questions go around the algorithms, optimizations etc. I think the expectation of coding on par with the developer is a bit too much for an SRE. SREs scripts to automate around the production/infrastructure stability, provisioning, deployments and probe tools. So IMHO the questions should be around that, not on how do you design and code an application, that too which has algorithms/data-structures such as trees/maps. Although I managed to write a working code. System Design - Positive experience: - Mostly from one of the common/widely-used distributed system (Ex: TinyURL, Whatsapp etc.), you need to design that. This one went well for me. Recruiter Response - very negative experience: Two weeks past the interview process, have asked for updates from the recruiter. But no response yet. Total 4 weeks as of now no updates, which is bad, even if it is a rejection, Recruiter should inform the candidate.
