J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez MuleSoft (San Francisco, CA) en juin 2015
Entretien
Had one telephone screen. Process took couple of weeks to complete. Recruiter contacted me on LinkedIn. Interview was based on my past experience, basic algorithms, operating system concepts, parallel programming concepts.
Questions d'entretien [1]
Question 1
Questions were common. One of them was very generic question "What are the ways to do interprocess communication?"
They told one round of interview. It went well answered all questions but no response received from them worst experience and worst employees of IBM management is very worst no response
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez MuleSoft en avr. 2019
Entretien
Multiple rounds of back and forth with recruiter with regards to position. They interviewed first time for one position and discovered during interview that I am not eligible for that position !!
Next interview for a different position was scheduled after couple of weeks. This time a junior engineer was assigned for phone screen. He asked two basic technical question. One was silly , the other from leetcode. He couldn't articulate first question. Not sure, but seems he was looking for a specific answer verbatim.
J'ai postulé via une autre source. J'ai passé un entretien chez MuleSoft (San Francisco, CA) en juill. 2017
Entretien
I got here at 9am, but they weren't ready for me, so I had to sit and wait for 40 minutes.
I didn't realize the pair-programming session was paired, since the guy was just doing his own work the whole time.
Questions d'entretien [1]
Question 1
Design a docker-like server to be able to run arbitrary worker jobs