Job search
Automattic Developer Trial: Reconcile the Brief, Part-Time Hours, and Collaboration Channels
Three current official hour descriptions and two completed fictional records clarify scope, part-time planning, feedback and delivery state without assuming a universal trial contract.
Before starting an Automattic developer trial, reconcile the actual brief with the public hiring pages. Those pages currently describe different amounts of work. Confirm the authorized hours, elapsed schedule, feedback checkpoints and delivery locations for your invitation before treating any one published range as your commitment.
This guide reviews public Automattic pages checked October 21, 2026. No application was submitted, trial performed or private channel accessed. LandOffer publishes this guide and offers job-search tools. If you are comparing this commitment with other opportunities, browse recent roles on LandOffer.ai while keeping each employer’s requirements separate.

Read the three hour descriptions together
The general Work With Us page describes a practical test or a longer trial of up to 20 hours, with most candidates finishing within roughly a week. It says hiring steps can vary by role. That overview does not identify the cap for a particular developer invitation.
The developer hiring page instead describes a paid, part-time trial spanning two to eight weeks, totaling around 15–35 working hours. It presents scheduling as flexible. Separately, its coding-challenge stage generally allows a week; that stage’s completion window should not become the assumed trial deadline.
The trial guidance page gives another typical range: 25–40 hours for non-Happiness roles. It publishes a standard trial rate of $25 USD per hour and says this does not determine eventual salary. These are public descriptions, not confirmation of your approved hours or payment arrangements.
All three pages were accessible during this review. The difference cannot be resolved by choosing the smallest number, averaging the ranges or assuming the developer page overrides everything else. We did not establish which description governs a new individual trial. Preserve the URLs and ask the hiring contact to identify the applicable scope in writing.
Separate authorized working hours, the calendar window and the reviewer’s checkpoint. Confirm each one; a date range alone does not tell you how much work to reserve. An open weekend does not increase an approved budget, and waiting three days for a review is not automatically three days of billable work.
Turn the invitation into a bounded work agreement
Read the actual task and accompanying instructions before arranging evenings around it. Identify the required outcome, included activities and completion evidence. Ask whether setup, reading, written updates, review responses and a final summary belong inside the same cap. Include these activities in the clarification rather than treating everything outside coding as unrecorded preparation.
Automattic’s writing guidance says not to generate replies to its questions with AI and asks candidates to explain any AI use and output review. The cases here are AI-authored teaching examples, not candidate submissions to copy. Write actual employer communication in your own voice and follow the specific task’s tool rules.
Keep unresolved items visible. A brief may explain the feature well while omitting the latest acceptable delivery date, time-recording method or who can approve extra scope. An estimate from a trial buddy is not necessarily permission to exceed a cap. Ask who owns that decision and what to do when the remaining hours cannot cover a requested revision.
Clarify the relationship between an initial submission and later changes. Does a checkpoint invite exploratory feedback, or must it contain every acceptance item? Is a second pass expected? What should happen if feedback arrives after your last available block? A confirmed checkpoint lets you reserve time for revisions and show when a delayed review would affect delivery.
Also confirm permitted tools and material handling. Public descriptions of using your own tools do not settle the rules for a specific repository, AI assistance, external services or retaining trial code afterward. Use the instructions supplied for that work. Avoid importing confidential material from a current employer to demonstrate speed or technical familiarity.
Worked example: reconcile a part-time brief before starting
The following candidate, task, dates and correspondence are wholly fictional. They are not an Automattic invitation, rate quote or accepted schedule. The example concerns planning and communication; it supplies no answer to an actual hiring exercise.
Mira receives an invented brief to improve an export-settings form. It asks for validation behavior, a small test set and an explanation of an accessibility tradeoff. The brief says “part-time trial” but supplies no total-hour limit. Mira can reserve six three-hour blocks across three weeks. She does not yet have permission to start.
Her completed reconciliation record separates available time from confirmed obligations:
| Item | Evidence in the fictional record | Decision before work begins |
|---|---|---|
| Deliverable | Validation change, tests and tradeoff note requested | Keep these three outputs together; ask which repository and written-summary location to use |
| Candidate availability | Six blocks × three hours = 18 hours | Offer 18 hours as availability, not an agreed cap |
| Public hours | Up to 20; around 15–35; typically 25–40 | List the conflict; request the invitation’s exact authorized total |
| Review timing | No reviewer checkpoint specified | Propose a first review after block three and ask when feedback can reasonably arrive |
| Further revisions | No extension owner named | Stop at the confirmed limit and request a scope decision before additional work |
Mira prepares this complete, unsent clarification:
Thanks for the brief. I can reserve six three-hour blocks across three weeks, totaling 18 hours. Before starting, could you confirm the authorized total and whether setup, tests, written updates and review changes are included? The public hiring pages show different hour ranges, so I do not want to assume which applies here. I propose a first review after my third block. Please confirm the delivery deadline, likely feedback timing, where to record time, and who can approve a scope change. I also need the designated code and decision-summary locations and the rules for tools and retaining materials. If the requested scope needs more than 18 hours, I would like to agree a smaller scope or another schedule first.
Her proposed allocation remains unapproved: block one for setup and clarification; blocks two and three for implementation and a first test pass; block four for review changes; block five for remaining checks; block six for the final explanation and handoff. Each block is three hours. These are her planning choices, not Automattic’s prescribed durations.
The draft plan reserves nine hours before the first review and nine afterward. It does not guarantee feedback will arrive between those groups. Mira marks the start as pending until the owner confirms both scope and review feasibility. If a 30-hour requirement is later confirmed, her 18 available hours leave a 12-hour gap; flexibility in calendar dates alone does not remove that gap.
This record produces an actionable result: no assumed start, no silent expansion, and a named set of questions that can change the plan. It also gives the hiring team something concrete to adjust. Mira can offer different dates without implying that she has unlimited evenings or has already accepted terms.
Give each collaboration channel a clear job
Automattic’s trial guidance favors its designated hiring Slack channel over direct messages where possible, and asks candidates to preserve decisions and updates on P2. It also describes a trial lead and feedback during the work. The developer page names Slack, GitHub and P2 in the process. Neither source specifies a universal response deadline or identical repository workflow for every trial.
Use the supplied instructions to map those tools to actual artifacts. A conversation can raise a question; a code review can discuss an implementation; a durable summary can explain what changed and why. Ask which location is authoritative when they disagree. Do not create public repositories or move private trial material into a personal portfolio merely because GitHub is mentioned.
Keep links and state together. “Submitted for review” tells a reviewer where to look and what remains open. “Approved” requires evidence of approval by the relevant person. A passing local check, a friendly Slack reply and a merged change are different observations; none should be relabeled as a hiring decision.

