What a reviewer is actually checking
Someone who will work with you reads this, usually in fifteen minutes, often alongside a dozen others. What they are looking for is narrower than candidates assume:
| Checked | What it tells them |
|---|---|
| Does it run from the README | Whether you can hand work to another person |
| Does it do what was asked | Whether you follow a spec |
| Is it readable | What reviewing your pull requests will be like |
| Are there tests | Whether you think software is maintained, not just written |
| Did you handle the obvious failure cases | Whether you think past the happy path |
| Is the scope right | Judgement - and this is where people lose |
The over-building trap
Asked for a small API, candidates add authentication, Docker, a database migration framework, a front end and a CI pipeline. It feels like showing range. It reads as poor judgement, because in a real codebase that is the person who turns a two-day ticket into a two-week refactor.
- Build exactly what was asked, and build that well.
- Put your opinions in the README instead of in the code. "I would add rate limiting here, left out as it was not in scope" shows the same thinking at none of the cost.
- Respect the stated time budget. If it says four hours, a reviewer comparing yours against a four-hour submission should see a four-hour project.
- Do not add dependencies you do not need. Every one is a decision you may be asked to defend.
The README, which is half the grade
It is the first thing opened and sometimes the only thing read carefully. Keep it short and make it carry the things code cannot:
- How to run it, in commands that work on a clean machine.
- How to run the tests.
- What you chose and why, in two or three lines. Trade-offs, not a tour.
- What you deliberately left out, and what you would do with more time.
- Anything you know is weak. Naming it yourself reads as self-awareness; having it found reads as a gap.
When to decline
Take-homes are generally reasonable, and sometimes they are not:
- Reasonable: a few hours, clearly scoped, at a company you actually want.
- Negotiable: longer than it should be. Asking to scope it down, or offering a pair-programming session instead, is a normal professional request and is often granted.
- Decline: multiple days of unpaid work, or work that looks like a real feature on their actual product. The second is rare and worth recognising.
- Ask first: where it sits in the process. Doing six hours of work for a first-round screen is a different proposition from doing it as the final step.
Take-homes are most common at the entry level outside big tech, which is covered in entry level software engineer interview questions.
On using AI for a take-home
A take-home is submitted as your own work and should be your own work. Beyond the honesty point, there is a practical one: these are routinely followed by a call where someone asks why you made a particular choice, and code you did not reason through does not survive that conversation. If you use AI the way you would in any normal development work, be ready to explain every line as your own decision, because you are claiming it as one.
Where CoPilot Interview fits
Disclosure: we build an interview assistant, so treat this as a disclosed pitch. CoPilot Interview is for live rounds, including the follow-up call where you defend your take-home decisions, with a permanent free tier that needs no credit card. The assignment itself is yours.
Frequently asked questions
How long should you spend on a take-home assignment?
The stated budget, and no more. A reviewer comparing your submission against others sized to four hours will read a twenty-hour project as poor judgement rather than as dedication, so put the extra thinking in the README instead of the code.
What do reviewers look for in a take-home assignment?
Whether it runs from a clean checkout following your README, whether it does what was asked, whether it is readable, whether there are tests, and whether the scope is right. Scope judgement is where strong candidates most often lose.
Is it okay to decline a take-home assignment?
Yes, when it runs to multiple days of unpaid work or looks like a real feature on their product. For an assignment that is merely longer than it should be, asking to scope it down or offering a pair-programming session instead is a normal request that is often granted.
Can I use AI on a take-home assignment?
A take-home is submitted as your own work. Beyond the honesty question there is a practical one: these are usually followed by a call asking why you made particular choices, and code you did not reason through does not survive that conversation.
Walk into the round with a second pair of eyes
CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.
Try it free