Web Developer applicants have rated the interview process at Mozilla with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 41.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Web Developer roles take an average of 61 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Mozilla overall takes an average of 33 days.
Common stages of the interview process at Mozilla as a Web Developer according to 4 Glassdoor interviews include:
Phone interview: 44%
Skills test: 22%
Personality test: 11%
One on one interview: 11%
Background check: 11%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 2 weeks. I interviewed at Mozilla (Portland, OR)
Interview
Interview cycle consisted of 4, roughly 1 hr phone interviews. This was made up of 1 screening interview and then 3 technical interviews from peers on the team I would be working on.
Interview questions [1]
Question 1
An open ended one: "How would you design ProductX (a product we are currently working on)". Was difficult since I had very little context as to the reasoning for ProductX and what the base requirements were.
I participated in multiple nice interviews and some online tests. Overall process was nice, but a bit long. It took about four months for me. But it was Christmas time back then.
Interview questions [1]
Question 1
What do you think is a problem with an intentional team?
I applied online. The process took 3 months. I interviewed at Mozilla (Mountain View, CA)
Interview
When I applied I grabbed a book, "Programming Interviews Exposed" to refresh myself on how the process would go. (I hadn't been in the job market for 8 years). Pretty standard developer interview for tech industry: recruiting phone screen, managerial phone screen, 2 phone tech interviews, 6 in-person interviews. The process took a long time, but it wasn't confusing or painful.
Interview questions [1]
Question 1
I was asked to solve a typical tree-sorting problem with a couple different algorithms.