In general, the interview process was a very good experience. Everyone was really nice, and the questions allowed me to show skills that were relevant to the position. There were multiple technical interviews along with a couple of HR interviews. In total, I did 7 interviews for the position.
You receive a map which is a list of lists of integers. All integers are 0 or 1. Tiles with a 0 show that this tile represents water, tiles with 1 represent land. Consecutive blocks of land are called islands. For every land tile you have a "black box" function that returns all neighboring tiles that are also land. We want to count how many islands are there
This interview had multiple smaller questions regarding my technical background and how I would respond in various situations.
What big problems have you solved in a backend in the past?
You receive an alert in PagerDuty and it's warning you that one of our database instances is getting a very high CPU load. What do you do? Where do you start looking?
API server is not responding any more. How do you debug that?
API server responds slower than usual. What then?
Your entire infra becomes slower in production. How do you deal with it? Canary deployments?
You are building a mobile client and you want to upload/serve images to it. You want to make sure that clients are not showing any images that are corrupt.
The following metrics were computed from 1 interview experience for the Sysdig Backend Engineer role in Munich, Germany.
Sysdig's interview process for their Backend Engineer roles in Munich, Germany is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Sysdig's Backend Engineer interview process in Munich, Germany.