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

      M*Modal

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur M*Modal | Offres d’emploi chez M*Modal | Salaires chez M*Modal | Avantages sociaux chez M*Modal
      Entretiens chez M*ModalEntretiens d’embauche pour Software Engineer chez M*ModalEntretien chez M*Modal


      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

      26 oct. 2015
      Candidat à l'entretien anonyme
      Pittsburgh, PA
      Offre refusée
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 1 jour. J'ai passé un entretien chez M*Modal (Pittsburgh, PA) en sept. 2014

      Entretien

      Meet with a series of people, some senior and others junior. There was casual discussion about the job requirements. There was some whiteboard work regarding coding in Python and Java. There were a lot of probing questions about the background as written in the resume.

      Questions d'entretien [1]

      Question 1

      Asked to explain the software architecture of a project listed in the resume.
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez M*Modal

      Entretien pour Software Engineer

      19 juin 2015
      Employé (anonyme)
      Pittsburgh, PA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via une agence de recrutement. Le processus a pris 3 semaines. J'ai passé un entretien chez M*Modal (Pittsburgh, PA) en mai 2015

      Entretien

      I received a call from a recruiting company M*Modal uses in the Pittsburgh area back in the second week of May (a friend of mine was interviewing with the company and gave them my information). I spoke to the first representative (Gina) that told me a little about M*Modal. I was told I would get a phone call from the head recruiter within a couple days. The recruiter, Anthony, actually called same day. Due to work and school we played phone tag until the next day. Anthony and I had about a 30-minute conversation regarding what the company does, the type of environment, and the team. After the conversation, he quickly emailed me a coding sample that one of the teams at M*Modal required. It was a simple reverse string project, however I had to also use JUnit to write unit tests for my design. Once I submitted that, Anthony set up an interview with the hiring manager and team for the following week. When Anthony called me to discuss the time and date, he gave me a pretty good overview of how the company does interviews and questions they may ask. It was like getting the coaching lessons for interviews that you get back in college, but far more informative. The interview was to last 3 hours, but actually lasted about 4 and half, and was with 4 team members. First was the interview with the hiring manager. The conversation was more laid back, just discussing the company, its history, what they do, and my background (school, previous experiences). The next interviewer asked technical questions such as polymorphism, difference between interface and abstract class, and a couple other basic questions. Then he asked me to implement the high level view (architectural) of Netflix. The goal was to see my thought process, and how I iterated through designs as new requirements are introduced. I will say it was fun to do. Next, he had me implement Fibonacci’s number. I started by implementing the recursion method, which then I was asked to improve it. I made a simple map that had the number-solution as a key-value pair. After that, we discussed implementation differences of XML and JSON (I asked him his preference, etc). The third gentlemen interviewing me wasn’t expecting to do an interview that day, however it made the interview more dynamic. First we discussed my background, and where I felt most comfortable. He would ask a question, and we would have a discussion, then it would prompt him to ask another question. They were simple questions like earlier, except he asked about factory patterns and other design patterns. I was just really learning these in my master’s program, so he went easy on me. The fourth member of the team to interview with had questions that increased in complexity. He also included “theoretical questions” that do not exist in Java, but could some day. He wanted to see my answers based on other things I knew. Basically, can I piece my knowledge of how Java works to answer questions I may not know. He also asked questions regarding different versions of Java (difference between 6, 7 and 8). In addition, he and I had discussions regarding technologies that exist that he liked, I liked, and ones we mutually didn’t like. It was a nice change of pace having to try to think of an answer to something you don’t think you would know, but actually do because of other knowledge you have. Finally, the hiring manager came back in to discuss my pay requirements, benefits, and discuss more about what I would be working on. He told me I would know the following Friday (this interview was on a Friday) their decision. A week passed without any contact. I emailed Anthony, who told me he would check in. Within 30 minutes he called me to let me know they were doing an interview and he would let me know. A week passed, and I received a few other offers, but after discussions with Anthony and my interviews I felt M*Modal was the best fit. I contacted Anthony to give him a heads up, and he told me he would check in. He asked me what the other companies were offering. I received a phone call the next day before I had to give an answer to a company, letting me know they were planning on hiring me, they were just getting some information together. The following week, I received the offer (not as high as the highest offer, but close). I thought about it over the weekend, and took the offer from M*Modal. Anthony and his team always kept me updated on the process when they knew anything, and always made sure I was ready to go when needed for interviews. It was a great interview process, and the company is very passionate about what they do.

      Questions d'entretien [5]

      Question 1

      Design the architectural view of Netflix.
      1 réponse

      Question 2

      Implement Fibonacci's number, then improve on your original design.
      1 réponse

      Question 3

      Could you declare a final method in an abstract class?
      1 réponse

      Question 4

      For threading, there is Runnable and Thread, which is best to use when?
      1 réponse

      Question 5

      Difference between HashMap and HashTable
      1 réponse
      13

      Entretien pour Software Engineer

      15 juill. 2013
      Candidat à l'entretien anonyme
      Pittsburgh, PA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez M*Modal (Pittsburgh, PA)

      Entretien

      Was referred to an opportunity at MModal through a recruiter who sold me on the company and the culture, which sounded promising. The position was sold as an entry-level position with room to grow, and they just wanted "good engineers". The phone interview was pretty standard for a technical position with some high and low level CS questions. The interviewer seemed to determined to trip me up and even was mistaken on a CS question, but the recruiter relayed that I did well and wanted to set up an in-person round. The next interview was even more puzzling (literally and figuratively). 1) My interviewer was not prepared or even in the same building when I arrived and had to wait. 2) The manager/second interviewer blew off my interview for another meeting, so I never spoke to him. 3) My interview was a Java quiz. There were no questions about previous projects, likes, dislikes, or anything really about my resume. The interviewer rattled off a bunch of specific technologies that I didn't have experience with (he knew this from both my resume and phone interview). Honestly, he seemed annoyed that he had to interview me at all which leads me to believe the recruiting agency pushed to have me interviewed against the wishes of the group. Did not receive an offer: "looking for someone with more experience" was the reason given.

      Questions d'entretien [1]

      Question 1

      Have you ever worked with Hibernate?
      1 réponse
      3