Mews Software Engineer Interview Questions
& Process

I applied online directly to the company website. It's a 3 or 4 stages process. Initial hr, team meeting, and a take home project that takes 2-4 hours to complete. Almost instantly they asked me to meet for an interview. It seemed I had passed to the next stages. After that, radio silence for two weeks. A reminder email saying they are still evaluating, then refused saying I was over budget. I always made clear my salary expectations. It appears I was in the back burner until they hired someone else. I think the bad reviews I read online come for a reason.

HR Chat Technical Exercise (Real scenario, no bullshit) Exercise Defense Culture/Hiring Manager Offer (In the end I said no but not because I didn't want to but because the timing wasn't right for me) The process was quite straightforward, although a bit long (exercise + defense makes you have to spend a lot of energy on the process) Both in the technical chat and in the defense they touched on "REAL" topics and you could tell they knew and wanted to take care of the company's knowledge. I did well but besides that, I learned. They made some corrections in the exercise that, although they were nitpicking, helped me improve some ways I had of aborting certain parts of the logic.

This was a 3-round interview process with one home assignment, and the whole thing took over 3 months. Recruiters were usually silent for over a week after each step. They rescheduled rounds a few times, one time by two weeks. The first was a 30-minute intro call to see how we'd fit. Then, a 1-hour call with the hiring manager, with general questions and time for me to ask about the team, company, and engineering culture. After that, a take-home test due in 7 days, which is public on their MEWS GitHub repo. It required a lot of effort, probably more than other candidates put in. The final round was a technical interview with a senior dev and manager from the target team to discuss the take-home assignment. They also asked some technical questions about React and server response memorization. The vibe was friendly, not pressured, and we had a good chat. My questions were all answered. I got feedback the next day and a short feedback session a few days later. The feedback wasn't super clear, but the chat was good. I liked the calls, but the month-long silence after the test, long waits between rounds, and unclear feedback made it a negative experience. I wouldn't recommend interviewing there.