Stages:
1. 30-min greeting call with an external recruiter to review your and the company's profile.
2. Tech task: you have 1 week to develop a fully working API with clean code and architecture. There were 3 calls to implement: 1 POST and 2 GETs. Also, there is a Producer-Consumer topic present, where one service creates a job and another service (or BackgroundWorker in .NET) consumes it. Additionally, there is a list of requirements such as "must do the proper logging". Quite a heavy exercise, you will have to commit a lot of hours to do it properly.
I made an ASP.NET Core (.NET 5) API with the Domain-Driven Design (DDD).
3. 1h-long call with a Team Lead and a Senior DevOps engineer. First, you discuss your solution with them, what decisions you made, what to improve. Then they ask you about your experience, what tech stack you worked with.
4. "Something off" stage. First, it was meant to be a 30-min talk with the CTO, which did not happen because the interviewer got sick. Then, I was told to do such an interview with 2 members of my potential team, that one did go. I was told there was nothing to prepare, and it was just talking. It turned out to be a set of very generic questions (see an example below), and I got rejected. I kept asking "Does that make sense?" and "Does that answer your question?", that helped to stay connected with the interviewers, and got "yes" as an answer multiple times. The rejection reason is: "vague answers", which does not make sense to me on its own, nor on how it is related to the work environment.