The last time Hackerfall tried to access this page, it returned a not found error. A cached version of the page is below, or clickhereto continue anyway

Inside Automattic’s remote hiring process | Dave Martin Inside Automattic’s remote hiring process – Dave Martin

How can Automattic consistently hire the best people without ever having a single voice conversation?

Lets face it, hiring is tough. When you ask startup founders what their biggest challenge is, hiring is one of the most common answers youll hear.

Its hard enough when you have an office and can interview an applicant in-person. Automattic is 100% distributed. We hire people from all around the world. We cant meet people in-person to interview them.

You may be wondering how do you consistently hire great people at a distributed company?

Heres the inside scoop

Our hiring process is a bit different than most companies

We dont schedule chats, we dont fly people out, and we rarely even have a single voice call before people are hired.

You might think, Thats crazy, theres no way that can be effective.

Well, here are some numbers:

I handle all design and growth hiring at Automattic. I began hiring about a year and a half ago. In that time Ive reviewed a total of 251 resumes.

63 of those have gone on to an interview (25% of applications received)

41 have been given a trial (65% of those who I interview)

15 have gone on to a final interview (37% of those who do a trial)

14 of those have been hired (93% of those who receive a final interview)

None of those whom Ive hired have been fired and zero have left the company voluntarily. (100% retention so far)

How do we do it?

Ive laid out our entire process below in five easy steps:

Step 1) The pre-screen

Ultimately, much of your success with hiring will come down to the degree to which your CEO sees it as a priority (hint: hiring should be a top priority for every CEO). Matt Mullenweg, Automattics founder and CEO consistently spends about 20-30% of his time on hiring. To this day, Matt pre-screens every single resume that comes into Automattic. This takes a significant portion of his time (we get lots of resumes).

Thats insane, you might say, Why invest so much of the CEOs time just pre-screening resumes? Shouldnt this be delegated?

No! Heres why:

Quality control: By reviewing all applications himself upfront, Matt can ensure from the very beginning that each applicant will be a good fit for the company. – Position throttling: At any point in time, Matt knows better than anyone else which roles in the company have the greatest need for additional resources. By pre-screening all applications he can easily throttle how many applications get forwarded on to each hiring lead, thus effectively increasing or decreasing volume for every role in real time. – Pre-approval: As a hiring lead, knowing that Matt has already pre-approved all resumes that come my way helps me move forward confidently with each applicant. I never have to second-guess as to what Matt might think about a particular applicant, because hes essentially already pre-approved every application that I see.

Step 2) Second tier resume review

We now have 315 people at Automattic. As such, we have multiple hiring leads for various roles. Every week Matt sends each hiring lead a batch of applications. Mine will consist of design and growth applications exclusively. Ill then review, and respond to each applicant.

Note: Replying to applicants takes top priority over every other responsibility I have.

If someone doesnt look like theyd be a good fit, Ill typically send them the following:

Hi John,

Thanks for your application to Automattic. We dont think theres a great fit at this very moment, but I encourage you to keep an eye on the Work With Us page on, and also keep us updated and consider re-applying as your skills and contributions to open source projects grow and expand.


Dave Martin

We try to reply to everyone, whether they look like a good fit yet or not. There are good reasons for this. Not only is it the right thing to do, weve actually had quite a few Automatticians get hired after reapplying a second or third time.

When someone does look promising, Ill send the following:

Hi John,

Please add me on Skype (redacted is my username). Id love to chat with you about the position.



Typically the applicant will add me on Skype within the next 24hrs.

Step 3) Interview

Immediately after I accept someones Skype invite Ill kick things off by saying something to the effect of:

Hi John!

Rather than set up a time to chat, lets just keep a conversation going in Skype. Ill ask questions, and you can answer as you have time. Could be today, tomorrow, whenever youre available. Sound good?

Then I just wait for them to respond. By keeping things 100% text, and 100% asynchronous, I dont have to worry about trying to schedule a day/time to chat (which can definitely be a pain across timezones).

Not only that, the concept of answering questions asynchronously is a relief for most people. Most everyone who applies is currently working elsewhere. Allowing them to answer questions whenever theyre available gives them the freedom to answer before or after work, or even on the weekend.

It also frees me up to work on other things in the meantime. I can have up to five interviews going at any one time without any difficulty, while also working on other stuff in between. It ends up working out really, really well.

After they reply to that first question Ill let them know that well just keep the chat text-only, and Ill typically ask an open ended question. Something like:

Id love to learn more about you. Lets just keep it as Skype text for now (most of our communication at Automattic is done via text). Tell me a bit more about yourself. What are you passionate about? What do you enjoy doing?

Im able to glean quite a lot out of this first question. Their answer here shows me how well they communicate. It gives me a glimpse into their interests, which helps determine whether theyll be a good culture fit at Automattic. It also serves as a bit of an ice-breaker before we dive into questions related to the role.

After weve chatted about interests, Ill dive right into questions related to the job. My goal is to keep interviews as short as possible, while at the same time extracting as much insight as possible. Im constantly fine tuning the questions that I ask. Here are a couple of examples:

– Can you break down how comfortable are you with the following, on a scale from 1-10 (10 being expert): PHP, JS, react, jQuery, HTML, CSS? – What one single design that you can share a link or screenshot to are you currently most proud of creating? – When it comes to growth, would you say you skew more towards A) Doing a little bit of research, and then just starting to test stuff, or B) Devoting more time doing research up front before you narrow in on which tests to run? – Take a product like Lets say you were tasked with increasing engagement (which we define as the number of people who log back in each month). What are some specific ways that you might go about trying to do that?

