How to Prepare for a Take-Home Assignment or Work Sample Test

In this chapter

A take-home or work sample is a slice of the job done out of sight: a small app, a memo, a lesson plan, a deck, a chart critique, a writing sample, a refactored function, a 48-hour case.

It matches the “work sample” round in a question bank. It is not a homework contest. They are trying to see whether you can finish, communicate, and choose, without a live audience.
Read the brief twice before you open a tool.

Circle the deliverable, the time they claim it should take, and any explicit constraints (stack, length, data you must use, what you must not do). If the brief is vague, ask one clarifying question early. Silence plus a clever misread is how people spend twelve hours on the wrong artifact.
If they will not say how long it should take, give yourself a budget anyway — often two to four focused hours for a “short” take-home, a defined evening for a longer one — and stop.

Unbounded unpaid work is a signal about the company. Treat it as data.

Work backwards from “done.” Done means the thing they asked for exists, runs, or reads, with a short note on what you would do next.

Incomplete brilliance loses to a simple complete. That is the same rule as a live technical round, with more temptation to keep polishing.
Write the cut in the first twenty minutes: must-have, nice, fantasy.

Fantasy goes in the “with more time” note, not in the repo. If you cannot finish the must-have in the budget, cut again. A working subset with a clear README is a professional artifact. A half-framework with no entry point is a diary.
Protect sleep and your current job.

A take-home that requires you to vanish for a weekend is either badly designed or a filter for people with spare life. You may still do it. Do it with a clock, not with guilt.

They cannot see you think unless you leave a trail.

A short README or cover note: what you understood the ask to be, what you optimized for, what you skipped and why, how to run or read it, known limitations. That note is often graded more honestly than the flourish in the middle.
Match the posting’s altitude.

A senior sample should show a decision (what you would not build). A junior sample should show care (tests, labels, a clean path through the work). Do not submit a platform for a “small function” brief. Do not submit a toy for a brief that asked for a plan a director could use.
Use their nouns.

If they asked for a briefing for a school board, do not deliver a startup pitch deck. If they asked for production-minded code, a notebook with no error path is a miss even if the math is pretty.

Follow the rules they wrote.

If they ban libraries, do not sneak them in. If they allow AI, use it the way you would on the job — and say so in one line if the brief asks. If they are silent, assume they care whether the thinking is yours. A sample you cannot explain in the debrief is a trap you set for yourself.
Do not copy a public solution and change variable names.

Take-homes get searched. Do not have a friend “just look at” the whole thing unless the brief allows collaboration. If you pair, name it.
Cite data and quotes.

A case built on invented statistics will die in the follow-up. A memo that distinguishes fact, assumption, and recommendation will survive.

Submit on time, in the format they named, with files they can open.

Then prepare a five-minute walkthrough: the ask, the cut, the one trade-off, what you would do next. Many processes add a live debrief. The take-home was the artifact. The debrief is whether you still own it.
When they criticize, do not defend every pixel.

Agree with what is true, say what you would change, keep what you still believe. The sample is a starting point, not a personality.
If you do not hear back, follow the after-interview rules later in this guide.

Do not send a second, larger version unasked. That reads as not hearing the brief.

You are done preparing when you can read a brief, name a time budget, list a must-have cut, and imagine the README in one sitting — before the clock starts.

When the assignment arrives, you execute that plan.
The next chapters are about the room itself: video, then panels.

A take-home can sit between those rounds. Do not let the sample eat the live hours. They are different tests.

Generate questions from that job description — free preview, $2 for the full kit. No account. Paste a job description.