Automattic application practice

Small, finished work is more useful here than an elaborate speculative project. For Automattic, prepare a bounded fix with a progress update, tests and a handoff another person can use. The source guide also describes practical assessments and paid trials; confirm the actual invitation's scope and terms before committing time.

Choose your application route

Work to compare: Engineering; product/design; customer support; other named product vacancies.

Prepare one example: A small finished fix, progress update, tests and a handoff; clarify paid-trial scope before starting.

Ask the team: What task, review criteria, hours and payment terms apply to this invitation?

Employer resource: How Automattic hires developers

Before applying: Check the vacancy’s degree or experience gate, term, worksite, pay basis and deadline. This is preparation guidance, not a verified 2027 internship list. A suggested work sample is not an application requirement.

Understand the paid-trial distinction

Automattic's hiring overview describes practical assessments for some roles and paid trials that provide an opportunity to work together. Later conversations can involve leadership. The sequence and time commitment vary, so confirm the brief, compensation, scheduling, and expectations for your specific process. A trial is an assessment, not a promise of employment. Source: How Automattic hires

The developer-specific guide describes activities such as a text-based interview, a coding exercise with support from a buddy, and a trial involving real work. That developer pathway should not be generalized to every business, design, or customer-facing position. Source: How Automattic hires developers

Do not prepare only a polished sales pitch. Prepare a repeatable way to understand a problem, deliver a bounded result, explain decisions, and incorporate review. The suggestions below are editorial preparation advice, not an official scoring system.

Select a role and a product context

Start with the official jobs and working-with-us page. Read the specific responsibilities, eligible locations, working arrangements, and requested application materials. Do not assume that every Automattic role has identical hours, product exposure, or assessment stages.

Developers. Prepare to navigate existing code, reproduce a problem, make a maintainable change, and explain its behavior. A small fix with tests, clear scope, and thoughtful review responses is more useful than a large unexplained code dump.

Customer support and happiness roles. Show careful reading, diagnosis, empathy, and a clear next step. Prepare examples that resolve a user's actual problem without unnecessary jargon. Distinguish being friendly from making promises you cannot keep.

Design and product. Show how you balance simplicity with real user constraints. Prepare a decision narrative that includes discovery, alternatives, implementation, and what happened afterward. A portfolio should reveal your judgment rather than only attractive screens.

Marketing, sales, and operations. Use a campaign analysis, qualification plan, or operating document that demonstrates the relevant skill. Explain the audience, objective, constraints, measurement, and decisions you personally owned. Do not make a developer portfolio the default for a non-developer role.

Make the application inspectable

Your resume should identify relevant work and provide a clear path to supporting detail. Choose a few links that load without special permissions. State what each artifact demonstrates so a reviewer does not have to search a personal website for evidence.

Fictional illustration: "Reproduced a checkout failure affecting one payment method, added a regression test, and documented a safe workaround while the patch was reviewed." Even without a dramatic percentage, this describes diagnosis, testing, communication, and scope. It is stronger than "Passionate about customer-centric engineering."

A support applicant might write: "Created a troubleshooting guide after reviewing recurring configuration questions; teammates used it to resolve cases without repeating the same escalation." Use real evidence for adoption or time saved when available. Do not invent precision or claim another person's implementation as your own.

Explain career transitions directly. An agency developer can show client communication and maintenance work. A teacher can demonstrate written instruction and difficult conversations for an appropriate customer-facing role. Transferable skills strengthen an application only when the role's essential requirements are also credible.

Prepare for a trial without overcommitting

Before agreeing to a practical assessment, establish the scope, payment terms, expected hours, deadline, tools, reviewer, and communication channel. Ask how to handle competing obligations and whether work can be scheduled around existing commitments. Resolve conflicts with any current employer's confidentiality or outside-work rules without disclosing protected material.

Automattic's trial guidance emphasizes communicating progress and questions through the appropriate shared channels. It discusses keeping updates understandable and making the work visible. Use that guidance to prepare a working rhythm rather than disappearing until you have something you consider perfect. Source: What to expect during a trial

A useful personal rhythm is to clarify the objective, propose a small first step, share progress, expose blockers, and ask focused questions. Distinguish decisions you can reasonably make from decisions that need context. Constantly requesting reassurance can slow the work, but silently assuming requirements can be worse.

If the assignment seems larger than the agreed scope, raise that early. Explain what you can complete, what you would defer, and why. Do not try to compensate by secretly doing an unlimited amount of work. The assessment should reflect a sustainable, transparent way of contributing.

A practical progress update template

Write updates that answer four questions in a few sentences: What changed? What evidence supports it? What is blocked or uncertain? What happens next? Link a test, draft, screenshot, or decision note when it helps.

For example: "I reproduced the failure with an empty configuration field and added a test. The proposed validation change prevents that path, but I have not yet checked the import flow. I will test imports next; I need confirmation about whether blank values are valid for older installations." This communicates progress and a specific question without pretending the work is finished.

For support or marketing work, replace the technical details with the equivalent evidence: a case pattern, user misunderstanding, campaign assumption, or unresolved approval. The same principle applies: a teammate should understand the state of the work without a lengthy private conversation.

Interview preparation that complements the work sample

Prepare three stories: a time feedback changed your work, a time you made progress with incomplete information, and a time you corrected an error. Explain how you communicated during the event, not only what you learned afterward.

For a text-based conversation, practice concise answers with a clear conclusion and enough context. Do not paste an essay that ignores the question. For a live discussion, prepare to open an artifact and explain the most important decision without narrating every step of your career.

Ask which AI tools, reference materials, and outside assistance are permitted at each assessment stage. Permission to use a tool for personal preparation is not permission to use it during evaluated work. Be able to explain and verify every part of an authorized submission.

Avoid performance theater. Staying online continuously, sending constant updates, or writing elaborate essays does not by itself demonstrate useful remote collaboration. Aim for reliable progress, appropriate visibility, and a completed result that another person can use.

Questions to ask before accepting an offer

Ask what the first project would be, how work is reviewed, and how priorities change. Clarify customer coverage hours or team overlap when relevant. Ask how new hires get product context and how success is evaluated after the initial learning period.

During a trial, pay attention to the experience as well as the outcome. Were expectations clear? Was feedback actionable? Could you ask questions? Did the work resemble the role you applied for? Your own assessment of fit matters alongside the employer's decision.

Do not treat a paid trial as a reason to resign from an existing job before an employment offer and its conditions are settled. Keep records of agreed trial scope and compensation, and use the recruiting contact to resolve administrative questions.

Related career guides

GitLab job guide | Notion job guide | Duolingo job guide

Evidence date