Why take-homes exist
The take-home assignment has gained ground in 2026 as the whiteboard challenge has lost it. The shift is partly demographic — companies wanting to test asynchronous work because remote and hybrid teams operate that way — and partly diagnostic — take-homes reveal how the candidate structures their thinking on paper, which is closer to actual day-to-day UX work than whiteboarding.
The interviewer is assessing four things. How the candidate scopes ambiguity into a tractable problem. How they structure their thinking so a reviewer can follow it. What decisions they made under time pressure and how they explain them. Whether the deliverable is honest about its limits or fabricates confidence.
Scope without over-investing
The single most common take-home failure is over-investment. Candidates spend 30 or 40 hours on briefs the company expected 6 hours of work for. Hiring managers can usually spot the discrepancy within the first 30 seconds of reviewing the deliverable, and they treat the over-investment as a signal of poor judgement or desperation rather than enthusiasm.
The operational rule: honour the time the brief states. If the brief says 4 to 6 hours, finish at 6 hours regardless of whether you feel "done". The deliverable should reflect what a senior candidate would produce in that time, which is a thoughtful framing, two or three considered decisions, and an honest list of things you'd want to validate or extend if you had longer.
Structuring the deliverable
Five sections that work consistently
- Problem framing. One paragraph restating the problem as you've interpreted it. Name the assumptions you're proceeding on.
- Approach. What you decided to do in the time you had, and what you explicitly cut.
- Key decisions. Two or three decisions, each with alternatives considered and trade-offs accepted.
- Outputs. The sketches, flows or wireframes themselves. Low fidelity is fine — sometimes preferable.
- What I'd do with more time. The validations you'd run, the alternatives you'd test, the depth you couldn't reach.
Reviewers can read this structure in 10 minutes. The candidate's judgement is visible at every step.
AI use, honestly
The 2026 expectation: candidates who used AI on a take-home should say so. The disclosure isn't optional in serious processes; hiring managers increasingly assume AI use and treat the absence of disclosure as either naive or evasive.
Strong AI disclosure looks like: "I used Claude to generate initial competitor analysis from a list of 12 products; I cross-validated 4 of the 12 manually and corrected three inaccuracies before incorporating the analysis." Specific, honest, evidence of judgement layered on top.
Weak AI disclosure looks like: "I used AI tools throughout, as you'd expect." Vague, defensive, doesn't show the candidate's judgement layer. The broader cluster view is in AI for UX designers.
Format and length
Most UX take-homes are delivered as a deck (Figma, Keynote, Gamma) or a written document (Notion, Google Doc, PDF). Either works. The format choice matters less than the structure.
Length: 6 to 12 pages or 8 to 16 slides for a 4-to-6-hour take-home. Longer rarely gets fully read. Hiring managers review take-homes in 10 to 20 minutes on average; the deliverable should be designed for that window. Candidates who submit 40-page take-home decks tend to lose this round.
The presentation follow-up
Most take-homes are followed by a 45 to 60 minute presentation interview where the candidate walks the hiring manager (and sometimes a panel) through the work. The presentation usually has three parts: candidate walks through the deliverable (15–20 minutes), interviewer asks questions about specific decisions (20–30 minutes), candidate questions (5–10 minutes).
The presentation matters at least as much as the artefact. Candidates who can defend their take-home decisions confidently — including the decisions they're not fully satisfied with — convert significantly better than candidates who present a polished take-home but lose composure under questions. Strong candidates often say "I'm not fully sure about this decision because" — this signals judgement, not weakness.
Defending the work
Interviewers will challenge specific decisions. The framework for handling challenge: acknowledge the challenge specifically ("you're asking about why I chose X over Y"), state the assumption you were proceeding on ("I assumed Z, which informed the choice"), engage with the alternative ("if Z is wrong, you're right that Y would be the stronger choice"), and either revise or hold ("I think Z is reasonable to assume in this brief, so I'd hold the choice", or "I think you've identified a stronger framing, and I'd revise").
The collapse-vs-defend pattern is the most diagnostic moment in the round. Candidates who collapse — "you're right, I shouldn't have done it that way" — usually lose. Candidates who defend without engagement — "no, X is definitely correct" — also lose. The middle path of engaged judgement is what converts.
Paid versus unpaid take-homes
Some companies pay for take-homes (£100 to £500 is the typical UK range; higher in the US). Most don't. The convention varies by company size and seniority of role.
For senior roles, it's reasonable to ask whether the take-home is paid before committing. The ask isn't a red flag and demonstrates judgement about time investment. For junior and mid roles, paid take-homes are rarer; the take-home is usually expected as part of the process.
Candidates running multiple processes simultaneously sometimes decline take-homes from companies that aren't their top choice. This is a legitimate scoping decision and doesn't usually damage the application — recruiters understand that take-homes are expensive and candidates have to choose. The full pipeline view is in interview preparation guide.
For the whiteboard alternative, see whiteboard challenge examples. For the presentation round specifically, see interview presentation guide. For interview question patterns, see UX interview questions. For portfolio-side preparation, see portfolio examples and case study examples.
Frequently asked questions
How long should a UX take-home assignment take?
Honour the time stated in the brief. Most UX take-homes specify 4 to 8 hours. Hiring managers can spot over-investment.
Should I disclose AI use in a UX take-home?
Yes. Declaring AI use is professional in 2026; pretending you didn't use it reads as naive.
Is it okay to ask for clarification on a take-home brief?
Yes. One or two specific questions before starting demonstrates judgement under ambiguity. Don't ask ten.