Disappointing. The role looked interesting. It required experience in C++ and statistics, perfect for a software engineer with a physics PhD. The recruiter asked me to sit a Python test, which was a problem, since physics, maths, CS, Verilog, C++, MATLAB, SQL and many other things are listed on my Resume except Python. She then told me that Python was probably essential, which is odd, since we managed quite well at CERN without it.
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Mozilla (Mountain View, CA) en juil. 2016
Entretien
1. HackerRank challenge
2. Two technical phone screens, two managerial phone screens.
3. On-site: 4 technical interviews, 2 non-technical
The interviews are not easy, but not impossible. They look for strong candidates who are able to think clearly - distributed working is a big part of the company culture, so employees need to be self-motivated and able to communicate clearly.
In addition, employees need to understand - and work to further - the Mozilla mission. Understand what that means to you, both personally and professionally!
Questions d'entretien [1]
Question 1
Stats, distributed systems, databases, map-reduce, general analytics skills
J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Mozilla (Vancouver, BC) en juil. 2016
Entretien
First round is an online test. I received an hackerrank invitation. I had to do 3 technical questions within 90 minutes. I did not get past the first round. Overall, the experience is good. They responded really fast.
Questions d'entretien [1]
Question 1
first questions is about stack, 2nd question is about array, 3rd question is about bit manipulation (Similar to cracking the code interview questions)