Software Developer applicants have rated the interview process at MathWorks with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 48% positive. To compare, the company-average is 55.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 17 days to get hired, when considering 186 user submitted interviews for this role. To compare, the hiring process at MathWorks overall takes an average of 20 days.
Common stages of the interview process at MathWorks as a Software Developer according to 186 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 13%
Skills test: 13%
Presentation: 11%
Background check: 7%
Group panel interview: 5%
Personality test: 4%
Drug test: 3%
IQ intelligence test: 2%
Other: 1%
Here are the most commonly searched roles for interview reports -
Multiple coding assessments online, with browser use monitored to prevent cheating. The online environment had no linting or suggestions, so you need to know the correct syntax and function names for your selected programming language
Interview questions [1]
Question 1
Generally was string handling and mathematical puzzles they had contrived.
I applied online. I interviewed at MathWorks (Bengaluru) in Oct 2025
Interview
The interviewer himself doesn’t seem to have knowledge of mathematical algorithms. He hasn’t heard of basic numerical concepts such as floating-point precision or exact computation with rational numbers. I’m not sure how he became a team lead or how he provides feedback to others.
Interview questions [1]
Question 1
They informed me that the questions would come from numerical algorithms. However, they didn’t mention any specific topics, so it felt very abstract.
The interview process included an initial HireVue behavioural assessment, followed by a timed technical test with algorithmic questions. After that, I had a interview where I walked through my CV and answered scenario-based questions
Interview questions [1]
Question 1
“Can you walk me through your CV and highlight the most relevant projects?”
“Why are you interested in joining our organisation and this role specifically?”
“Describe a time you made a mistake at work. What did you learn from it?”
“What technical challenges have you faced recently, and how did you solve them?”
“How do you usually gather and validate requirements from stakeholders?”