# Beating the take-home without burning your weekend

> A good take-home is a small, realistic task with a clear brief. Here is how to stand out without sacrificing your Saturday.

_Category: Winning the application · Updated: 2026-10-15 · 2 min read_

A good take-home is a small, realistic task with a clear brief. Here is how to stand out without sacrificing your Saturday.

## Time-box it

Decide how long you will spend, three to five hours is plenty if the task is fair. Write that down and stop when you hit it. A focused submission beats an exhausted one.

## Do the boring things well

- A README that says how to run it, what you chose, and what you would improve.
- One or two tests, not a suite.
- Clear commits. Reviewers read the history.
- It runs on the first try. Untested submissions are the most common own-goal.

## Show your thinking

If the brief is ambiguous, state your assumptions and proceed. Say what you would ask the product owner. This is exactly the judgement a remote team needs; see [the remote interview](/guides/preparing-for-a-remote-technical-interview).

## Push back politely when it is too big

If the task is a week's work, ask whether a smaller scope is acceptable. Fair teams say yes; teams that do not are telling you something. Compare the ask against [the posting](/guides/how-to-read-a-job-listing-like-a-recruiter).

## Then let it go

You will not get it perfect, and you do not need to. Ship a clean, honest solution and move on.