Software Developer applicants have rated the interview process at MathWorks with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 38% positive. To compare, the company-average is 65.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 72 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at MathWorks overall takes an average of 29 days.
Common stages of the interview process at MathWorks as a Software Developer according to 8 Glassdoor interviews include:
Phone interview: 23%
One on one interview: 23%
Group panel interview: 15%
Presentation: 15%
Skills test: 8%
Other: 8%
Background check: 8%
Here are the most commonly searched roles for interview reports -
I was given HackerRank Challenge for 120 mins with two problems. Other section included MCQs based on data structure and algorithms. I did not get a call back. I am assuming i was late to apply and the position was filled since they never got back to me.
Technical coding assessment given on online platform. Plenty of time for assessment, easy and medium difficulty questions. A series of questions about my experience for which I recorded a video response
Interview questions [1]
Question 1
Do you have any experience with object oriented programming languages
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.
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?”