The interview process started with an initial system design exercise. Following that, there was a coding challenge, and lastly, a few behavioral interviews with the hiring manager, the head of engineering of the stream, and the head of engineering of the company.
The entire process lasted about a month. I found the process to be extremely well-organized and executed. At each step, the recruiting team prepared me for who I was going to meet, how they related to the role for which I was interviewing, and the kinds of things they would be looking for during the interview. There was also plenty of preparation material to review at each step.
System design - design/architect a system proposed by the interviewer.
Coding challenge - write some code to solve some specific real-world requirements. Note that this was not a LeetCode-style "solve this tricky algorithm" question. There is no single "correct" solution, and you will need to make decisions and be expected to justify them.
Behavioral - standard questions to assess leadership experience, ability to work with a team, ability to deal with failure, priorities, other challenges, ability to learn, grow, and drive change, etc...
The following metrics were computed from 1 interview experience for the Miro Staff Software Engineer role in Berlin, Germany.
Miro's interview process for their Staff Software Engineer roles in Berlin, Germany is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Miro's Staff Software Engineer interview process in Berlin, Germany.