M*Modal logo

M*Modal Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 8 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at M*Modal.

Showing 3 of 8
M*Modal logo
M*Modal

Senior Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Decline offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Technical Coding

I had two technical interviews. The first one was with my potential manager, and the second one was with a lead engineer and another senior engineer. Both interviews involved solving algorithm problems. During the manager interview, we also discussed code quality, focusing on readability and maintainability. The interview with the lead engineer was a bit more challenging and concentrated on finding efficient solutions.

Confirmed questions1 question
  • The last algorithm question involved solving the backpack problem, but with some additional, non-standard parameters included.
M*Modal logo
M*Modal

Software Engineer

Engineering

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Onsite Background check Offer
Interview formats
Technical Coding Behavioral Presentation

I started with a brief 30-minute phone chat with my manager. Then, she gave me a coding challenge to complete in an hour. It involved a directed graph with certainty values and how to get rid of nodes below a threshold without messing up memory. The code needed to be C++ using pointers and classes, plus some internal libraries. She was available by email for questions while I worked on it. Based on my submission, I was invited for an on-site interview. They gave me a tour and coffee. I met with three engineers I'd be working with and my manager. There were some communication style differences due to accents and brevity, but it was a good overview of the team. We discussed tech stacks, memory, data structures, inheritance, and the company's work. I might have briefly met HR, but no higher management.

Confirmed questions5 questions
  • After a brief explanation of Hidden Markov Models and Gaussian curves and their business relevance, how would you suggest improving this process?
  • Can you explain stacks and heaps regarding both memory and data structures?
  • What is inheritance?
M*Modal logo
M*Modal

Software Engineer

Engineering

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding Behavioral

Got referred to MModal by a recruiter who told me a lot about the company and their culture, which sounded great. The job was described as an entry-level Software Engineer role with opportunities to advance, and they were looking for "good engineers" in general. The first interview was a phone call, pretty typical for a technical role, covering both fundamental and more specific computer science topics. It felt like the interviewer was trying to find fault, even making a mistake on a CS question himself. However, the recruiter said I did well and wanted to schedule an in-person interview. The next interview was quite confusing. First, the interviewer wasn't ready and wasn't even in the office when I arrived, so I had to wait. Second, the manager who was supposed to interview me had another meeting and missed it, so I never got to speak with him. Third, the interview was essentially a Java quiz. They didn't ask about my past projects, preferences, or anything from my resume. The interviewer asked about specific technologies I didn't have experience with, even though he knew this from my resume and the phone interview. He seemed irritated to be interviewing me, suggesting the recruiting agency pushed for this interview against the team's preference. I didn't get an offer, with the reason given being that they were "looking for someone with more experience."

Confirmed questions1 question
  • Do you have any experience with Hibernate?

M*Modal Software Engineer Interview Questions

Quoted word for word from M*Modal interview reports.

Is it permissible to declare a final method within an abstract class?

Read reports

Regarding threading, when would you choose to use Runnable over Thread?

Read reports

Can you explain stacks and heaps regarding both memory and data structures?

Read report

After a brief explanation of Hidden Markov Models and Gaussian curves and their business relevance, how would you suggest improving this process?

Read report

Formats, difficulty and experience

Across all 8 M*Modal interview reports.

Interview formats

Technical 33.3%
Behavioral 29.2%
Coding 25%
System Design 8.3%
Presentation 4.2%

Interview difficulty

Easy 0%
Average 87.5%
Difficult 12.5%

Candidate experience

Positive 62.5%
Negative 25%
Neutral 12.5%