Mews Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mews.
Mews
Backend Developer
Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Presentation Background check
Interview formats
Behavioral Technical Coding
I got referred by a friend. First, there was an HR interview, the usual stuff. Then a tech interview where they asked about my past experience and some domain knowledge. After that, I had a take-home assignment which felt fair and didn't take too much time. Then came a feedback and review stage, with questions about the assignment, what I'd improve, and some work culture topics. Finally, I got a negative response with a short feedback call. Even though I didn't get an offer, the experience was really good. I was kept in the loop about my application status, my needs were met, and everything was very transparent.
Confirmed questions1 question
- Can you explain various .Net concepts, such as DI?
Mews
Backend Engineer
Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding
The recruiting process started with 3 interviews plus a tech task. First was an HR interview, covering basic questions about my experience and why I wanted to switch companies. Next, I spoke with the CTO, who asked similar questions but with some tech context. Then, I was given a technical task, which was supposed to be realistic for a backend engineer, not just simple algorithms. After that, I had an interview with the team I'd be joining to discuss my task solution, my experience, and software engineering best practices. I thought I made a good impression, but I was rejected in the end. While that's okay, the feedback session HR mentioned as standard never happened. I tried contacting them for weeks with no reply, which left a bad impression because it seems like once you're out, no one cares. I put in a lot of time and effort, and I really wanted to know why I was rejected.
Confirmed questions2 questions
- Can you tell me about your past experience?
- What development practices do you employ?
Mews
Backend Engineer
Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Panel Offer
Interview formats
Behavioral Technical Coding
The process was pretty much what I expected: first, I had a chat with a recruiter about basic HR stuff and learned about the company's culture and values. Then, an initial technical interview where we talked about my previous job and some technical topics. After that, I had a take-home coding assignment. Next, a technical interview to discuss and justify my approach to the coding test, with some questions and suggestions. Then, the team's PM joined to talk about how they work together. Finally, I got feedback on the technical interview and received an offer a few days later.
Confirmed questions1 question
- Can you explain what immutability is?
Mews Backend Engineer Interview Questions
Quoted word for word from Mews interview reports.
“Could you add a method implementation on an interface definition?”
Read reports →“Can you explain what immutability is?”
Read reports →“What is something your friends would describe about you?”
Read reports →“Can you talk about event-driven and queue and microservices architectures?”
Read reports →“Are you aware of any security concerns in software?”
Read report →“Can you explain various .Net concepts, such as DI?”
Read report →“What are your comments or feedback regarding the homework?”
Read report →“Can you tell me about the biggest mistake you've made?”
Read report →“Can you implement a feature as part of a code challenge?”
Read report →Formats, difficulty and experience
Across all 12 Mews interview reports.