How to Make Your Take-Home Assignment Stand Out

How to handle a take-home assignment, from reading the brief and asking questions to scoping, submitting with a clear write-up and preparing to present.

Your first interview went well, and HR emails you a brief: “Please analyse the attached sales data and propose ways to grow sales next quarter. Submit within 5 days.” You already have a full-time job, time is tight, and you are not sure how detailed they want it. A take-home assignment is a great opportunity, because you get to show how you actually work, not just talk about it in an interview.

What is a take-home assignment?

It is a task a company gives candidates to complete within a set time, then submit or present in the next round. It appears in many fields: developers build a small feature, data analysts analyse a dataset, marketers plan a campaign, designers create a mockup.

Assessors usually look beyond the final answer. They want to see whether you think in a logical order, make reasoned decisions and communicate your work clearly.

Step 1: Read the whole brief, then ask

Read the brief at least twice. Underline the deliverables, file format and any stated criteria. If something is unclear, ask on day one, for example:

• “Roughly how many hours should this take, so I scope it appropriately?”
• “If some data is missing, may I make my own assumptions?”
• “Should I submit slides, a document or code?”

Good questions show that you work professionally, which is exactly what assessors want to see.

Step 2: Scope it and plan your time

If the company says it should take about 3 to 4 hours, do not spend a whole week. Work far beyond scope can suggest you struggle to prioritise. Split your time like this:

1. Understand the brief and data: about one fifth of the time
2. Complete the core work the brief asks for
3. Review and write the explanation. Do not leave too little time for this

Step 3: Finish the core before polishing

Answer every part of the brief first, then add extras. A beautiful submission that misses parts usually scores lower than a plain one that is complete and correct.

Examples by role

• Developer: code that runs, a README explaining how to run it, and tests for the key parts
• Data analyst: how you cleaned the data, three main findings and practical recommendations
• Marketing: target audience, key message, channels, rough budget and metrics
• Designer: the user problem, your concept and the reasons behind key decisions

Step 4: Write an explanation

This is the part that makes work stand out most, and people often skip it. Write one short page:

• Summary: what you did and your main conclusion in three lines
• Assumptions: what you decided because the brief did not say
• What you chose not to do: and why, such as limited time
• With more time: what you would do next

Good work answers the brief. Outstanding work explains why it answered that way.

Step 5: Prepare to present

If there is a presentation round, tell it in order: the brief, your thinking, results and limitations. Prepare for tough questions such as “If this data were wrong, would your conclusion change?” Saying “I have not looked at that yet, let me check” is better than guessing.

Be careful

• Use AI transparently: if the company allows it, say which parts you used it for, and be able to explain every part yourself
• Do not copy others’ work: assessors can spot it and often probe deeply in the presentation
• Watch for unusually large tasks: if the brief looks like real work the company will use, such as a full marketing plan for a real product, politely ask about scope before you start
• Submit on time: if something comes up, tell them in advance and ask for an extension. Do not go silent and submit late

How to get started

1. Read the brief twice and send questions on day one
2. Plan your time according to the scope the company gave
3. Complete the core work, then add extras
4. Write a one-page explanation: summary, assumptions and next steps
5. Rehearse your presentation and answers with Interview Lab

If you work in tech, read Technical Interview Prep for Developers, and to reuse this work as a portfolio piece, read Preparing a Portfolio for Interviews.