J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Automattic (San Francisco, CA) en mai 2022
Entretien
You'll be assigned a take home project, even though you're applying a position for JS, you still needs to be familiar with PHP since that project is written in PHP in a large portion. The hiring team is very helpful and gives an goal to test your knowledge in security and performance. The feedback is not very clear on what I'm missing though, if they're afraid the answer will be posted on websites like here, they can ask the candidate to sign a non-disclosure form.
Expérience positive
Entretien moyen
Candidature
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Automattic (Madrid)
Entretien
In my cases there were 2 practical stages. The first one was to fix some issues in a real project like you would do in a real scenario, interacting with Slack, GitHub comments etc The second one was more of a planning and high level architecture for a feature
Questions d'entretien [1]
Question 1
There were some questions about security which involved finding security issues in some code and relate them to OWASP top 10 security risks
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Automattic (Londres, Angleterre) en sept. 2021
Entretien
Approached by an internal recruiter about interest generally in a position, without specifics. Had a chat, which went well and felt we had a good rapport.
Assigned a code test, accessible via a cloud environment and provided access to a Slack channel to talk things over with the recruiters.
Although this wasn't hard, there was a lot of small granular tasks to complete which took longer than expected, due to full time employment.
Completed all requested challenges - wrote out my thought process for each approach, however was not successful.
Feedback was prompt, however in my opinion some of the points raised felt quite subjective and would easily be rectified with discussion - as in a work environment.
One of the points raised was that a specific submitted file on PR had formatted differently to their standards, meaning it was hard to spot the changes.
This is valid, however I think it's reasonable given the circumstances when not provided the expected formatting standards / configs.
It did feel like there was some hidden rules / hoops to jump through that weren't explained all that clearly.
Questions d'entretien [1]
Question 1
One of the tasks was to make elements accessible to screen readers.