Written Interview Assignment Tips 2026

The strongest written interview assignment is a bounded work sample, not an invitation to produce unlimited free consulting. First clarify the purpose, audience, format, time limit, scoring criteria, permitted tools, and confidentiality rules. Then turn the prompt into a small scoring checklist, use a format that resembles the target job, time-box the work, and make assumptions visible. Submit a clear recommendation or answer with trade-offs, and prepare to explain what you would revise with more time.

Key takeaways

• Treat the assignment as a simulation of the job, not a contest to see how much unpaid work you will absorb.
• Ask about purpose, audience, format, deadline, time budget, evaluation criteria, permitted research or AI tools, and confidentiality before starting.
• Build a one-page checklist covering interpretation, audience awareness, reasoning, organization, recommendation, and error control.
• Use a decision-led structure: answer first, evidence and assumptions next, risks or alternatives after that, and next steps last.
• Set a stopping point and state what you prioritized if the requested scope cannot fit the reasonable time available.
• Use AI only within the employer’s rules, protect confidential information, and be ready to explain every substantive choice.

A written interview assignment is a take-home work sample, timed writing exercise, editing task, case response, memo, or other professional document used to observe how you interpret a problem, communicate, make decisions, and produce a job-relevant result. The U.S. Office of Personnel Management describes work samples as tasks that mirror job activities and measure competencies expected at entry through observable work or outcomes. (U.S. Office of Personnel Management)

What employers want from a written assignment in 2026

Do not assume the best submission is the longest, most decorative, or most heavily researched. A useful work sample gives the reviewer a practical view of how you would operate: identify the decision, select relevant evidence, prioritize, make a recommendation, acknowledge uncertainty, and explain what you would validate next.

Start by asking what activity the prompt is simulating. A marketing brief may test audience judgment and prioritization. An operations exercise may test process diagnosis and trade-offs. A product case may test how you connect user needs to outcomes. An editing task may test whether you can preserve meaning while improving clarity. A technical explanation may test implementation choices, testing, and communication. The point is not to guess a hidden answer; it is to demonstrate the competencies the role actually needs.

The assessment should resemble the writing produced on the job. OPM guidance on assessment strategy identifies writing assessments as a way to measure concise, organized communication and says work-sample writing tests should reflect job-relevant writing. (U.S. Office of Personnel Management, USA Hire) As a candidate, use that principle in reverse: identify the likely workplace output and make your submission look usable by its intended reader.

• Clarity: Can a busy reader find the answer without decoding jargon?
• Role relevance: Does the work resemble the decisions and outputs the position requires?
• Reasoning: Can the reviewer follow how evidence led to your conclusion?
• Judgment: Do you distinguish facts, estimates, assumptions, risks, and open questions?
• Audience awareness: Does the tone and format fit the reader rather than a generic school essay?
• Completeness: Have you answered every requested part without silently expanding the scope?

Clarify the brief before doing the work

Before researching or drafting, turn the prompt into a four-part brief: deliverable, audience, decision, and constraints. The deliverable is what you must submit. The audience is who will read or use it. The decision is what that reader should decide, approve, understand, or do. Constraints include length, deadline, time budget, sources, formatting, access, collaboration, spell-check, confidentiality, and permitted tools.

Also ask why the exercise exists and whether it will be discussed in a follow-up interview. That question helps you prepare the right evidence. If the assignment tests editing, expect to explain why you changed tone or structure. If it tests analysis, prepare to discuss assumptions and alternative interpretations. Work-sample guidance emphasizes job relevance, appropriate administration, and trained evaluation; a follow-up conversation gives the employer another way to examine your judgment rather than treating the document as self-explanatory. (U.S. Office of Personnel Management)

Send a concise clarification message before investing serious time:

“Thanks for sending the assignment. Before I begin, could you confirm the expected time budget, required format and length, evaluation criteria, permitted research or tools, confidentiality restrictions, and whether AI assistance is allowed? I will state any remaining assumptions in the submission.”

If the employer does not answer, record your assumptions near the beginning or in a short assumptions section. For example: “I assume the goal is to improve qualified sign-ups rather than total traffic, and that the team can run one experiment during the first month.” This distinguishes your working model from a company fact.

Pay particular attention to scope. If the exercise could require many hours, ask whether a smaller representative sample is acceptable and state the amount of time you can reasonably spend. A useful boundary is: “I can complete a focused version in approximately X hours. If trade-offs are necessary, should I prioritize analysis, recommendations, or presentation?” That is a professional scope question, not a refusal to participate.

Check whether the task involves confidential, proprietary, personal, or live company information. Ask whether the case is hypothetical, whether the employer may use the submission, and whether any material may be shared with external tools. You should not paste restricted information into a public or external AI service without explicit permission.

Use a four-part system to build the submission

