Job search
Unclear Take-Home Interview Instructions? Build a Delivery Brief Before You Start
A complete fictional delivery brief, unsent clarification request, reply change log, and no-response branch separate confirmed requirements from assumptions.
A take-home invitation says to build a small tool, spend a few hours, and return it by Friday. That leaves several decisions unresolved: what the tool must do, which resources you may use, what “Friday” means, and how the reviewer receives your work. Start by turning those gaps into a delivery brief you can confirm.
LandOffer publishes this guide and offers job-search tools. The examples below are original editorial fiction, not an employer’s assessment or a completed candidate submission. Public sources were checked on October 21, 2026. Use the employer’s actual instructions and answers for your own assignment; this framework does not reveal its private scoring criteria.

If you are balancing this assignment with other applications, keep those commitments visible alongside recent roles on LandOffer.
Separate delivery requirements from guesses about scoring
Use the brief to record the requested result and the agreed delivery route. It cannot establish whether an interviewer privately values a particular framework, architecture, or visual style. Label an item “required” only when the instructions or a subsequent answer support that label. Keep your proposed implementation choices separate.
Public recruiting documentation shows why this distinction matters. Ashby’s setup documentation separates candidate-facing assignment instructions from reviewer-only notes. The candidate instructions can specify the scenario, submission format, expected effort, and resources. This describes a recruiting product’s configuration, not the private rubric of your prospective employer.
Write down the source of each requirement: invitation, attached specification, submission page, or dated reply. If two sources disagree, retain both versions and ask which controls. Do not quietly select the instruction that makes your preferred solution easier. Confirm a deadline change explicitly rather than inferring one from a newer-looking link.
Build the brief before building the solution
Here is a completed initial brief for fictional candidate Sasha and fictional employer Harbor Finch, role HF-62. The original invented instruction is: “Using the supplied sample requests, build a small command-line summary tool. Include run instructions and an example output. Spend about three hours; return it Friday.” No real assessment data or invitation is involved.
| Brief field | Sasha’s initial record | Status and consequence |
|---|---|---|
| Required result | Command-line summary tool, run instructions, example output | Explicit in the fictional instruction; no web interface required |
| Input | Supplied synthetic request file | File is named requests.csv; headers, malformed-row handling, and timezone interpretation need confirmation |
| Output | Example summary produced by the tool | Exact grouping and required fields unknown; propose totals by request category for confirmation |
| Optional work | Charts, deployment, database, polished website | Candidate ideas only; excluded from the initial plan, not employer-approved “nice-to-haves” |
| Resources | No permission statement supplied | Documentation, libraries, AI tools, collaboration, and code reuse require clarification |
| Effort | About three hours | Ask whether this includes setup, tests, packaging, and explanation; no assumption of unlimited polishing |
| Calendar deadline | Friday | Date, clock time, and named timezone unknown; not a usable deadline yet |
| Delivery | Return the work | Email attachment, private repository, portal, accepted format, and receipt mechanism unknown |
| Review | Not described | Ask whether there is a walkthrough, its duration, and what to prepare |
This completed record makes the unresolved decisions visible before Sasha commits implementation time. Completeness means every important field has a source or an explicit unknown, not that Sasha has guessed an answer for everything.
The grouping proposal is a question to the employer. It is not a sample solution to a proprietary test, a claim that category totals will earn points, or a reason to invent extra requirements. If the supplied input contains confidential material, the brief should also record its handling restrictions before any external tool or public repository is considered.
Keep effort time separate from calendar time
A preparation allowance and a deadline answer different questions. GitLab’s technical interview guide provides one documented example: for some roles, it describes up to an hour reviewing a self-contained merge request, a link provided at least 72 hours before the call, asynchronous review completed at least 24 hours beforehand, and a subsequent 90-minute discussion. These timings describe GitLab’s published process for some roles; verify the instructions for your own role.
For Sasha’s fictional case, the stipulated reply in the next section sets a three-hour total effort cap and a deadline of Friday, October 30, 2026, at 5 p.m. America/New_York. That instant is 2 p.m. America/Los_Angeles. The brief is confirmed Thursday, October 29, at noon Los Angeles time: 26 elapsed hours remain, not 26 hours of expected labor.
Sasha’s proposed effort allocation is 20 minutes checking inputs and setup, 85 implementing the required behavior, 35 checking examples and edge cases, 25 writing run instructions, and 15 packaging and reviewing delivery details. The total is 180 minutes. These are planning allocations, not hidden grading weights, promised performance, or proof that an unfamiliar environment can be configured within 20 minutes.
An original local Python check calculated the zone conversion, 26-hour interval, and 180-minute total. It also checked that the initial brief is blocked on missing essential fields and that a later reply leaves one resource permission unresolved. This was an offline check of declared fictional records, not a run of the interview task, an employer portal, or an assessment timer.
If setup consumes its allocation, log the obstacle and reassess the remaining scope. Ask for guidance rather than silently turning three hours into a weekend. A request for an alternative exercise or a different schedule is a request until the employer agrees. GitLab’s guide explicitly discusses considering alternatives; that does not establish another employer’s policy.

