Miro Product Manager Interview Questions
& Process

The interview process was thorough yet never redundant. It was evident that each interview built upon the previous one, eliminating the need to retell my story from scratch each time. Each interviewer had a specific focus, and the atmosphere during the interviews was consistently professional. It was more like a conversation between peers rather than a formal interviewer-interviewee dynamic. The given exercise was clear and allowed for flexibility in approach. The effort was justified given the role. One of the most positive aspects was the recruiter's transparency throughout each step of the process. They proactively followed up after each round and even provided feedback, which was positively surprising. I never felt any shenanigans or hidden agenda throughout the process. People involved were open about the process, salary, and role expectations. Overall, it was an excellent hiring experience.

Miro takes the PM role very seriously since they're a product-led company. Expect a thorough, high-bar process with multiple stages. What stood out was how friendly everyone was and how genuinely interested they were in me and my work. Product, Design, Marketing, Engineering – all interviewers reviewed my assignment and asked relevant questions. Even the Founder/CEO looked over my assignment and was curious about my decisions. In short, put in the work, and trust they will too. Even before the offer, the process felt fair and equitable. Stages: HR - Hiring Manager (Head of Product) - Assignment - Panel 1 (present assignment) - Engineering collaboration - Hiring Manager from another department - Founder/CEO - 2 referral check interviews.

The interview process included an HR screen, a chat with the Hiring Manager (who is a peer PM), a filmed case interview via Loom, a second case interview with two peer PMs, and then 4 separate 1:1s with people like the Head of Growth and an engineering lead. My experience was decent until the case interviews. The case question felt very technical, and I was unsure about the expected technical depth for a PM role. I've done many case interviews before, but never one like this. They marked me down for not knowing some specifics about their current product (even though I did research, I didn't find every single feature) and also for not considering things that weren't explicitly mentioned in the case.