Worked example: preserve a decision without inventing acceptance
This second example is also wholly fictional and independent of Mira’s hour plan. Jonas is working on an invented trial component that displays a stale saved setting after a user changes a selection. No real code, company system or trial repository was accessed, and the example does not claim any implementation was run.
Jonas initially writes: “Fixed the stale-setting issue; everything is ready.” His record supports a draft and an unresolved behavior question, rather than a completed fix. It contains a proposed change and two planned checks, while one behavior question remains unresolved. He replaces the broad claim with a completed handoff package:
| Location in the fictional package | Filled entry | State supported by the entry |
|---|---|---|
| Designated hiring-channel note | “The draft changes when the displayed setting refreshes. I need clarification on whether a canceled edit should restore the previous display.” | Question raised; no answer recorded |
| Code-review description | “Draft patch prepared for the refresh path. Planned checks cover a saved edit and a canceled edit; execution evidence is not yet attached.” | Draft available; checks not executed |
| Durable decision summary | “A previous proposal refreshed only after reopening. The current draft refreshes after save. Cancel behavior remains undecided; no final acceptance is recorded.” | Rationale documented; decision incomplete |
| Final handoff note | “Review the draft and resolve cancel behavior before marking the task complete. Further changes depend on the remaining authorized scope.” | Ready for review, not accepted |
His corrected summary is useful because the unresolved item is precise. The reviewer can answer one behavior question instead of deciphering a blanket success claim. Jonas has also preserved the discarded approach without treating an untested alternative as a measured improvement.
We checked an original local consistency fixture for these two examples. It verifies the six-block allocation and the 12-hour availability gap, then rejects three deliberately incorrect records: available hours labeled as approved, planned checks labeled as executed, and a submitted draft labeled as accepted without approval evidence. This was an offline record check, not an Automattic trial, repository test or evaluation of candidate performance.
For your own work, preserve the actual artifacts the instructions permit: the current draft identifier, requested behavior, executed-check evidence when it exists, open questions and the next owner. Do not manufacture additional documentation to create an appearance of activity. A short accurate update is more useful than several repetitive posts that disagree about task status.
Finish the trial with an explicit state
Near the confirmed limit, summarize delivered items, remaining gaps and recorded hours in the required locations. Ask how the team wants unfinished scope handled. If a review has not arrived, preserve the submitted state and ask about the next checkpoint. If a blocker prevents progress, explain the missing decision before reserving more work. A timely scope question gives the owner a chance to choose a smaller outcome or authorize another step.
If you receive feedback, distinguish the requested revision from your interpretation. Record what you changed, what you checked and what still needs review. If the feedback is ambiguous, ask a narrow question before broadening the task. Keep the conversation in its designated channel and preserve material decisions where the trial instructions require them.
A completed trial is still one hiring stage. Public descriptions of offers and feedback do not establish that submitting your work results in employment, a particular team assignment or a guaranteed decision date. Retain the actual next-step message and keep your application state truthful while you wait.
Before committing, retain the confirmed scope, authorized hours, workable calendar, feedback plan and delivery route in your own permitted notes. Ask about any missing item before starting or accepting a larger revision. For other opportunities that fit your available time and experience, explore LandOffer.ai and evaluate each process on its own terms.
Sources and Further Reading
Automattic: Work With Us — general hiring overview; role variation and up-to-20-hour trial description.
Automattic: How We Hire Developers — separate coding challenge and developer trial descriptions.
Automattic: What to Expect During a Trial — different typical hours, stated pay and communication guidance.
Automattic: Show us your best work — authentic communication and AI-use disclosure expectations.


