Initial 30 min chat with the recruiter. Mostly talked about the company and my experience. Was then offered a coding challenge to write an API client in Go. Their test is available on their github to see. This took me about 12 hours as I never used Go before, but happy with the experience I gained. There is no timeframe specified for completing this test. Once that was done we arranged a final 90 minute interview with 3 different people. First was code review, where the reviewer pointed at problems with my code, and I'd explain how to resolve them. Second part was some technical questions, where I royally messed up explaining how a request travels through the network stack. Finally there was a debug task where the interviewer talked me through a scenario and how I'd respond, and also talked more into detail about their on-call process. All the interviewers were great, and even while I was messing up my breakdown of the network stack the interviewer was trying to help steer me back on track and stayed positive. There was no offer because of that bad performance, but they were happy with the rest of my performance. So spruce up your Cs knowledge before an interview, and if you are also skilled developer there should be no problems.

Very transparent process, nothing secret. Recruiter explain very thoroughly what is needed and how the interview will go before it even starts. The recruiter explains very thoroughly what will happen in series of pre-interviews. Take-home exercise that is publicly available on github. However the actual interview that follows the take-home exercise feels too much like "box-checking" exercise than actual deep understanding of problems. "Have you heard about X tech, have you heard about Y tech". It does not feel difficult but also not that meaningful.