Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      M*Modal

      Questa è la tua azienda?

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su M*Modal | Offerte di lavoro di M*Modal | Stipendi di M*Modal | Benefit di M*Modal
      Colloqui di M*ModalColloqui per Software Engineer presso M*ModalColloquio di M*Modal


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Software Engineer

      5 ott 2013
      Dipendente anonimo
      Pittsburgh, PA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 giorni. Ho sostenuto un colloquio presso M*Modal (Pittsburgh, PA) nel mese di giu 2012

      Colloquio

      My first experience with the interview process with M*Modal was a short half hour phone call with my future manager. After that, she sent me a simple software problem to be done in an hour regarding a directed graph with certainty values and how to safely eliminate nodes that dropped below a given threshold without creating dangling nodes in memory. The code was C++ with usage of pointers, classes, and one or two proprietary libraries. She remained available for questions via email during the time I was doing the problem. Afterwards, based on my results, I was brought in for an on-site interview. While there, I was hospitably shown around the facility and provided coffee. While there, I talked with three of the engineers that I would work with as well as my manager. My initial impression was that communication would be an issue. Three of the engineers had strong accents from different nationalities and the one person without an accent spoke in a clipped awkward shorthand common to technical people not necessarily happy with being part of the interviewing process. While there, there was the usual discussion of what stacks and heaps meant (which I addressed in terms of memory, only to find that they were asking about the data structures), inheritance, and what the company did and how my division would fit in. It was overall a pleasant experience that gave me a good overview of the sort of driven technical people I would be working with. I think that I met briefly with one member of HR, but there was no meeting with management above that of my division.

      Domande di colloquio [1]

      Domanda 1

      I was given a brief explanation of Hidden Markov Models and Gaussian (which confused me at first because my interviewer pronounced it differently) curves and how they related to our business approach. I was then asked to make suggestions as to how the process could be improved. It was very open-ended, which was good in that there were technically no wrong answers, but not so good in that there were, of course, correct answers and the person I was talking with had a good poker face, showing no sign of how I was doing.
      1 risposta

      Altre recensioni di colloqui per Software Engineer presso M*Modal

      Colloquio per Software Engineer

      19 giu 2015
      Dipendente anonimo
      Pittsburgh, PA
      Offerta accettata
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso M*Modal (Pittsburgh, PA) nel mese di mag 2015

      Colloquio

      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.

      Domande di colloquio [5]

      Domanda 1

      Design the architectural view of Netflix.
      1 risposta

      Domanda 2

      Implement Fibonacci's number, then improve on your original design.
      1 risposta

      Domanda 3

      Could you declare a final method in an abstract class?
      1 risposta

      Domanda 4

      For threading, there is Runnable and Thread, which is best to use when?
      1 risposta

      Domanda 5

      Difference between HashMap and HashTable
      1 risposta
      13

      Colloquio per Software Engineer

      26 ott 2015
      Candidato anonimo a colloquio
      Pittsburgh, PA
      Offerta rifiutata
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto un giorno. Ho sostenuto un colloquio presso M*Modal (Pittsburgh, PA) nel mese di set 2014

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Asked to explain the software architecture of a project listed in the resume.
      Rispondi alla domanda

      Colloquio per Software Engineer

      15 lug 2013
      Candidato anonimo a colloquio
      Pittsburgh, PA
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso M*Modal (Pittsburgh, PA)

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Have you ever worked with Hibernate?
      1 risposta
      3

      Le migliori aziende per "stipendio e benefit" vicino a te

      avatar
      World Health Organization
      4.3★Stipendio e benefit