Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo

      Mozilla

      Fait partie de The Mozilla Foundation

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Mozilla | Offres d’emploi chez Mozilla | Salaires chez Mozilla | Avantages sociaux chez Mozilla
      Entretiens chez MozillaEntretiens d’embauche pour Web Developer chez MozillaEntretien chez Mozilla


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Web Developer

      7 sept. 2012
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 mois. J'ai passé un entretien chez Mozilla en juill. 2011

      Entretien

      ---- I am using the email trails in my gmail to write specific dates, times, and events in the following description --- * Approached by a Technical recruiter at Mozilla on 6/28/2011 * Followed up by mail from another (fellow of the first) technical recruiter on 7/19/2011 (almost 20days after the first email exchange). He fixed a time for a Skype call on 7/20/2011 * Did not show up on time, said Google calender did not alert him. Call postponed for the next day. * An introductory call on 7/21/2011. * I told the recruiter that I am a backend (architecture and development) guy and not a frontend (html/css/js ) guy * The recruiter told me that the position would either be remote (from India) or based from there HQ in the US. It will be decided later based on the interviews and VISA concerns. * He told me that usually there are three phone interviews and then followed up by on-site interviews. * The recruiter told me about the different projects going on at Mozilla and the different teams and roles. * Interview fixed for 7/27/2011. * Interview - 1 - 7/27/2011 - 10PM IST (GMT+530) * Interviewer did not show up on time, had to reach out to the recruiter to get a hold of the interviewer. Interview started one hour late at - 11PM IST (GMT+530). * Purely technical interview. Testing the fundamentals of web, http, web development, web security, Python, Django. * 7/30/2011 - Heard back from the recruiter. Asked for availability for next interview and handed over the job of fixing the next interview to a coordinator. * 8/2/2011 - The coordinator came up and fixed the next interview for 8/5/2011 * Interview - 2 - 8/5/2011 - 10PM IST (GMT+530) * The interviewer did not turn up. * Reached out to the coordinator. She re-fixed the interview with a different person on 8/10/2011 * Interview - 2 (re-fixed) - 8/10/2011 - 10PM IST (GMT+530) * Very interesting interviewer. Hard core backend developer. We shared a lot of interests. * Technical interview. Testing the fundamentals of web, http, web development, web security, Python, Django. * Some discussion on philosophy of development, technical debt, maintanability and testing. * 8/16/2011 - The recruiter got back and said that he would like to set up another call. * 8/17/2011 - The coordinator set up another call for 8/24/2011 * 8/23/2011 - The coordinator emailed that the next interviewer has a conflict of schedule and would like to prepone the interview by one hour on 24th. * Interview - 3 8/24/2011 - 6PM IST (GMT+530) * Technical interview. Testing the fundamentals of web, http, web development, web security, Python, Django. * No response for two weeks even after seeking it twice. * 9/6/2011 - silent gap of almost a 2 weeks - the recruiter responds and fixes a call with the Director of Web development - for 9/7/2011 * Interview 4 - 9/7/2011 - 9:30PM IST (GMT+530) * Mostly general, but some technical stuff too. * More info about teams and projects. * No response for three weeks even after expressing that they are testing my limits of patience. * 9/29/2011 - The recuiter got back. * Change of plans - all (5 in number) interviews that were supposed to happen onsite will now happen on Skype over a period of 2 days. All sorts of excuses given for why they cannot get me there. * No clear answers to questions. * 10/1/2011 - A new coordinator got in touch and fixed the interviews for 10/5/2011 (3 interviews) and 10/6/2011 (2 interviews) * Interview 5 - 10/5/2011 - 9PM IST (GMT+530) * Technical, backend web development, web/http fundamentals, web security, Python, Django, testing. * Interview 6 - 10/5/2011 - 9:45PM IST (GMT+530) * Technical, backend development, heavy on testing because the interviewer was the author of a very widely used Python testing framework. * Interview 7 - 10/5/2011 - 10:30PM IST (GMT+530) * Frontend interview - some HTML/CSS, a lot of Javascript - I flunked this. * Interview 8 - 10/6/2011 - 9:00PM IST (GMT+530) * Technical, backend web development, web/http fundamentals, web security, Python, Django, testing. * Interview 9 - 10/6/2011 - 9:45PM IST (GMT+530) * Concluding interview with the director of web development. * No response for a week. * 10/11/2011 - I reached out via an email. * 10/12/2011 - The recuiter got back and I was told that "Your backend architecture, database modelling, backend development skills and web security knowledge and expertise is a perfect match BUT we are looking for a full stack developer who can do frontend also" * I was shocked - I told the recuiter in the first interview that I am not a frontend guy and it took him 3.5months to understand that??? * I lost my cool and told him in befitting words that "I don't buy his argument". * Neither side followed up after that. conclusion in one word = "unprofessional"

      Questions d'entretien [1]

      Question 1

      One full unexpected interview focused on frontend web development, with a lot of unexpected questions - which I clearly flunked.
      1 réponse
      6

      Autres retours d’entretien d’embauche pour un poste comme Web Developer chez Mozilla

      Entretien pour Web Developer

      24 août 2017
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive

      Candidature

      J'ai passé un entretien chez Mozilla

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      What do you think is a problem with an intentional team?
      Répondre à cette question

      Entretien pour Web Developer

      6 nov. 2015
      Employé (anonyme)
      Mountain View, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 mois. J'ai passé un entretien chez Mozilla (Mountain View, CA)

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      I was asked to solve a typical tree-sorting problem with a couple different algorithms.
      1 réponse
      5

      Entretien pour Web Developer

      23 janv. 2013
      Employé (anonyme)
      Portland, OR
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 2 semaines. J'ai passé un entretien chez Mozilla (Portland, OR)

      Entretien

      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.

      Questions d'entretien [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.
      Répondre à cette question