Five recurring brief types
UX take-home assignments in 2026 cluster into five recurring brief types. Recognising the type within the first read lets the candidate map their preparation onto the brief efficiently and avoid the trap of treating every take-home as a full case study build.
The five types: product redesign of a specific flow, journey improvement with provided data, research synthesis of provided transcripts, feature prioritisation given a set of candidate features, and competitive analysis of a market segment. Each type tests something different about the candidate. The full pipeline view of where take-homes sit in the broader interview process is in interview preparation guide; the operational guide to scoping is in take-home assignment guide; this article covers the recurring brief types and the strong response patterns.
Product redesign brief
Brief. "Pick a flow within [our product or a public product]. Redesign it. We're looking for your approach, decisions, and reasoning. 6 hours. Submit as a written document or deck. Follow-up interview will ask you to walk through your work."
The most common take-home brief. The interviewer is testing the candidate's ability to identify the most important friction, propose a meaningful intervention, and articulate the trade-off accepted.
Strong response shape. Choose a flow with a clear, identifiable friction (not "the homepage" or "the whole product"). Frame the problem in one paragraph. Name two candidate interventions you considered. Choose one. Show the redesigned flow at low fidelity (sketches or wireframes are fine — high fidelity in 6 hours signals over-investment). Name the trade-off accepted. Close with "what I'd validate" and "what I'd do with more time".
Common mistakes. Redesigning the entire product. Showing only finished screens without process. Inventing user research that wasn't done. Skipping the trade-off section entirely.
Journey improvement brief
Brief. "Attached: analytics data and 6 user interview summaries from our checkout journey, where conversion has dropped 8% over the last quarter. Propose improvements. 8 hours."
A brief that provides data and asks the candidate to make sense of it. The interviewer is testing analytical thinking, prioritisation, and the discipline of working from evidence rather than instinct.
Strong response shape. Start with a written diagnosis: what does the data tell you? What does it not tell you? Where are you confident and where are you guessing? Identify two or three friction points evidence supports. Choose one to address in depth. Propose a specific intervention. Estimate the expected impact and name the confidence level. Close with what you'd test next and what data you'd want.
Common mistakes. Treating the data uncritically. Ignoring data that contradicts the intuitive answer. Proposing four or five interventions without prioritising. Skipping the confidence-level discussion.
Research synthesis brief
Brief. "Attached: 8 user interview transcripts from a study we ran last month. Synthesise the findings and recommend next steps for the team. 6 hours."
A brief common at companies with strong research culture. Tests synthesis capability, pattern recognition, and the ability to translate raw research into team-actionable recommendations.
Strong response shape. Read all transcripts before starting synthesis (cutting transcripts to save time produces weaker patterns). Identify three to five recurring themes with evidence quotes from at least two transcripts each. Translate each theme into a specific recommendation. Name what you're uncertain about and what additional research would be useful. Be honest about AI use if you used it for transcript synthesis.
Common mistakes. Themes that don't have transcript evidence. Recommendations that don't follow from the themes. Inflated synthesis ("80% of users said X" when 6 of 8 said something tangentially related). Hiding AI use in synthesis.
For the broader view of research methods that sits behind this brief type, see UX research methods and the user interviews guide. The AI-assisted UX research piece covers the honest disclosure pattern.
Feature prioritisation brief
Brief. "We have 12 candidate features for our roadmap (attached). Prioritise the top 4 for the next quarter. Show your reasoning. 4 hours."
A brief that tests strategic thinking and the ability to apply a prioritisation framework under constraint. Common at product-led companies.
Strong response shape. Choose a prioritisation framework explicitly (RICE, ICE, value-vs-effort, etc.) and justify the choice in one paragraph. Score each candidate feature against the framework. Surface the top 4. Walk through the reasoning, including the features you considered and rejected and why. Name the assumptions you're proceeding on. Close with what evidence would change your prioritisation.
Common mistakes. Not naming the framework. Scoring features without justification. Picking 4 obvious features without showing the trade-off against borderline ones. No discussion of the assumptions underlying scores.
Competitive analysis brief
Brief. "Analyse 3 competitor products in [our space]. What are they doing well, where are they weak, what can we learn? 5 hours."
A brief common in early-stage companies and consultancies. Tests external orientation, analytical capability, and the ability to translate competitive observation into useful direction.
Strong response shape. Choose three competitors that span the strategic space (not three similar ones). For each, identify two strengths and two weaknesses with evidence (screenshots, specific flows, named features). Surface two or three strategic takeaways that apply to the company you're interviewing with. Frame each takeaway as a hypothesis to test, not a recommendation to ship.
Common mistakes. Choosing three obvious competitors without strategic spread. Listing surface-level observations without strategic translation. Recommending the company copy competitor features rather than learn from competitor decisions.
Timeboxing pattern
How to spend the time
- Read and frame (60 min). Read the brief twice. Identify the brief type. Decide on the approach. Write the framing paragraph.
- Thinking and decisions (150 min). The core work. Whatever the brief calls for — analysis, synthesis, design exploration, prioritisation.
- Output (120 min). Produce the deliverable. Sketches, wireframes, document, deck. Time-box ruthlessly.
- Write-up (30 min). Reflection, "what I'd do with more time", brief notes on AI use, final read-through.
Adjust proportions for 4-hour or 8-hour briefs. The pattern works because it prevents the most common failure: spending 5 hours on output and 1 hour on framing, which usually produces polished work without thinking.
Presentation expectations
Most take-home briefs are followed by a 45 to 60 minute presentation where the candidate walks through the deliverable. The presentation matters as much as the artefact. Three patterns work:
Lead with the framing. Open with how you interpreted the brief and the assumptions you proceeded on. This catches misalignments early and lets the interviewer engage on framing rather than challenging it through your output.
Walk through one decision in depth. Rather than narrating every page of the deliverable, choose the most interesting or contested decision and spend 5 to 10 minutes on it. The depth signal compounds across the rest of the conversation.
Defend gracefully. Interviewers will challenge specific decisions. The pattern that works: acknowledge the challenge, restate the assumption you were proceeding on, engage with the alternative, either revise or hold with reasoning. The interview portfolio presentation piece covers this in detail.
The take-homes that converted in the hiring rounds I ran were almost always the ones where the candidate had explicit 'what I'd do with more time' sections longer than expected. The reflection signalled judgement about the time constraint and prevented the over-investment trap. Take-homes that arrived with no acknowledgement of the constraint often lost the round at the presentation stage when the candidate couldn't honestly defend their time budget.
Common mistakes
Five mistakes recur across weak take-home submissions. Each is identifiable by hiring managers and damages the application.
Over-investment. 30 to 40 hours on a 6-hour brief. The polish doesn't match the time budget and the over-investment signals desperation or poor judgement.
Fabricated user research. Inventing personas, interview quotes, or usability test findings that weren't actually conducted. Hiring managers spot this pattern instantly and treat it as a credibility failure.
Final output without process. Submitting only finished designs or recommendations without the framing, thinking, or trade-offs that produced them. The deliverable loses the dimension hiring managers care most about.
Hidden AI use. Pretending AI tools weren't used when they obviously were. In 2026, disclosed AI use is professional; hidden AI use is naive and increasingly identifiable.
Skipping the reflection. No "what I'd do with more time" section. No naming of the assumptions you proceeded on. No acknowledgement of what you couldn't validate. The reflection layer is where senior judgement is most visible; skipping it costs the round.
For the broader pipeline view, see interview preparation guide. For the take-home scoping operational guide, see take-home assignment guide. For the whiteboard alternative, see whiteboard challenge examples. For the presentation round that follows take-homes, see interview portfolio presentation and interview presentation guide. For portfolio-side preparation, see portfolio examples, junior examples or senior examples. For interview questions that often appear in the follow-up, see UX interview questions. For salary expectations and offer-stage preparation, see UX designer salary UK and salary negotiation guide. For broader career context, see how to get your first UX job.
Frequently asked questions
What kind of take-home assignments do UX companies actually give?
Five recurring brief types: product redesigns, journey improvements with data, research synthesis of transcripts, feature prioritisation, competitive analysis. 4 to 8 hour briefs most common.
How should I timebox a UX take-home assignment?
Honour the brief's time. Break into framing (20%), thinking (40%), output (30%), write-up (10%). The strongest take-homes have explicit 'what I'd do with more time' sections.
What are common mistakes in UX take-home assignments?
Over-investing, fabricating user research, presenting only final output without process, hiding AI use, skipping the reflection. Each damages the application.