Job search
Automattic Slack Interview: Confirm the Format and Manage the Written Conversation
Two fictional completed conversation and delivery records distinguish scheduled Slack discussion, advance questions, authentic voice and pending receipt.
Read your Automattic invitation for the exact format: a scheduled Slack conversation, advance questions, or another arrangement. Then prepare to explain your own experience in your own words and keep unfinished questions visible. “Slack interview” alone does not specify a deadline, message length or a universal process for every role.
This guide checks official Automattic sources on October 21, 2026. Automattic's writing guidance says candidates should not use AI tools to generate replies to its questions. The examples below are AI-authored, entirely fictional teaching exercises, not real employer prompts or candidate submissions; do not copy them into an interview. No Slack account, invitation or private conversation was accessed. LandOffer publishes this guide and offers job-search tools; you can browse recent technical roles while reviewing the instructions for your actual role.

Establish the format for your invited role
Automattic's current careers page says hiring steps can differ by role. Most roles start with a Slack interview, while some instead use a 30-to-60-minute video interview. Its Slack advice is to arrive early, take time with responses and bring questions. That supports preparing for written communication; it does not establish a fixed Slack duration or response-size limit.
There is also a documented role-specific asynchronous component. The official design hiring guide, published July 17, 2024, describes questions to answer asynchronously before the interview and sharing accessible work samples. It discusses text conversations and long-form writing. This is a design-team description, not evidence that every engineering or support invitation includes the same preparatory questions.
Use the invitation for your specific role and current round. Record whether participants will be present together, whether answers are due before the meeting, and whether a portfolio or other document is requested. If the invitation names a meeting time but says nothing about advance answers, do not infer an assignment from someone else's experience.
If two instructions differ, identify the exact conflict. For example, a calendar event may name a conversation time while a separate message supplies a deadline for advance material. Both can be valid. Ask which items belong before the conversation and which will be discussed during it, rather than treating the earlier deadline as a replacement meeting time.
Verify the hiring channel and keep your own voice
The official jobs page warns about impersonators and says hiring goes through Automattic's official careers page, with email messages from its @automattic.com domain. Trace a Slack invitation back to the verified recruiting exchange. A workspace name, familiar logo or display name should not independently establish who invited you.
Keep credentials and unrelated private work out of the conversation. If a new contact asks you to move to an unexpected service or supply sensitive information, verify the change through the recruiting channel you already know. This is a verification habit, not a claim that an unfamiliar invitation is necessarily fraudulent.
Automattic's Show us your best work guidance asks applicants to communicate authentically and says not to use ChatGPT or similar tools to generate replies to its questions. It separately asks people using AI tools to explain what they used, when, how and how they evaluated the output. The disclosure request is not blanket permission to generate interview answers.
Prepare by recalling facts you can explain: the problem, your responsibility, your decisions and what you actually observed. Keep any notes within the interview's instructions. Do not disguise generated text as your spontaneous response, invent a project to match an example, or paste confidential team discussions to obtain a polished answer.
Keep a scheduled written conversation responsive
For a scheduled Slack round, set aside the confirmed interval and use the specified time zone. Before the start, identify the intended workspace and channel through the verified invitation. This guide did not join a workspace or test any notification settings, so it cannot promise that a particular invitation or device will work.
During the conversation, answer the question that was actually asked. A useful response can begin with the relevant decision and then explain the evidence. If a question contains several parts, keep track of each part rather than sending a polished story that addresses only the easiest one. Let the interviewer redirect the discussion.
Avoid treating silence as a score. The other person may be reading, composing or handling the conversation differently. If you need time to organize a response, say so briefly. If a term is ambiguous, ask what it means in that question. There is no sourced universal rule here about how many sentences to send or how quickly every message must arrive.
A useful working log records the question, whether you addressed it and the follow-up still open. It should help you listen, not become a second transcript filled with private employer material. Where the interview restricts notes, follow that restriction. Do not use a hidden assistant to write live replies or turn the log into a covert recording workflow.
Worked synchronous conversation: separate an answer from an unfinished follow-up
Fictional candidate Nadiya has a stipulated 45-minute written conversation from 14:00 to 14:45 UTC. These times are invented for the exercise. She is discussing a fictional volunteer project in which she maintained a sign-up form; the example is not a disclosed Automattic interview question.
Her teaching prompt is: explain a decision you changed after a teammate raised a concern. The original illustrative answer is:
I initially proposed making every sign-up field required because incomplete records were difficult to sort. Our volunteer coordinator pointed out that some participants did not have a phone number they could share. I changed the proposal so email was required and phone was optional, then added a clear contact-preference choice. I updated the form and the coordinator reviewed the wording. We checked three invented entries to confirm that a missing phone number no longer blocked submission. I did not measure whether this increased participation, so I would describe it as removing an unnecessary form requirement, not improving conversion.
This is a complete editorial example of responsibility, feedback, changed action and a bounded result. It is not a statement about a real applicant's work. A reader should select a different, truthful experience and write it independently within the employer's rules.
Nadiya's completed conversation log distinguishes her answer from later questions:
| Fictional time | Conversation item | Status at the end of the interval |
|---|---|---|
| 14:06 UTC | Explain the original decision | Addressed in the opening of her answer |
| 14:12 UTC | Explain the teammate's concern | Addressed without claiming the concern was her own discovery |
| 14:21 UTC | Describe the resulting change | Addressed with her implementation and the coordinator's review separated |
| 14:34 UTC | Explain how she would test accessibility further | Acknowledged; detailed answer still unfinished |
| 14:42 UTC | Ask how the team reviews written decisions | Asked; interviewer's response still pending |
At the closing time, she does not label all five items complete. Her illustrative handoff says: “I have described the form change and our limited checks. My accessibility follow-up is unfinished, and my question about decision reviews is still open. Would you prefer a follow-up in this channel or to leave those for a later discussion?” It remains an unsent teaching statement, not an action performed here.
Her closing record distinguishes one answer completed, one substantive follow-up unfinished and one candidate question awaiting a response. It does not predict an interview outcome or prescribe that a real interviewer must accept additional material after the interval.

