This was a rather lengthy, but overall pleasant process, taking about 1.5 months. This was partially due to it occurring during the Christmas period.
I expected more LeetCode-style problems for the coding part, but it was more focused on software design, discussing trade-offs, talking about concurrency, and seeing the bigger picture of how the component would be used.
The recruiter on the Miro side was super helpful and reactive. Big kudos to him for making this process transparent and pleasant to follow. Interviewers on the company side were mostly pleasant. There was one interview that I thought I bombed (System Design), but later learned that I did very well on it. I believe I just misread the communication style of the interviewer.
Altogether, I really liked how involved everybody was during the interviews. Everybody I was able to talk to through acquaintances who work at Miro seemed genuinely enthusiastic about what they are building there. That was also the reason I went for Miro over other offers I received at the same time.
Create a component that manages message delivery in a concurrent setup.
Behavioral interviews:
System Design:
The following metrics were computed from 1 interview experience for the Miro Staff Engineer role in Amsterdam, Netherlands.
Miro's interview process for their Staff Engineer roles in Amsterdam, Netherlands 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 Engineer interview process in Amsterdam, Netherlands.