Mews Frontend Engineer Interview Questions
& Process

I applied as a mid-level developer. The whole thing took about 3 weeks and involved about 165 minutes of meetings plus some homework. The first round was with HR for about 30 minutes, where they asked about Mews, you, your past work, what you expect salary-wise, and how you learn stuff. The second round was a 60-minute chat with the engineering manager. It was mostly about introducing yourself, discussing your experience, what you're most proud of learning, and the engineering teams. If you've hopped jobs a bit, they'll ask why. Then came the homework, which took me several hours. The fourth step was a 75-minute technical round with two developers. This was the most frustrating part for me. They didn't seem to know anything about what I'd already shared in earlier rounds, so I had to repeat myself for a third time. After that, there were over 20 scripted questions about soft skills, JavaScript, React, and TypeScript, which felt really generic. We only discussed my homework for about 10 minutes, and they just said it looked good. I got rejected via email after this round, with them saying I didn't defend my solutions well enough, some answers were weak or forgotten (even though they said it was okay not to know everything), and my task wasn't up to par, without explaining the specific standard. It really felt like they treat you like just another applicant, making the process disorganized and impersonal. It also felt like a one-way conversation most of the time, not like a real chat. Hope this helps them improve things for future candidates. Good luck!

I applied for a remote job and the interview was remote too. The whole process was super quick, just a few days between each step. There were 3 stages in total. First, a quick informal chat with a recruiter. Then, a 1.5-hour technical discussion with the dev team about problem-solving, process optimization, and tool choices. No coding tests or anything like that. Finally, I had a call with the entire team where we talked about team processes, they told me more about the product, and asked some tech and teamwork questions. It was a really friendly chat!

The interview process began with a recruiter call to discuss my background and the role. Next, there was a cultural fit interview focusing on company values and my alignment with them. Following that, a technical interview delved into my experience and technical concepts. A week-long take-home assignment involved a frontend task using an external API, which was clear and well-structured. The final interview was with the Engineering Manager and an Engineer. This last stage felt a bit mixed, starting with some cultural questions similar to earlier stages, then a brief review of the take-home assignment with specific questions, and concluding with a technical concepts quiz which took up most of the time. I was a bit surprised by the focus on concepts instead of a deeper dive into the assignment I worked on for days. Communication could have been better, with slower responses and unanswered clarification emails. While the Mews team is great, the interview process structure and communication clarity could be improved for a better candidate experience.