Les candidats postulant à un poste comme Software Engineer chez MathWorks attribuent un niveau de difficulté de 3 sur 5 (5 étant le niveau de difficulté le plus élevé) à leur expérience d’entretien et sont 100 % à l’évaluer comme positive. À titre de comparaison, la moyenne pour l’ensemble de l’entreprise est de 77,8 % d’avis positifs, d’après les évaluations Glassdoor.
Voici les rôles les plus recherchés pour les rapports d’entretien -
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez MathWorks en janv. 2014
Entretien
The process consisted of a phone screen with an Engineer. I was essentially asked java trivia. E.g. what does it mean to define a class with the keyword protected, etc. It seemed like you needed to get all or most of these correct to move to the next round.
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
Questions d'entretien [1]
Question 1
Do you have any experience with object oriented programming languages
J'ai postulé en ligne. J'ai passé un entretien chez MathWorks
Entretien
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
Questions d'entretien [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
Questions d'entretien [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?”