Hiring work-sample tasks: clarify the brief, deadline and criteria

Before starting a hiring work-sample task, confirm the deliverable, deadline and time zone, expected effort, stated criteria and permitted resources. Then record any assumptions you need and prepare to explain your choices. This helps you complete the assignment without expanding its scope through guesswork.

A sample you create on your own initiative belongs in your portfolio. An employer's assessment has specific instructions and conditions. Do not substitute one for the other without agreement, or present a personal exercise as work already completed for a client.

Understand the assignment

Automattic describes projects or tests simulating work for some roles, with hiring steps varying by position. This is an example of that employer's process, rather than a compulsory standard for other organizations.

Read the whole brief before opening files or producing an answer. Separate explicit instructions from your interpretation: which problem should you examine, who will read the response, and what final output is expected? “Analyze” might lead to a written recommendation, presentation or executable file; one word does not define a deliverable.

If instructions conflict, point out the passages to your contact and ask which version to follow. For a timed activity, check the starting rules before activating an attempt. Do not assume you can pause or restart.

Turn uncertainty into questions that affect execution

Oxford's careers service advises clarifying activities, duration and criteria when assessment-centre invitations lack information. Here we adapt that care to an individual assignment, without assuming the same assessment format.

Use this worksheet created by FoxApply to organize questions:

Item	What needs to be clear
Deliverable	Content, format, length and submission channel
Deadline	Full date, time and time zone; submission versus presentation
Effort	Expected duration or working limit, separate from the available calendar time
Criteria	What evaluation guidance was provided and what you should demonstrate
Resources	Permitted material, tools, references, AI and assistance from other people
Open issues	Contact for questions, missing data and how to record assumptions

Group the questions that affect your work and send what is necessary. You do not need to demand an internal scoring rubric: request deliverable guidance and criteria the team can share. If you need a participation arrangement, explain it to your contact and confirm the alternative before assuming it is available.

Turn a vague request into a bounded brief

Fictional scenario created by FoxApply; no real company, completed assessment or applicant outcome is represented. On November 4, 2026, someone receives: “Analyze the maintenance requests and present a recommendation by Friday”. Format, priority rules and working conditions are missing.

A possible manual message is:

Thank you for the brief. Should I deliver only a proposed order for handling the requests and its justification, or an execution plan as well? How much working time should I reserve? Could you confirm the submission time and time zone, criteria and permitted resources, including AI and external references? If priority data is missing, should I record a question or make an explicit assumption?

Suppose the contact clarifies the following conditions only within this simulation. Nothing has been submitted or assessed; the table illustrates notes after a fictional reply.

Field	Demonstration brief confirmed in the scenario
Input	Four fictional maintenance requests and a supplied priority rule based on stated impact
Deliverable	PDF of up to two pages with suggested order, reasons and open questions; no services performed
Expected effort	Ninety minutes of work; an invented condition of this scenario, not a market benchmark
Final deadline	November 6, 2026, at 17:00, UTC−3; reply through the assignment email
Stated criteria	Apply the supplied rule, explain exceptions and make limitations visible
Resources	Editor and calculator; supplied material only; no generative AI or outside assistance in this example
Presentation	A later explanation of up to five minutes, at a time still to be confirmed

Notice the difference: having two days until submission does not mean working for two full days. A later presentation without a confirmed time does not change the PDF deadline either.

Record assumptions without inventing missing data

While working, maintain three labels: received information, your decision and open issue. Readers can then distinguish the brief from your reasoning. An assumption must remain visibly hypothetical, rather than quietly turning into a fact.

In the fictional case, one request has no impact information. A possible note is: “Request C has no stated impact. I left its position pending because the rule depends on that data. The final order may change after confirmation”. This is one option in the scenario, rather than the correct response to every assessment. If instructions require an assumed value, identify the one you used and why.

Do not consult a prohibited person or tool to fill the gap. Ask if permission is unclear. When AI use is authorized, follow any disclosure instructions and check its output; permission to use a tool does not authorize exposing restricted information to it.

Decide what to do when a condition does not work

Situation	Possible next step
Format or deadline is ambiguous	Request confirmation and record what remains unresolved
Effort exceeds your availability	Explain the limitation and ask about another deadline or scope; wait for agreement
Access or a file fails	Report the problem through the confirmed channel without claiming completion or an approved extension
Scope changes after starting	Confirm the new output and its effect on deadline and effort

If you cannot participate under those conditions, communicate your decision clearly. Silence does not need to become consent, and a requested change is not already approved. For a remote presentation, a sound and connection rehearsal helps prepare the technical setup.

Review the submission and prepare your explanation

Compare each part of your file with the brief. Open the final version and check readability, boundaries, permissions and destination. Do not send internal documents from another job to enrich the answer. Avoid adding unrequested work simply to appear more comprehensive.

Prepare a short explanation: assigned objective, chosen approach, main decision, assumption and limitation. Distinguish what you completed from what you would do next. If asked for a revision, check the scope again.

After submitting, record the channel and the next step actually agreed. The application follow-up guide helps track the stage. To connect resume experience to a role, explore FoxApply for comparison support; the analysis does not complete, mark or approve this assessment. Sources accessed November 4, 2026.