The Interview Process There are 4-5 rounds: Recruiter, Live Coding, System Design, Hiring Manager, and possibly a team interview. The recruiter round covers standard questions about your expectations, salary, notice period, and proudest achievement. The live coding round involves solving canvas-related problems using Miro's own code block tool. The problems are straightforward. The Problem Even if you solve everything correctly and explain your solution well, they may still reject you. Why? Because some of their job posts don't actually exist. How I Found Out I applied for a Miro job in late 2025. The position had already been open for a month when I applied, yet they only invited me to interview in March 2026, five months later. That same job is still posted today and keeps getting reposted. That was the first red flag. I passed the live coding round. One of the interviewers even acknowledged that I solved the problem correctly, with both a generic and an optimal solution. A few days later, Miro sent me a survey about the interview process, focused specifically on their live coding tool. When I didn't respond, one recruiter followed up. Then another one did. I'm not the only one who experienced this. A friend of mine went through the same interview process for the same position. He also solved all the problems completely and still got rejected right after the live coding round. That's when it clicked. The job has been open for 6 months in a market where that role isn't hard to fill. They pushed hard to get feedback on their live coding tool specifically. Based on all of this, I believe Miro is using fake job posts to test and collect feedback on their live coding tool, likely to eventually release it as a product feature for other companies.