Surprisingly well, the product is considering the terrible processes across the organization.
Miro represents modern Russian values: achieving small victories at any cost. There is no hierarchy, but a group of product managers who try to come up (or more likely steal) an idea similar to other real-time boards, and then promise the C-level executives that it can be done in one month. There is no planning, estimations, or anything close to agile processes. Shenanigans and lies are common practices in communication across all levels of the organization. You will get dozens of messages after hours from your manager asking if you can work throughout the whole night on a feature that they promised to their boss, but don't expect you'll ever be recognized for your efforts.
You listen only to the reports you want to listen to. A lot of Slido questions remain either unanswered or simply lied upon. Try collecting the feedback from linear engineers, not the product managers who try hard to look good, ruining the lives of the team that they consider their personal slaves for some reason.
After applying, I received a message stating 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.
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.
The process was divided into several interviews, including live coding challenges, a technical interview, system design, and culture fit & soft skills. First, I had a call from a recruiter who works for Miro. Later, the first interview was scheduled
After applying, I received a message stating 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.
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.
The process was divided into several interviews, including live coding challenges, a technical interview, system design, and culture fit & soft skills. First, I had a call from a recruiter who works for Miro. Later, the first interview was scheduled