1. Map requirements to competencies

Copy the prompt into a working document and turn every instruction into a checklist item. Next to each item, write the likely competency: prioritization, audience judgment, analysis, editing accuracy, technical reasoning, stakeholder communication, or another role-specific capability. This makes omissions visible before the prose becomes polished.

2. Set assumptions and outline the answer

Write the decision question in one sentence. Then list the information you have, the information you lack, and the assumptions bridging that gap. Choose a small number of criteria before comparing options—for example, customer impact, feasibility, risk, and time to learn. Use criteria that follow from the prompt and role, not a framework added merely to look sophisticated.

A practical outline for a memo, email, briefing note, or case response is: recommendation, objective, evidence or analysis, options and trade-offs, implementation or next steps, assumptions, limitations, and validation questions. Lead with the answer because reviewers often need to assess the recommendation quickly. For an editing task, show the revised copy first and explain the material choices afterward. For a technical task, put the result, method, tests, and known limitations in a sequence another practitioner can follow.

3. Time-box the work

Set the stopping point before you begin. For a flexible 60–90 minute assignment, one possible planning model is 10% prompt and job-description analysis, 60% drafting, 20% revision against the requirements, and 10% proofreading and packaging. This is a planning example, not a universal rule: give more time to analysis when the task is data-heavy and more time to revision when precision or editing is the point.

1. Reserve the final review block before opening research tabs.
2. Create a rough answer early so you can test whether the recommendation survives contact with the details.
3. Stop research when another source is unlikely to change the decision or add material evidence.
4. Revise against the prompt and role requirements, not against an imagined standard of perfection.
5. Use the final block for file naming, permissions, links, formatting, and an opening-page check.
6. If the scope cannot fit the stated time, document what you prioritized and what you left out.

This protects you from turning a short assessment into open-ended unpaid consulting. A long assignment is not automatically improper, and some roles genuinely require substantial analysis. The useful test is whether the requested work is clearly explained, job-related, reasonably bounded, and representative of the skill being assessed. If a supposedly simple exercise requires extensive original research or a deliverable that could be used directly by the employer, pause and ask for scope clarification rather than silently adding hours.

4. Attach a concise decision memo

End with a short handoff note, even if the assignment already has an executive summary. Include the objective, final recommendation, three key assumptions, rejected alternatives, limitations, and what you would do with another day. This gives the reviewer a fast evaluation path and gives you a structured script for the debrief.

Make the final document easy to evaluate

Professional writing is not only about correct sentences. Review whether the document helps the intended reader act. Use descriptive headings, short paragraphs, meaningful bullets, and tables only when they make a comparison easier. Put definitions next to unfamiliar terms. If you include a figure, explain its source, date, definition, and limitation. If the prompt provides data, show the calculation path instead of presenting a bare conclusion.

Your final quality check should cover both language and judgment:

• Accuracy: Are facts, calculations, names, dates, links, and citations correct?
• Instruction-following: Did you meet the requested format, length, deadline, and file requirements?
• Audience: Would the intended reader understand the recommendation without extra context?
• Logic: Does the evidence support the conclusion, or have you skipped a necessary step?
• Scope: Have you answered the prompt without adding unrelated research or decorative analysis?
• Accessibility: Are headings, contrast, links, and document structure usable for the reader?
• Consistency: Do terms, numbers, recommendations, and assumptions remain consistent throughout?
• Actionability: Is it clear what should happen next and how success would be assessed?

Authenticity, originality, and AI use

Do not reduce the AI question to whether an employer can detect it. The relevant questions are what the instructions permit, what you actually used, and whether you can own every substantive decision. Policies differ by employer and exercise. If the instructions allow AI for grammar but not drafting, keep those uses separate. If they prohibit AI, do not use it for any covered stage.

• Read the instructions before using AI for brainstorming, research, grammar, drafting, or editing.
• Ask for written clarification if the policy is ambiguous rather than treating silence as permission.
• Never paste confidential, proprietary, personal, or restricted information into an external tool without explicit permission.
• Keep a brief record of substantive assistance, including what you asked a tool to do.
• Verify every factual, numerical, analytical, and technical output before using it.
• Disclose AI use when requested and follow the employer’s required disclosure or certification format.
• Make sure the finished work is genuinely yours and that you can explain its reasoning in a follow-up conversation.

A tool may improve wording while still leaving you responsible for the argument. Your own contribution should remain clear in the assumptions, prioritization, calculations, recommendation, and trade-offs. A polished submission that you cannot explain creates a credibility problem even when the sentences appear flawless.

Role-specific evidence without overbuilding

Use evidence that answers the assigned question. Do not add statistics merely to make the document look researched. Label the source, date, definition, and limitation when a figure matters. If outside research is permitted, use only what is relevant and keep a source list that another person could inspect.