Automattic's Interview Process (2026)

Blog / Automattic's Interview Process (2026)
Automattic Interview Process
Automattic's software engineer interview process is highly unconventional, and most candidates report it feels more like starting a job than interviewing for one. The process is almost entirely asynchronous and text-based, typically unfolding across four to five stages over two to three months.
  • Application and Questionnaire: You submit a resume, cover letter, and answers to specific application questions. The written responses are reviewed as a formal step, so treat them as seriously as a coding challenge.
  • Intro Chat (Slack): If your application moves forward, you are invited to a private Slack channel for a text-only conversation with an engineer, typically lasting around 60 to 90 minutes. Expect questions about your background and how you approach real-world engineering problems.
  • Coding Challenge (GitHub): A take-home assignment where you are given access to an existing codebase, often a WordPress-related plugin or toy project, and asked to solve specific objectives. You usually have around one week to complete it.
  • The Trial: A paid, part-time contract where you work on real tasks alongside Automattic employees for roughly three to four weeks. You use their internal tools, including P2 and Slack, and are assigned a buddy who reviews your work.
  • Final Review (Matt Chat): After a successful trial, the hiring team submits a recommendation for a final review, which is sometimes a direct conversation with a senior leader or CEO Matt Mullenweg. This is typically a fit and feedback session before a formal offer.
To prepare effectively, focus your energy on these key areas that Automattic actually tests:
  • Coding Challenge (Take-Home Project): A real-world take-home coding challenge focused on modifying an existing codebase.
  • Behavioral and Remote Work Philosophy: Questions about communication style, handling ambiguity, and remote work values.
  • Written Technical Communication: Demonstrating technical thinking and decision-making through clear written documentation.
1. Coding Challenge (Take-Home Project)Automattic does not use LeetCode-style algorithmic puzzles. The coding challenge asks you to work within an existing, unfamiliar codebase and complete specific objectives, with an emphasis on security, performance, and readable code.The goal is not just a working solution. Reviewers want to see how you approach an unfamiliar codebase, the trade-offs you considered, and why you made specific decisions. Think of it less like a test and more like a first week on the job.Practicing with realistic, project-style problems is the best way to prepare. Our take-home project practice covers the kind of applied problem-solving Automattic is looking for, which is a much closer match than grinding abstract algorithm questions.
2. Behavioral and Remote Work PhilosophyAutomattic places significant weight on how you work, not just what you can build. Expect questions about your remote work philosophy, how you handle ambiguity, and how you communicate across time zones without real-time meetings.These are not softballs. Interviewers want specific examples, so prepare stories that show how you have dealt with unclear requirements, documented decisions for teammates, or debugged a problem asynchronously. Structuring your answers using the STAR principle helps you stay focused and concrete.For broader preparation, the Behavioral Interview Course and Behavioral Playbook will help you build a solid bank of stories before your Slack intro chat.
3. Written Technical CommunicationAt Automattic, the writing is the work. Every stage of the process, from your application answers to your trial pull requests, is evaluated on how clearly you can communicate technical thinking in text.During the trial, you are expected to document your reasoning on P2, Automattic's internal WordPress-based communication tool. A well-structured P2 post with clear headings and a concise summary signals stronger technical aptitude than a wall of text with the same information.Practice writing up your decisions as you code. For any solution you work on, including exercises from our take-home project practice, try writing a short summary of what you built, what alternatives you considered, and why you chose your approach.
ConclusionAutomattic's process rewards candidates who communicate clearly, work independently, and treat every written update as part of their craft. Start practicing with realistic project work, sharpen your written communication, and build your behavioral stories now. Follow the Automattic Interview Roadmap for a structured, stage-by-stage plan to get you to an offer.

About TechPrep

Never walk into a technical interview unprepared again. TechPrep empowers software engineers to stop guessing and start getting offers. We provide the exact questions asked by tech companies across Data Structures & Algorithms, System Design, Low-Level Design & Practical coding rounds. Don't leave your career up to chance. Join thousands of engineers who have successfully navigated the tech hiring maze and landed roles at top tech companies.