Preguntas de entrevista para Customer Success Engineer de MuleSoft

Actualizado el 5 ago 2019

Para filtrar entrevistas, o .
Se encontraron 4 de más de 377 entrevistas

Entrevistas en MuleSoft

Experiencia
Positiva100%
Cómo obtener una entrevista
Postulación en línea50%
Reclutador25%
Recomendación de empleado25%
Dificultad
3,5
Promedio
DifícilPromedioFácil

MuleSoft

Empleado anónimo en München, Bavaria

Oferta aceptada
Experiencia positiva
Entrevista promedio
Solicitud

Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en MuleSoft (München, Bavaria) en jul 2019

Entrevista

I applied for this position in the Munich office. The interview process consisted of 4 rounds with 4 phone interviews and one on-site panel presentation. The interviews were mostly around personality together with cultural fit and also my background in integration development and previous working experience. They were also very interested in my motivation for MuleSoft and Salesforce. The complete interview process was split into 4 rounds: Round 1: Call with recruiter A relaxed 30-minute phone call with my recruiter - who was going to be my contact person during the whole process - about CV, motivation and general fit for the role. The recruiter also provided me with an update during and between all rounds. Round 2: Call with hiring manager A 60-minute video call with the hiring manager about motivation, working experience, handling different situations and again cultural fit. The first 30 minutes the hiring manager asked questions and the second 30 minutes I had the opportunity to ask questions about the company, role, team, etc. Round 3: Interviews with other team members 60-minute technical interview with a Customer Success Architect mainly about web services, software development, error handling and performance issues to check my technical knowledge. Again 30 minutes questions from the interviewer and 30 minutes to ask all sorts of questions. 60-minute consulting interview with a Customer Success Manager about how I would handle different customer situations and how I would approach customers. Again 30 minutes questions from the interviewer and 30 minutes to ask all sorts of questions. Round 4: On-site panel presentation They sent me an integration case with very loose requirements where I should build an integration scenario using MuleSoft and prepare a 20-minute presentation assuming I would present to a customer. In total, I had 3 weeks to work on the panel presentation. The 60-minute panel presentation (20 min presentation, 10 min Q&A, 30 min to ask questions) took place in the Munich office. All in all it was a very long but also very interesting and rewarding process. I enjoyed every step of the process and I am very much looking forward to joinig this great team soon.

Preguntas de entrevistas
  • Tell me about a time you had convince a customer/team member.
    Responder pregunta
  • How would you handle different customers?
  • Why do you want to join MuleSoft?
Sé la primera persona en mencionar que esta entrevista es útil

MuleSoft

Empleado anónimo en Alpharetta, GA

Oferta aceptada
Experiencia positiva
Entrevista difícil
Solicitud

Me postulé a través de un reclutador. El proceso tomó 7 semanas. Acudí a una entrevista en MuleSoft (Alpharetta, GA) en jul 2017

Entrevista

Overall, I found the MuleSoft interview process incredibly transparent. I was actively interviewing with multiple companies, and MuleSoft stood out in large part because of how the recruiter kept me abreast of where i was in the process. The interview process is also outlined in detail on MuleSoft’s careers page under “Interviewing”. My process from initial contact from a recruiter to offer received was approximately 7 weeks with multiple phone interviews and an all day on-site interview. I actually declined an offer from another company mid way through. Even before initial contact, I had happened to come across a whitepaper, “The Top 6 Microservices Patterns" published by MuleSoft. I hadn’t heard of MuleSoft, so curiosity propelled me to dive a little into what the company did, their product. As it turned out, their platform was in use in a project that I was tangentially related to. Initially, a recruiter from MuleSoft reached out to via LinkedIN messaging, and we scheduled a 45-minute call and discussed the what MuleSoft does, the Customer Success Engineer role and job description, my experience at previous companies, and how I might fit into the role. This led to another phone call with the hiring manager, Director of Customer Success. We covered similar topics, but delved deeper into my experiences specific situational questions and deeply into accomplishments at my previous company. The dreaded salary question came up, but I was assured that MuleSoft’s compensation was highly competitive. We also discussed availability for travel. I probably could have talked to him forever, but we kept the discussion at about an hour. Next, were a pair of 45-minute phone interviews with two of the hiring manager’s peers, the Director of Customer Success Architecture and a Customer Success Architect. The Director of Customer Success Architecture’s questions learned more behavioral and situational while the Customer Success Architect’s questions focused more on technical specifics of the accomplishments I outlined in my resume. We did get into “1s and 0s” on several of my highlighted accomplishments, recalling how the implementation was done. They were back-to-back phone calls, so I consciously gave myself a 15-minute buffer in between. As I mentioned, I was actively interviewing with other companies at the time, and I received an offer. I shared this with the recruiter. The recruiter shared the value proposition of sticking the process through, and an estimate of how much longer the process would take. My expectations weren’t that the process would change or be short-circuited to accommodate me. I wanted to gauge where I was in the process. I at least knew that I would be proceeding to the onsite. Suffice it is to say that I declined the offer from the other company. The onsite interview was kind of fun. I was asked to build an application using MuleSoft’s AnyPoint Studio, with some fairly loose requirements, and present it to 3 members of the local customer success team, including the hiring manager. A group of 6 members of the local customer success team attended (Architects, Managers, and a Director), plus 1 Director dialed in remotely, all of which provided for an interesting and dynamic conversation. My application design choice was scrutinized, and so I had to defend or concede design choices, where things could be improved, and what v2.0 would look like. The onsite also included a quick 30 minute car ride, to-and-from Starbucks. This was a welcome break from the presentation, and gave me a chance to just get to know two of the people who I might get to work with in a low-pressure situation. Next, I had to opportunity to speak with the VP of Customer Success. His queries were exclusively behavioural and situational, specifically around my interactions, face-to-face with customers. During the phone call, part of the office erupted in cheers. The VP explained to me that it was likely the always exuberant Account Development Representatives. I took note of that. That teamed seemed incredibly happy and highly motivated to be there. That sort of atmosphere is infectious, and one i wanted to be a part of. After that, I circled back with the hiring manager. We had about an hour plus conversation. This was more of an opportunity for me to ask questions, and get to know the company, culture, and work environment. Unsurprisingly, over the course of the four phone interviews, no item on my resume was left unscrutinized. I feel that it is as important for a candidate to scrutinize an opportunity, as it is for a company to scrutinize a candidate.

