Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en MuleSoft (San Francisco, CA) en sept 2015
Entrevista
Several long phone interviews, then an all-day on-site interview, then a take-home coding challenge.
I found they had not really looked at my code.
I have a master’s degree in CS and about 20 years of experience.
And even though I “certainly wasn’t a bad fit”, they decided to “move forward with an internal referral candidate”.
Evidently the decision was based more on office politics, and someone just wanting a referral bonus.
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
Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en MuleSoft en abr 2019
Entrevista
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.
Me postulé a través de otra fuente. Acudí a una entrevista en MuleSoft (San Francisco, CA) en jul 2017
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Design a docker-like server to be able to run arbitrary worker jobs