Plan asynchronous material using both deadline and effort
Advance questions require a delivery plan, not continuous availability until the deadline. Record the exact due date, time zone, requested destination, material and any effort limit. The days available and the time you expect to spend are different quantities. A short calendar window does not authorize unlimited effort, and a long window does not imply that someone is waiting for immediate replies throughout it.
Check what counts as delivery. The instruction might request a channel message, an attached document or a link; do not substitute one for another without agreement. If a link is requested, review the destination's access requirements using the employer's permitted method. Do not publish private work to make an inaccessible link easier to open.
Track draft readiness separately from delivery and acknowledgement. A finished document on your computer is not evidence that the hiring team received it. A post visible to you also should not be described as reviewed or accepted unless you actually have that confirmation. This guide did not send a message, upload a file or inspect a real receipt.
Worked asynchronous brief: a finished draft with delivery still pending
Fictional candidate Elian receives a stipulated request for two advance responses in an approved hiring channel by October 23, 2026, at 16:00 UTC. The example concerns a fictional internal documentation project, not a real Automattic prompt. The stipulated request arrives October 21 at 16:00 UTC, leaving 48 calendar hours. Elian plans 75 minutes of active work across two sessions; the invitation's actual effort limit, if any, would govern a real case.
| Item in Elian's completed brief | Recorded decision |
|---|---|
| Requested material | Two original responses; no portfolio attachment requested |
| Delivery deadline | October 23, 2026, 16:00 UTC |
| Planned active effort | 45 minutes drafting plus 30 minutes checking facts and coverage |
| First response | Drafted with personal responsibility and limits explicit |
| Second response | Drafted, but one supporting fact still needs verification |
| Delivery and receipt | Not sent; no visible delivery or hiring-team acknowledgement |
One complete illustrative draft, about a documentation handoff, reads:
I maintained the setup notes for our fictional community website. When another volunteer could not reproduce my instructions, I asked them to identify the first unclear step rather than sending a longer version of the whole document. We found that I had assumed a sample file already existed. I added that prerequisite, named the expected file and asked the volunteer to read the revised sequence. They confirmed the missing step was now explained. We did not repeat the full setup together, so I could not claim that the whole guide had been validated. My next check would be a fresh run by someone who had not seen my local environment.
The draft's completeness does not make it a submission. Elian's second response has an unresolved fact, and neither response has reached the stipulated channel. His status is draft package incomplete; delivery and receipt pending. He should verify the fact or accurately narrow the claim before sending anything in a real situation.
The executed original offline check for this article calculates that the two planned sessions total 75 minutes, keeps the UTC deadline unchanged and flags the unresolved response as blocking readiness. It uses synthetic records only. It does not connect to Slack, schedule a reminder or certify that a message would arrive on time.
Close with an accurate written handoff
Before a scheduled conversation ends, distinguish answers already given, follow-ups still unfinished and questions awaiting the interviewer. For asynchronous material, distinguish your local draft, the requested delivery action and any acknowledgement. Ask about unresolved format or timing through the verified hiring contact rather than filling gaps from third-party interview stories.
Carry forward only truthful claims you can explain in your own words. The goal is a clear written exchange within the requested process, not a script designed to imitate a successful candidate. As you find recent roles on LandOffer, check the role-specific format and organize truthful examples before the conversation begins.


