mthree Software Development Engineer SDE interview questions
based on 7 ratings - Updated May 11, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
50%
Campus Recruiting
Campus Recruiting
25%
Other
Other
25%
Applied online
Applied online
Interview search
7 interviews
Viewing 1 - 5 of 7 Interviews
mthree interviews FAQs
Software Development Engineer SDE applicants have rated the interview process at mthree with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 61.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Development Engineer SDE roles take an average of 56 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at mthree overall takes an average of 18 days.
Common stages of the interview process at mthree as a Software Development Engineer SDE according to 1 Glassdoor interviews include:
Background check: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
it was mainly focused on networking fundamentals and DSA. The interviewer asked questions like the difference between TCP and UDP, HTTP vs WebSocket, and some coding problems based on arrays and strings. Overall, the interview was moderate and focused more on fundamentals and problem-solving ability.
Round 1 : Resume shortlisting
Round 2 : APPTITUDE test
Round 3 : Coding Round
Round 4 : tech interview 1 (in this they ask questions related to sql and projects and oops)
Round 5 : techincal + HR interview
I applied through college or university. The process took 4 months. I interviewed at mthree (Amravati) in May 2025
Interview
I joined the interview on time, and the interviewer initially asked me to share my screen, which I did. She began by asking me what a Singleton class is, but before I could respond, the interview got interrupted due to a brief internet issue on my end.
After reconnecting, I shared my screen again and asked if I should continue with my previous answer, but she moved on and asked a new question about the difference between an abstract class and an interface. I answered with 3–4 valid points. She then asked me about encapsulation and normalization along with its forms — all of which I responded to confidently.
However, throughout the interview, it felt like the interviewer was distracted, possibly using her phone. There were noticeable pauses after I answered each question, and I had to repeatedly ask if I was audible. At one point, after receiving no follow-up, I ended up repeating an answer just to fill the silence. Eventually, she just said “okay, thank you” and ended the call. The entire session lasted no more than 5–10 minutes, and only three questions were asked.
I was disappointed because I had put in a lot of effort to prepare. Despite answering everything confidently, the lack of engagement from the interviewer made it feel like my efforts weren’t truly evaluated. This kind of inattentiveness during interviews not only affects the candidate’s morale but could also lead to missed opportunities for skilled individuals.
After the session ended, I asked if I could still answer the earlier interrupted question, but she simply said “it’s okay.” When I requested feedback, she responded with “you’ll know when the results are out.”
I hope future interviews are conducted more attentively, as it’s not just a formality for candidates — it’s about our careers.