Before starting a take-home interview assignment, clarify the objective, scope, expected time and permitted tools. You should understand what to submit and how the employer intends to use it. A short clarification can prevent hours of work on the wrong problem.
This checklist is practical preparation, not a claim that every employer must use a particular assessment process. Follow the instructions you receive, protect confidential information and raise concerns before investing substantial effort.
1. What skill is the assignment intended to show?
Ask which capability the employer wants to assess: reasoning, writing, coding, analysis or another task. A clear objective helps you allocate effort. If the brief already explains it, reflect that understanding rather than asking a question answered on the first page.
Hypothetical wording: “Am I right that the main focus is how I structure the analysis, rather than a polished dashboard?” Do not assume presentation quality matters more than correctness, or that extra features will compensate for missing the requested task.
2. What exactly is in scope?
Confirm the required output, audience, assumptions and any explicit exclusions. Identify ambiguous phrases such as complete strategy or production-ready. Ask which parts can be simplified for the exercise.
A bounded task is easier to complete and discuss. If you cannot obtain clarification, state your working scope in the submission and explain why you chose it. Avoid silently expanding the assignment until it becomes an unpaid full project; extra work may not answer the employer’s actual question.
3. How much time is expected?
Ask for the expected effort and submission deadline, and clarify the time zone if relevant. These are separate points: a week-long deadline does not necessarily mean a week of work is expected.
If the stated effort does not fit the requested scope, explain the mismatch and ask which component to prioritise. You can also discuss a practical extension when needed. Do not claim you completed an extensive task in an unrealistically short time to appear more efficient; be truthful if asked about your process.
4. Which tools and assistance are allowed?
Check the rules for internet research, libraries, templates, AI tools and help from other people. Do not infer permission from the fact that the exercise is done at home. Ask how sources or assistance should be disclosed.
Use only material you are entitled to use. If a tool is permitted, you remain responsible for checking the output and explaining your decisions. Avoid submitting code, text or calculations you cannot understand simply because a tool produced a plausible-looking result.
5. What data and materials should I use?
Confirm whether the employer provides data, expects public sources or wants a fictional example. Ask about handling any supplied confidential material and follow the instructions. Do not use a current or former employer’s private information to make the submission more realistic.
If you create fictional data, label it clearly and explain that it demonstrates a method rather than a market finding. If source access fails, report the limitation instead of inventing figures. Keep references sufficient for the reviewer to understand where factual inputs came from.
6. How will the work be reviewed and used?
Ask what happens after submission and whether there will be a discussion. Clarify any concern about the work resembling a live commercial project, including intended use and applicable ownership terms. Do not assume a general answer settles a specific contractual issue.
You can request a narrower or fictional task if appropriate. Keep the conversation factual: “Could you confirm whether this is an assessment example or work intended for operational use?” Decide whether the arrangement is acceptable before proceeding, rather than relying on unstated expectations.
7. What format and explanation should accompany it?
Confirm file type, naming, submission channel and whether a short rationale is expected. Include the assumptions, what you completed, how you checked it and any unresolved limitations. Make the main answer easy to find.
Test that the file opens and that links work without granting unintended access. Do not submit a folder of unexplained drafts. If something is incomplete, identify it accurately; do not label the whole assignment finished when a required component is missing.
A concise clarification message
Hypothetical wording: “Thank you for the brief. Before I begin, could you confirm the expected effort, whether AI or external libraries are permitted, and whether the review focuses on the reasoning or the final visual polish? I plan to submit the requested file with a short note on assumptions and checks.” Remove questions the instructions already answer.
Submission check
Read the brief again, check the requested output, verify calculations or code and label fictional inputs. Keep a copy of what you submitted and prepare to explain the decisions yourself.
Should I complete extra tasks to impress the employer?
Prioritise the requested work. Extra scope is useful only if it supports the assessment and fits the agreed effort.
Can I decline an assignment?
You can discuss concerns or decide not to continue. Consider the actual request and communicate your decision professionally.
For presenting the result, use the portfolio interview walkthrough.
