Software Engineer applicants have rated the interview process at Miro with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 63% positive. To compare, the company-average is 63.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 19 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at Miro overall takes an average of 28 days.
Common stages of the interview process at Miro as a Software Engineer according to 8 Glassdoor interviews include:
Phone interview: 30%
Skills test: 20%
Background check: 10%
Personality test: 10%
One on one interview: 10%
Group panel interview: 10%
Presentation: 10%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 1 week. I interviewed at Miro (Amsterdam) in Feb 2021
Interview
30 minutes call with a recruiter then take-home test. The take-home test is long. I received two lines of feedback, saying that it worked well but the API was not correctly implemented.
As this was a frontend test for an isolated component running locally, I still have no idea what it's supposed to mean.
The interview was quite challenging, but it provided a great opportunity to demonstrate my problem-solving skills. The live coding session was particularly engaging, allowing me to showcase my approach to coding under pressure.
They use Miro for every step of their interview. It will be better to create couple boards to get familiar with it before interview. Otherwise everything was similar to other firms.
I applied online. The process took 3 months. I interviewed at Miro
Interview
After applying, I received a message saying that each of the five stages would take 7-10 business days. Around a month after this, I received a hackerrank test, on which I did not score perfectly. After another month, I received a rejection email. I believe the rejection was fair, but the 7-10 business days mentioned in the first email were misleading.
Interview questions [1]
Question 1
Hackerrank test with simple algorithmics challenge