The process consist of a total of 7 interviews.
====
They are quite clear about the interviews steps and the interviewers really try to make you feel comfortable.
Each interview steps is well defined in the emails that you receive.
The process is somehow long, but at least you directly speak with a human being from the beginning.
The interviews are really open ended, the questions may vary based on your profile and experience. I found that interviewers are well prepared.
DevOps and CI/CD
* Simple live coding bash/shell exercise, this is just to see if you know how to work with shell
* Open discourse about deployment strategies (pros and cons of canary vs blue/green)
* Difference between ACID and CAP
* Difference between concurrency and parallelism
* Main problems in automations for IaaC
* A k8s related question about QoS
* Open discussion about data migration/sharing
* How would you manage in a queue structure multiple messages versions
* Open ended question about a possible cpu usage problem of a distributed pool of machines
Engineering & Architecture
At first I thought this was more about System Design, but then I found it more oriented to Software Design.
Kubernetes, Scaling, Collaboration
* Some questions about documentation and how to automatise documentation for software
* Various k8s related questions, some with a focus on storage.
* A question about CNI (e.g. calico)
The following metrics were computed from 1 interview experience for the Sysdig Site Reliability Engineer role in Milan, Italy.
Sysdig's interview process for their Site Reliability Engineer roles in Milan, Italy is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Sysdig's Site Reliability Engineer interview process in Milan, Italy.