Send one consolidated clarification request
Group the questions that affect your ability to start, finish, and deliver. Quote only the short portion needed to identify an ambiguity; do not forward confidential instructions into unrelated channels. Use the established recruiter or coordinator thread rather than guessing an engineer’s address.
The following complete message is an unsent fictional draft, stored only as an editorial example:
Subject: HF-62 take-home: delivery scope and deadline confirmation
Hi Morgan,
Thank you for sending the command-line summary exercise. Before I begin, could you confirm the delivery brief below?
I understand the required submission to be the tool, run instructions, and one example output using the supplied requests.csv. Would totals by request category meet the intended summary scope? Please confirm the expected columns and how to treat malformed rows and timestamp timezones.
Does the approximately three-hour allowance include setup, checking, documentation, and packaging? Which resources are permitted: public documentation, third-party libraries, previously written code, collaboration, or AI assistance? I will not assume that permission for one covers the others.
Could you specify Friday’s date, time, and timezone, and confirm whether to use an attachment, repository, or submission portal? Please also let me know the expected file format and how I can verify receipt. Is there a later walkthrough, and what should I prepare for it?
I plan to omit charts, deployment, and a web interface unless they are requested. If this interpretation misses an essential deliverable, please correct it before I start.
Best, Sasha
The message offers a bounded interpretation while leaving the employer room to correct it. It does not ask for interview answers, confidential reviewer notes, or a guarantee that a particular implementation will pass. No email was sent, no Gmail draft was created, and no real recruiter responded.
Save the answer and record what actually changed
For this worked example only, stipulate a fictional reply, not an observed employer response: “Category totals are sufficient. The file has category and count columns; timestamps are irrelevant. Reject malformed rows with a clear error. Three hours includes all work. Public documentation and the standard library are allowed; no collaboration or reused project code. We will confirm AI permission separately. Submit a ZIP through the original portal by October 30 at 5 p.m. New York time. Retain its confirmation screen; contact me in this thread if it errors. Expect a 30-minute walkthrough next week; scheduling will follow.”
Sasha preserves the initial brief and records version 2 rather than overwriting the unanswered questions without history:
| Change | Version 2 decision | Remaining boundary |
|---|---|---|
| Summary and input | Category totals; category/count columns; malformed rows produce an error | No invented timestamp conversion or chart requirement |
| Effort | Three hours covers all work | Candidate’s allocation stays within 180 minutes; no extension implied |
| Resources | Public docs and standard library permitted; collaboration and reused project code excluded | AI permission still unknown; do not use it pending confirmation |
| Deadline | October 30, 5 p.m. America/New_York / 2 p.m. Los Angeles | Written instant retained; no automatically extended cutoff |
| Delivery | ZIP through the original portal; preserve confirmation screen | No portal opened or receipt observed in this example |
| Review | Thirty-minute walkthrough next week | Date, meeting link, and attendees still unconfirmed |
The remaining AI question does not become permission because other resource questions received answers. Sasha can plan an approach using only the expressly allowed resources, without treating an optional unresolved tool as necessary. If the assignment cannot be completed without a resource whose use is unclear, pause that dependency and ask again.
Save the dated reply beside version 2 and list each changed field in the work log. A reviewer should be able to distinguish an employer-confirmed requirement from Sasha’s own implementation decision. The walkthrough’s unscheduled date does not change the submission deadline.
Decide what to do if there is no reply
In this alternative fictional branch, stipulate that Sasha sent one clarification request and received no reply. This invented event is separate from the article’s actual unsent example: no message was sent during production. Start from version 1, not the fictional confirmed version 2. At Sasha’s chosen checkpoint, Thursday October 29 at noon Los Angeles time, the deadline’s time and zone, output scope, resource permissions, and delivery route remain unknown. The completed decision is to hold implementation dependent on those answers, retain the request record, and prepare a follow-up through the established channel if proceeding with the application.
Do not import the other branch’s October 30 deadline into this branch. “Friday” alone still does not establish that instant. A personal checkpoint helps Sasha decide when to seek guidance; it does not create an employer extension, stop an assessment timer, or preserve candidacy automatically.
Work that is safe to do without interpreting the task can stay narrow: list the supplied filenames locally, record questions, and check personal availability. Avoid publishing a repository, uploading employer material to an AI service, or building a production feature to compensate for missing instructions. If the proposed effort is unreasonable, discuss a smaller scope or alternative rather than treating excessive unpaid work as mandatory.
Deliver once, then prepare to explain your decisions
When the real brief is confirmed, check the requested files, run instructions, permitted dependencies, and sharing route against it. Record what you actually ran and any known limitations. A planned test, an uploaded file, a final submission, and a receipt are separate states.
Ashby’s submission guide illustrates why route details matter: its self-submission flow allows a candidate to submit once, while employer-side replacement and link-reset controls are separate; a reset removes already provided answers and files. This product-specific behavior should prompt verification of your own portal, not experimentation with a live assessment.
This fictional record stops before Sasha implements or delivers the tool. There is no ZIP, submission timestamp, receipt, or interview result. For an actual completed assignment, preserve the permitted delivery confirmation and prepare to explain requirements, choices, checks, and limitations without claiming unstated features. Keep other commitments organized with LandOffer’s recent job listings while waiting for the employer’s next step.
Sources and Further Reading
- GitLab: Technical Interviews — role-specific preparation, timing, discussion, and alternative-assignment context.
- Ashby: Setting Up Take-Home Activities — candidate instructions and separate reviewer notes.
- Ashby: Send and Review Take-Home Assignments — submission routes and employer-side replacement controls.