Preguntas de entrevistas
A 2 personas les resultó útil esta entrevista

MuleSoft

Empleado anónimo

Oferta aceptada
Experiencia positiva
Entrevista promedio
Solicitud

Me postulé en línea. Acudí a una entrevista en MuleSoft

Entrevista

I applied for this position in the San Francisco headquarters. The interview process was 4 phone screens and one day of on-site interviews with a presentation (of a project they had me work on). Interviews were mostly around cultural fit and my background in integration development. They also were interested in my motivations and why I was interested in joining the company. Finally they had questions around my familiarity with the product and its competitors. For the presentation, I had one week to work on an MuleSoft integration and they gave me free reign on what I wanted to do. During the on-site portion, I had to present and demo this to my hiring manager (Customer Success Director) and architect. They were looking for what problem I was trying to solve and how I utilized the product to solve it. Overall it was a very positive experience and I had a great time talking to each interviewer. In addition, the recruiter was awesome and honest about where we were in the process. He would call me personally to update me on the status instead of emailing, which made it very personable.

Preguntas de entrevistas
  • What are some ways you would scale this integration to work with a high load?
A 5 personas les resultó útil esta entrevista

MuleSoft

Candidato de entrevista anónimo en Atlanta, GA

Sin oferta
Experiencia positiva
Entrevista difícil
Solicitud

Me postulé a través de una recomendación de un empleado Acudí a una entrevista en MuleSoft (Atlanta, GA) en may 2017

Entrevista

I was contacted by the Recruiter via LinkedIn, and an initial phone screening was scheduled. After I spoke to the Recruiter, a phone interview with the Director of Customer Success was scheduled. The call went well and I was invited to a recruiter dinner event. The event was a great experience, which allowed me to learn more about the company and meet many key members of the company. I was then scheduled for two additional phone interviews with different Solutions Architects. After the second phone interview with a Solutions Architect, the communication slowed down. I was then contacted with the news that the company was going to adjust the job description to look for someone more along the lines of a Software Engineer. This was not part of the original job description. This was really disappointing, because at this point I was really excited about the position. Then a few weeks later, the Recruiter contacted me again to tell me they had once again changed their mind. They decided that they have Software Engineers, and that should not be a requirement for this position. I was invited to once again continue with the interview process, which I accepted. I was asked to create a unique MuleSoft application, using a descriptive document I was provided. It was up to me to use any available resources online to learn the MuleSoft Anypoint Studio and create the application. Once I had the application completed, I was to come in for a face-to-face interview for half of a day. I would meet with two gentleman for coffee in the morning, meet with the VP for a 45 minute one-on-one, and then present my application to three gentleman over a 30 minute period. However, during the period where I was told they were going in a different direction, I began interviewing with other companies. Before I came in for the final round of the interview process, another company made me a very good offer and I decided to go with them. Had that change in job requirements not have happened, I would have likely accepted an offer from MuleSoft. However, due to that, another opportunity came along and I went that route.

Preguntas de entrevistas
  • Create a MuleSoft application using Anypoint Studio and present it to a panel of MuleSoft employees
Sé la primera persona en mencionar que esta entrevista es útil
Canal de RSS</>Insertar

Oportunidades laborales populares entre las personas que buscan empleo en MuleSoft

Software Engineer
EmpleosSueldosEntrevistas
Senior Software Engineer
Software Engineer (All Levels)
Software Developer
Solutions Architect
Principal Software Engineer
Software Engineer(Internship)

¿Trabajas en MuleSoft? Comparte tus experiencias

MuleSoft logo
o