Every question I ask is strategic. Theres no sense in wasting your time, or theirs asking needless questions. Every question you ask should deliver some level of unique insight. If it doesnt, you should drop it, or tweak it.

On that note, if half way through the interview youve already made up your mind about an applicant, you might as well just end the interview there. When an interview doesnt work out Ill typically say something like:

Thanks so much for the interview. I appreciate your taking the time to chat. There were a number of things that I liked about your application, unfortunately I dont think theres a great fit at this very moment. I Would encourage you to keep an eye on the Work With Us page on, and also keep us updated and consider re-applying as your skills and contributions to open source projects grow and expand. All the best!

If the interview goes well, Ill ask if they have any questions. Some applicants have lots of questions, some have just a few. The question I get asked most frequently is about next steps, to which Ill reply:

Everyone that gets hired at Automattic goes through a paid trial process. You are given a project, which you can work on as you have time (could be an hour or two a night, could be on the weekend, whatever works for you). Youll keep track of the hours you work, and invoice us at the end of your trial. Most people do this while still employed. You can expect the trial to last about a month (but it really depends on how much time you can put in). There is no deadline, its done when its done. How does that sound?

Some applicants will want to start right away. Some may want to clear up a block of time, and may wish to hold off for a week or two. Well happily accommodate whatever works best for them.

Step 4) Trials

Trial projects are essential to effective remote hiring. I cant imagine hiring people without them.

Every single person who applies to Automattic (no matter the role) does a trial. We pay all trials the same amount ($25/hr).

Trials are a win/win solution for everyone involved.

For applicants: – A trial gives them a chance to test out whether theyll enjoy working remotely. – It gives them an opportunity to take Automattic for a spin, with no strings attached. – They can stop their trial at any time if they choose. – Whether they end up getting hired or not, they still get paid for their time.

Trial projects are great for us for a number of reasons:

– They give us insight into how a person actually works. – We get to see how well a person communicates over the course of a project, and how well they respond to feedback. – Our trial projects are real projects. They consist of actual work that we need done. In that sense, were also getting additional stuff done in the process.

To transition from the interview into the trial itself Ill usually tell the person:

Ill be in touch shortly with 2 things:

1) A trial contract (just sign it and email it back) 2) Access to a private blog where well communicate throughout the rest of your trial.

Weve got an internal tool that I can enter an applicants name, email and position into, which will then send out a trial contract to the applicant.

Once I fire off a contract, Ill post a comment on our internal hiring P2 to give HR a heads up that a trial contract will be incoming shortly.

NOTE: P2 is a WordPress theme that makes threaded discussions incredibly simple. We use P2 for a large portion of our internal communication.

Ill then create a new private blog and invite the applicant to be an editor. This is where Ill post the project brief. This is also where Ill move the conversation for the remainder of the trial.

Project brief you say? What does that look like?

Have a look, here’s an example:

Project Brief

Improve the homepage design for


Weve been meaning to give a refresh for some time now. The current design has been there for a number of years. Id love for you to spend some time coming up with a fresh new look. Just focus on the homepage for this trial project (no need to spend time redesigning any of the other pages).


Let me know if you need access to any additional resources.


Along the way, please post all of your deliverables to this P2.

Round 1: Summary of your thoughts

Id like for you to first summarize (just a simple bullet list is fine) the problems and opportunities you see with regard to the current website. Ill review this to make sure were on the same page, and then youll move on to round 2.

Round 2: Rough concepts

Use whatever method you prefer to convey quick concepts (sketches, wireframes, balsamiq, etc). Please dont spend any time on polish at this point. Im just looking for rough concepts. Youll then iterate quickly based on feedback until were both happy with the direction.

Note: Im not looking for any sort of re-branding. Feel free to move the logo around, and improve the layout, but no need to redesign the logo for this specific project.

Round 3: Add some polish

Get the design as close to pixel perfect as you can (or optionally hop straight to code, if youre more comfortable doing that).

Round 4: Code it up

Last, Ill ask that you code it up. Simple HTML and CSS is fine. Feel free to mix some JS in where appropriate if you feel comfortable doing so (but its in no way required).

Your final deliverable should be a zip file with all of your source files, as well as your HTML homepage.

Good luck!

There is no deadline for this project, but I encourage you to communicate early and often (not just when youve got something thats pixel perfect).

Ill touch base with the person one more time to make sure that they got the contract and access to the private blog, then Ill just leave it in their hands.

Ill then work with the person throughout each round of the trial project. Well communicate back and forth about the project via the private blog.

If things dont end up working out, Ill do my best to highlight why. At this point the applicant has invested quite a bit of time. I try and be as specific as possible as to why they are not going to proceed to a final interview.

If the trial goes well, Ill chat with them about the final interview with Matt.

Step 5) Final interview

In the final interview Matt will chat with each applicant. This serves as a good opportunity to vet each applicant one last time. This is also where Matt will chat with the person about compensation, and answer any additional questions they may have.

If the final interview goes well, they are sent an offer letter.

Recap & final thoughts

Interested in learning more about our process? You can read some of Matt’s thoughts in this HBR article.

We’re hiring

We currently have 13 open positions. We’d love to hear from you!

Like this:

Like Loading...

Continue reading on