Me postulé en línea. El proceso tomó más de 3 meses. Acudí a una entrevista en Mozilla (Mountain View, CA) en ene 2016
Entrevista
Online application through their careers page. I was contacted about 1 week later by HR and had 4 phone interviews over the course of 1 month. 2 technical and 2 regular conversations with management positions.
After passing those, I was brought in for an onsite interview with 8 individuals over the course of a full day. Half of the interviews were through a video conferencing system Mozilla uses.
The entire process took over 3 months and there were long periods of silence. HR was not responsive and often left me wondering what was going on. Overall, Mozilla is an extremely slow company since half of the employees are remote and communication takes extra time. I noticed there were very few employees under 30 years of age, which I found interesting for a tech company. Even from the interviews, I felt like the company was stuck in a bureaucratic mess where there was a frustration between old and new ways of development.
Two employees during my interview process mentioned that it was extremely hard to create change and bring in ideas since the majority of senior engineers have been at Mozilla for a long period of time and had a set way of doing things. I was a little shocked at how many internal problems seemed to occur at Mozilla.
Many engineers made it clear that working on OSS had many weak points and wanted to make sure I fully understood the drawbacks before considering Mozilla.
Having said all that, I did speak with highly passionate and talented engineers, managers, and directors. Their insights were fascinating and they all seemed excited to be part of the Mozilla organization. They all knew their field very well and held pride in their work. I would say the individuals were great, but the way Mozilla is run at a company level was restricting their capabilities and ideas.
Overall, you would have to be extremely passionate about OSS and user privacy to consider all the negatives accepting all the negatives that come from a company run like Mozilla.
PS: An interesting bit of information I learned from the interviews -- Firefox downloads have been steadily declining for some time now and their main business partner, Yahoo!, is not doing well.
Preguntas de entrevista [1]
Pregunta 1
Standard technical questions.
plus:
Why do you want to work for Mozilla? (everyone asked this)
What is your development process?
What is a challenge you had to overcome?
How would you convince someone to follow your idea?
What's the best way to revolutionize senior management? How would you bring in new ideas?
How did you deal with a conflict with another employee?
How do you feel about engineering in the public?
Do you have experience with test driven development?
How do you feel about working remotely?
Me postulé a través de otra fuente. El proceso tomó 4 semanas. Acudí a una entrevista en Mozilla (California, MD)
Entrevista
It was not that much good or bad. The interview hiring process took too much long. After applying for role it took a month to get response for next stage interview.
Acudí a una entrevista en Mozilla (San Francisco, CA)
Entrevista
Initial interview with someone from HR and then multiple rounds of technical interviews with usually two interviewers. Some questions are quite hard. Interviews usually take 45 mins, but sometimes it takes longer.
Preguntas de entrevista [1]
Pregunta 1
They asked about a difference between threads and processes
Me postulé a través de una facultad o universidad. El proceso tomó 1 día. Acudí a una entrevista en Mozilla (Toronto, ON) en feb 2025
Entrevista
The interview process was in the form of a behavioural part and a technical part, similar to any other software engineering role. It was two hours. They are strict with their scheduling, so be ready to interview fast.
Preguntas de entrevista [1]
Pregunta 1
They asked me leetcode question which was a hasp/two pointer based quesition, similar to three sum.