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
      employer logo
      employer logo

      Automattic

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Automattic | Offres d’emploi chez Automattic | Salaires chez Automattic | Avantages sociaux chez Automattic
      Entretiens chez AutomatticEntretiens d’embauche pour Code Wrangler chez AutomatticEntretien chez Automattic


      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 Code Wrangler

      21 oct. 2018
      Employé (anonyme)
      Offre acceptée
      Expérience positive

      Autres retours d’entretien d’embauche pour un poste comme Code Wrangler chez Automattic

      Entretien pour Code Wrangler

      29 avr. 2026
      Candidat à l'entretien anonyme
      New Delhi
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 5 mois. J'ai passé un entretien chez Automattic en juil. 2017

      Entretien

      You should know who applied: PHP/Symfony guy with zero WordPress experience. Zero. Nada. NULL. empty. I had installed WordPress 9-10 years prior to applying, I knew that one folder name is wp-admin and that WordPress had plugins, but that's kind of all. Therefore, I encourage all non-WordPress developers out there to give it a try. Day 0: Application. Sent e-mail with answers to all questions in their job ad. +7d: Invitation to interview. +14d: Slack Chat. 8 AM. Regular software development questions. Some available here in Glassdoor (CSRF, be ready!). Being text, the interview turned out to be non-stressful. 1st impression on my side: positive. +14d-21d: Coding. SVN (not git!) checkout. It was a broken plugin that I had to fix. Undefined variables without pre-checks, security issues, missing IFs, mixed HTML and PHP, etc. I decided to risk and not only fix the problems, but rather turn everything upside down. Created tens of classes with single responsibility, built basic DI, split rendering, persistence, and BL, added unit tests, added a CLI interface to prove that the request context can be easily switched, etc. I knew that I may be disqualified, but I couldn't help it. It was a moment when I said that I don't really care about the interview, but rather that I just want to get some work done. If you want to get over the interview easily, don't do like me :). The main problems can be fixed in just a few hours. +~31d. Coding review. Took about 10 days from sending the 'I finalized the commits' e-mail to a response (Day 28: sent reminder!). I had 2 bugs. First one was due to the fact that the plugin was run under a different name in their environment and I had a hardcoded URL (I actually did not know how to create relative plugin URLs). The 2nd one was also rooted in my lack of WordPress experience: I secured a query using get_posts instead of the "injectable" SQL, but I did not test properly. Nevertheless, they were nice and they let me debug and fix the problems. Had to explain my code-design choices (Strategy, Factory, etc). +~44d. Signing the consulting agreement for the Trial Received the consulting agreement, signed it. Due to my vacation and their yearly Grand Meet-up, we agreed to only start the real trial on Day 79. Don't be scared, it was a bilateral desire, and the application process can be faster for you. I live in Germany, we just like making these processes longer. +~69d-71d. Proxy access, internal documentation access. Sent my public key, received access to multiple documentation sources, read a bit, saw pretty good & concrete information. You don’t find that clear information in a regular company. +~79d-125d: The trial. Almost real-life project: "Hey, paint the blue wall in green, here is the basic documentation that may refer to this project, pick it up and see what you can do". From there on it's your job as a candidate to act as an adult and collect information, get access to what you need, say hi to your buddies and integrate yourself. Learned to use P2s, sandboxes, Jetpack, Calypso, a bit of ElasticSearch, and, most importantly, learned how to debug WPCOM code. Took me a few weeks to get the necessary access, to understand where the code that I had to modify is and then only one week to do the project itself. I changed the acceptance criteria for my project a few times, I had a few frustrating moments because my debugging was not working (yes, Jetpack run-path is totally different than the WordPress one...), but somehow in the end I must have made it, since they decided I should have the Matt chat. ~+140d: The Matt Slack Chat. It's a bit insane to schedule it, since you actually expect him to ping you on Slack 'sometime'. Pure serendipity. First he contacted me on my wife's birthday, then again while I was in office, and then finally after I postponed the office-time chat. The questions didn't require problem-solving skills, but rather creativeness and experience. I must have saved it somewhere in order to tell you more about it, but since I didn’t do that, you’ll have to deal with it itself. About 4 hours in total, and what was really beautiful is that at the end I could discuss the money. I had doubts that they would compensate for my previous offer, but they did, so you can expect them to pay relatively competitive salaries for your region. The recommendation here: be “ok”, don’t swear, don’t insult, and you’ll make it! ~+147d: Offer! After reminder in day 145. Everyone out there, don't get scared of the many-days timeline. It was fully agreed/influenced on my side, and I estimate that the experience can be up to 5 times faster for others. Also, the interviewing process is really not that difficult. Before applying, I thought a huge train would hit me, with extremely difficult tasks, but in the end it turned out to be normal and pragmatic. Just solve the task!

      Questions d'entretien [1]

      Question 1

      CSRF
      Répondre à cette question
      20
      Aucune offre
      Expérience positive
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Automattic (New Delhi)

      Entretien

      Communication was effectively facilitated through Slack. A take-home project was assigned, to be completed within compensated hours. Overall, the experience was highly positive.Communication channels were highly effective and streamlined the process. The assignment of a take-home project allowed for focused work on a specific task. This project was completed within the allocated compensated time. Overall, the project management approach proved to be efficient. The facilitated communication greatly contributed to a positive experience.

      Entretien pour Code Wrangler

      14 janv. 2025
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Automattic (San Francisco, CA) en janv. 2025

      Entretien

      I recently participated in the interview process for Automattic and, unfortunately, my experience was quite disappointing. While the team was professional and responsive initially, my code test was ultimately rejected for a issue that cannot be considered as part of evaluation. It felt as though they were searching for a reason to reject, rather than genuinely evaluating my overall performance. This approach not only undermines the effort candidates put in but also suggests a lack of fairness and consistency in the evaluation process. The entire experience left me feeling frustrated and undervalued, particularly given the time and effort I invested. I strongly encourage the company to improve their process by ensuring clear, consistent evaluation criteria and fair consideration of candidates' work.

      Questions d'entretien [2]

      Question 1

      I had to review a PR!
      Répondre à cette question

      Question 2

      I had to built a tool!
      1 réponse

      Entretien pour Code Wrangler

      16 mai 2022
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Automattic

      Entretien

      S1 Coding challenge: Take home, suggested to take a week and was allowed to coordinate if I needed more time. Work on a WordPress plugin and perform a few security audits. The final deliverable were pull requests on GitHub. S2 Slack Interview: There was a decent gap between the coding challenge and this next step. It took about a month for my code to be reviewed, however, I was in contact with my recruiter throughout. They kept me up to date with timelines on their end. Overall it felt transparent. Once my test was reviewed, we moved on to the Slack interview. This interview wasn't technical and focused on my work experience, my interest in the position, and in WordPress VIP and Automattic. S3 After the interview was my trial. This we scheduled very quickly after the interview. In all, my trial lasted 17.5 hours spread over the course of about 2 weeks. The trial format offered room to explain and express your thinking as well as provided a place to brainstorm and work out solutions with your trial lead. I found this part of the interview process the most fun. The questions were challenging but the feedback was really thorough and frequent and I never felt like I had to find an answer entirely on my own. Once me and my trial lead felt the tasks were completed, my trial was concluded and I was invited to another interview, this time over video call. S4 Video Interview: This was more of an informal chance to meet my team lead and meet the engineer I'd been working closely with during my trial. It was a great chance to meet the folks I'd been working with and also an opportunity to ask more questions. S5 The offer: The final offer was another slack chat. This time with my HR point. They asked some logistics questions and gave me the offer. I accepted and they sent the official offer to sign to me during the chat.

      Questions d'entretien [1]

      Question 1

      What are two points in the Automattic creed that stand out to you and why?
      Répondre à cette question
      7