Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      MathWorks

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur MathWorks | Offres d’emploi chez MathWorks | Salaires chez MathWorks | Avantages sociaux chez MathWorks
      Entretiens chez MathWorksEntretiens d’embauche pour Software Engineer chez MathWorksEntretien chez MathWorks


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      29 avr. 2022
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez MathWorks

      Entretien

      What I learned from this experience is to get clarification on what the position *really* is before committing several hours to a take-home coding assignment. I applied for a Software Engineer position with a Bachelor's under Requirements and C++ knowledge under Preferred. I was contacted a couple weeks later directly by an engineer that asked me to implement a class and unit tests and submit it within 5ish days. Ok, sounds interesting. The engineer responded to a couple clarification questions I asked but when I followed up with a few more, they essentially responded "it's up to you" and I got the impression they would not prefer any more clarification questions. With the absence of direction, I made some assumptions while writing the code (this is important later). Keep in mind, I still have not spoken with an HR person/team lead/someone who usually tells me about the role itself, the team, and the company. Just straight to this coding assignment. After submitting the assignment I quickly get a response to schedule a phone interview with the same engineer to go over the code. The interview is where my interest in the role went very much downhill. The engineer and I went through my code and they pointed out several legitimate areas where my code could have been improved, which was good. However, the engineer also harped on how my code had bugs, when these “bugs” were the intentional but incorrect assumptions I made after getting the non-committal response to my questions. As well, the engineer insisted for a period of time that my code shouldn't be compiling due to the way I declared a function. I did not know how to respond to this as the code was in fact compiling just fine and I had verified the way I declared it with several online examples. I realized by the end that if I got an offer and started working with this engineer, it wouldn't be "a good fit" as they say. Also, the apparent goal of this engineer's group was, er... boring, and not worth switching jobs for. The engineer only went through this aspect at the end of the call. Confirming my suspicions, I received a rejection email about a day later. The only loss here was, regrettably, my time in doing the take-home assignment.

      Questions d'entretien [1]

      Question 1

      Implement a C++ class along with unit tests - take-home.
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez MathWorks

      Entretien pour Software Engineer

      16 mai 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez MathWorks

      Entretien

      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
      Répondre à cette question

      Entretien pour Software Engineer

      5 janv. 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      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.
      Répondre à cette question

      Entretien pour Software Engineer

      2 déc. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez MathWorks

      Entretien

      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?”
      Répondre à cette question
      1