How to Complete a Remote UX Design Challenge

The design challenge is often the stage where Nigerian designers drop out of the process for foreign remote roles. Sometimes the work is weak. More often, the candidate spends three days perfecting visuals the reviewer never asked for, or NEPA takes the light halfway through a live whiteboard session. This guide covers the common formats of the UX design challenge and gives you an hour-by-hour plan for a take-home task. It also includes a clarifying-questions email you can copy, a structure for your submission and presentation, and the checks a Nigeria-based candidate should make before spending a weekend on any task.

Quick answer

A remote UX design challenge is a practical task, done at home or live on a video call, that tests how you frame a problem and reach a defensible solution. To do well, confirm the scope and time limit, ask clarifying questions, state your assumptions, sketch several options before committing, explain trade-offs, and keep the final screens modest. Before you start, check that the role accepts applicants living in Nigeria.

What a remote UX design challenge is testing

A design challenge gives the hiring team a small, controlled sample of how you work. Your portfolio shows finished projects that teammates, clients and time helped shape. The challenge shows what you do on your own, with a vague brief and a deadline.

Reviewers are usually looking at these things:

• Problem framing: do you restate the problem, identify the users and define what success looks like before you draw anything?
• Reasoning: can you explain why you chose one option over another, and what you gave up?
• Handling unknowns: when you lacked information, did you ask, make a reasonable assumption, or quietly ignore the gap?
• Communication: could a product manager or engineer follow your submission without you there to explain it?
• Craft at a sensible level: clear hierarchy, readable type, accessible contrast and consistent components. This does not mean a full design system.

This matches what hiring managers say about portfolios. In a Nielsen Norman Group survey of 204 UX professionals who hire, respondents asked candidates to show the problem, their role and the constraints rather than just the finished product. One respondent wanted to know "what isn't in the design and why". A design challenge is that same test, done in a few hours.

The four common formats

Companies use different names for these tasks, so read the invitation closely. This table explains what each format involves and what decides how it goes.

Many processes combine two formats. A common pattern is a take-home task followed by a presentation call. For skills and interview preparation beyond the challenge, see the UI/UX designer career guide for Nigerians and the product designer career guide.

Before you start: five checks that save wasted weekends

1. Confirm the role accepts applicants living in Nigeria

Check where you are allowed to live before you spend any time on the task. "Remote" in a job title does not mean "remote from anywhere". As of October 2026, Typeform's careers board on Greenhouse lists remote roles, and each one is tied to named countries such as the United Kingdom, Germany, Ireland, the Netherlands, Portugal, Spain or the United States. A Lagos-based candidate who completed a task for one of those roles would probably be rejected at the offer stage, whatever the quality of the work.

Some employers say plainly that location does not matter. As of October 2026, the Todoist careers page says its people "can work from anywhere in the world" and that it never places restrictions on locations. If the job ad says nothing about location, ask the recruiter before you start the task.

2. Find out whether the task is paid

Some companies pay for take-home work. As of October 2026, Doist's hiring FAQ lists a "paid task/assignment with feedback" as a hiring stage and says, "We pay you for completing it because we respect your time." Most companies do not pay. It is still reasonable to ask politely, and the answer tells you something about how the team values design time.

3. Get the time limit in writing

Ask "How many hours do you expect this to take?" if the brief does not say. The deadline (for example, "within five days") and the expected effort (for example, "about four hours") are two different things. Reviewers usually judge your work against the effort they expected, not against the full deadline window.

4. Check what they want back

The usual deliverables are a Figma file link, a PDF or slide deck, or a Loom-style video walkthrough. Some teams want a prototype and some explicitly do not. Sending the wrong format makes you look as if you didn't read the brief.

5. Read the brief for spec work

Be careful if the brief asks you to redesign the company's real product for a real, current business problem, with production-ready screens. That can drift into free consulting. Small critiques of the company's own app are normal. A full redesign of their checkout, delivered production-ready, is not. You can still do the task: scope it down, keep the output at wireframe or mid-fidelity, and say so in your write-up.

How to complete a take-home UX design challenge, step by step

The plan below assumes a brief that expects about six hours of work. Adjust the proportions for shorter or longer tasks, but keep the order.

Step 1: Read the brief twice and rewrite it in one sentence (20 minutes)

Write a problem statement in your own words: who the user is, what they are trying to do, what is getting in their way, and how the business will know things have improved. If you can't write that sentence, you have questions to ask.

Step 2: Send clarifying questions (10 minutes, then wait)

Send your questions as one tidy email rather than five separate messages. Some teams answer and some say "use your judgement". Both responses are useful.

Example (hypothetical): a clarifying-questions email.

Hi Tolu,

Thanks for sending the design exercise. Before I start, a few quick questions:

1. Is the primary user a first-time customer or a returning one? 2. Should I design for mobile, desktop or both? 3. Are there technical or brand constraints I should respect (for example, an existing design system)? 4. How many hours do you expect this to take, and would you like a Figma link, a PDF or both?

If any of these are meant to be open, I'll state my assumptions in the submission.

Best, Chiamaka

Step 3: Define users, assumptions and success measures (40 minutes)

Write down two or three assumptions you are making about the users and the context, and mark them clearly as assumptions. Choose one or two success measures that fit the brief, such as checkout completion rate, time to first booking, or fewer support tickets on a particular topic.

If you have time, talk briefly to two or three people who resemble the target user. Calling a cousin who shops online counts. Label it honestly as informal input, not research.

Step 4: Map the flow before drawing screens (45 minutes)

Sketch the current flow, if there is one, and your proposed flow as boxes and arrows. This is where most of your thinking becomes visible. It also stops you designing ten screens when the problem sits in two of them.

Step 5: Explore options at low fidelity (1 hour 15 minutes)

Produce at least two different approaches, not two colour variations of one approach. Rough sketches or grey boxes are fine. Then pick one and write two or three sentences on why it beat the others. Reviewers often read this decision record more closely than the final screens.

Step 6: Take the chosen option to mid or high fidelity (1 hour 45 minutes)

Design only the key screens and the states that matter, such as error, empty and loading states. Use an existing UI kit rather than building components from scratch, because you are rarely being tested on button-drawing. Run two quick checks:

• Usability: run through Jakob Nielsen's 10 usability heuristics (for example, visibility of system status, error prevention, and recognition rather than recall) and fix anything obvious.
• Accessibility: WCAG 2.2 at level AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. One sentence noting that you checked contrast tells the reviewer a lot.

Step 7: Write it up (1 hour)

Leave a full hour for the write-up. A strong solution with a confusing write-up often loses to a decent solution that is easy to follow.

Step 8: Review with fresh eyes and submit early (15 minutes)

Sleep on it if the deadline allows. Check that every link opens in an incognito window and that the Figma file's sharing settings allow viewing. Submit a few hours before the deadline, not in the final minutes.

How to structure your submission

Reviewers often look at a submission between meetings, so make it easy to skim. A structure that works for most briefs:

1. Summary (one slide or frame): the problem, your proposed solution in one sentence, and the main trade-off.
2. Problem and context: your rewritten problem statement, users and success measures.
3. Assumptions and open questions: clearly labelled.
4. Flow: the current flow and the proposed flow.
5. Options considered: the low-fidelity alternatives and why you chose one.
6. Final design: the key screens and the important states, with short annotations.
7. Trade-offs and what you left out: the "what isn't in the design and why" that hiring managers ask for.
8. Next steps: how you would test this with real users and which measures you would watch after launch.

In your Figma file, add a cover page that links to each section. Name your frames, and delete the scratch frames you don't want judged. A short screen recording of your own walkthrough, of five minutes or less, can help if the brief allows it.

For how this differs from a full portfolio piece, see our guide on what to include in a UX design case study.

How to present your design challenge

Many companies follow a take-home task with a presentation call. Assume you have about 20 to 30 minutes unless you are told otherwise, and plan to talk for only half of it. Leave the rest for questions.

A presentation outline that fits most slots:

• Two minutes: the problem in your words, and what you set out to achieve.
• Three minutes: users, assumptions and how you spent your limited time.
• Five minutes: the flow, the options you considered and why you chose one.
• Four minutes: walk through the final design.
• One minute: trade-offs, risks and how you would validate the design.

When panellists challenge a decision, treat it as a discussion, not an attack. "That's fair. With more time, I'd test X against Y, because..." is a stronger answer than defending a choice you aren't sure of. If they point out something you missed, say so and explain how you would handle it.

How to handle a live whiteboard challenge

A live whiteboard challenge compresses the same process into a single video call, usually in FigJam, Miro or the company's preferred tool. Thinking aloud matters more than drawing.

A useful running order:

1. Repeat the brief back and ask two or three clarifying questions.
2. State who the user is and what success means for this session.
3. Sketch the flow at box-and-arrow level.
4. Pick one part of the flow that matters most and sketch screens for it.
5. Close with trade-offs and what you would test.

Keep checking the clock out loud ("I have about 15 minutes left, so I'll focus on the payment step"). Reviewers like seeing a designer manage scope under pressure. Before the call, open the whiteboard tool, sign in and draw a few test shapes, because fumbling with an unfamiliar tool eats time. For camera, microphone and lighting, see the guide to preparing for a video interview with an international employer.

Nigeria-specific planning for remote design challenges

Time zones for live sessions

Nigeria stays on West Africa Time (UTC+1) all year. From 1 November 2026, US Eastern Time is six hours behind Lagos, so a 10am New York slot is 4pm in Lagos. US Pacific is nine hours behind in winter, so a 9am San Francisco slot is 6pm in Lagos. London is one hour behind Lagos in winter. When a recruiter sends a scheduling link, check the time it shows in WAT, and choose slots when your power and network are usually most stable.

Power and internet backup

Figma and most whiteboard tools run in the browser or depend on a live connection. For a timed take-home task or a live session:

• Charge your laptop, inverter or power bank fully the night before, and have a generator or solar plan if the grid is unreliable where you live.
• Keep two internet options ready, such as your main provider plus a MiFi or a phone hotspot on a different network.
• If you lose the connection during a live session, rejoin quickly and send a short message in the chat. Interviewers who work with distributed teams understand dropped calls. What they want to see is that you had a backup.
• For take-home tasks, export a PDF of your work at checkpoints so that an outage near the deadline doesn't leave you with nothing to send.

Tools and costs

You don't need to pay for software to complete most challenges. As of October 2026, Figma's Starter plan is free and includes unlimited drafts and access to UI kits and templates. The Professional plan is listed at $16 a month for a Full seat, which is about ₦21,800 at ₦1,362 to $1 (CBN rate, 23 October 2026). Use the free plan unless the brief specifically needs a paid feature. Check Figma's pricing page for the latest details.

Spotting design-test scams

A real design challenge never requires you to pay for anything. Be suspicious if a "recruiter" asks you to buy a software licence, pay for a "test platform", or move the conversation to Telegram before you have seen a proper job ad on the company's own careers page. Also be careful with tasks that ask for complete, production-ready assets for a business you can't find online. For the full set of warning signs, read how to spot remote job scams in Nigeria.

Example (hypothetical): a take-home brief and how to scope it

The brief: "Our grocery delivery app has a high drop-off at checkout on mobile. Redesign the checkout to improve completion. Please spend no more than six hours."

A weak approach: Redesign the whole app, including home, search, product pages and checkout, in high fidelity with a new colour palette, and submit 40 screens with no explanation.

A stronger approach:

The stronger submission might also note one trade-off. For example, a one-page checkout reduces taps but can overwhelm small screens, so you would A/B test it against a stepped flow and watch completion and payment errors. That single paragraph shows more seniority than any number of extra screens.

Common mistakes in UX design challenges

• Skipping the problem and jumping to screens. Reviewers cannot see your thinking if your submission begins on screen one.
• Over-polishing. A task scoped for four hours that clearly took four days can count against you, because it suggests you can't manage scope.
• Hiding assumptions. If you assumed something, say so. Unstated assumptions look like gaps.
• Inventing research. Don't present a conversation with two friends as "user interviews showed that 80% of users...". Label informal input honestly.
• Only one option. Showing alternatives you rejected proves you considered more than your first idea.
• Ignoring accessibility and edge cases. Payment failures, empty states, slow networks and contrast all matter, and mentioning them costs little time.
• Broken links. A private Figma file is an instant setback. Test every link while logged out.
• Missing the presentation slot. Double-check the time zone conversion. Getting it wrong ends the process.

For general advice on timed tests in other disciplines, see how to complete a remote technical assessment.

Frequently asked questions

How long should a take-home UX design challenge take?

As long as the company says it should, and no more. If the brief doesn't state an expected effort, ask the recruiter. Reviewers generally judge your work against the hours they had in mind, so a modest, well-reasoned submission within that budget usually compares well with an overworked one.

Should I do an unpaid UX design challenge?

Usually yes, if the task is reasonably scoped and the role accepts applicants living in Nigeria. Unpaid challenges are common in design hiring. Be cautious when the task asks for production-ready work on the company's real product, and keep that kind of work at wireframe level. Some employers, such as Doist as of October 2026, pay candidates for their task.

What do hiring managers look for in a UX design challenge?

They mainly look for your process: how you frame the problem, the assumptions you make, the options you consider, and how clearly you explain trade-offs. Visual craft matters, but at a sensible level. NN/g's survey of hiring professionals found they want to see the problem, the constraints and what was left out, not just finished screens.

Can I use a UI kit or template in a design challenge?

Yes, unless the brief forbids it. Using an existing UI kit frees time for the thinking reviewers actually assess. Say in your write-up which kit you used, so that nobody thinks you are passing off the components as your own work.

Can I use AI tools for a UX design challenge?

Only if the brief allows it or you have asked. Some teams accept AI help for things like placeholder copy, while others want unaided work. Whatever you use, say so in your submission, because being found out later damages trust far more than the time you saved.

What happens if my power or internet fails during a live whiteboard challenge?

Rejoin as quickly as you can on your backup connection, then briefly tell the interviewer what happened. Many interviewers who work with distributed teams will give you a few extra minutes. Prepare a second internet option and a charged power source before the call so that an outage stays short.

Do Nigerian candidates get different design challenges from candidates in other countries?

Generally no. A company runs the same exercise for every candidate for a given role. What changes for Nigeria-based candidates is the planning around the task: checking location eligibility, converting session times to WAT, and preparing backup power and internet.

Should I follow up if I don't hear back after submitting?

Yes. After about a week, or after the date the recruiter gave you, send one short, polite email asking about the timeline. If you are rejected, asking for brief feedback on your submission is reasonable, though not every company will reply.

Key takeaways

• A UX design challenge tests your reasoning and scoping more than your visual polish.
• Before starting, confirm that the role accepts applicants living in Nigeria, the expected hours, the deliverable format and whether the task is paid.
• Follow a fixed order: rewrite the problem, ask questions, state assumptions, map the flow, explore options, then finalise a few key screens.
• Spend real time on the write-up, and include trade-offs and what you left out.
• For live sessions, convert times to WAT and have backup power and internet ready.
• A genuine design challenge never asks you to pay for anything.

Next steps

When your next challenge arrives, keep this plan open and adapt the time budget to the brief. To find roles that accept applicants living in Nigeria, browse remote design and tech listings on WorkRemote, where each listing shows where applicants may live. After a search, you can turn on the free email alert for new matching jobs. To prepare for the interview rounds around the challenge, read the UI/UX designer interview questions and answers. If you would like one-on-one interview prep from the WorkRemote team, it is part of Premium membership, which also includes an interview invitation within your first week (an interview invite, not a job offer).

Sources

• UX Design Portfolios: Hiring Managers' Advice, Nielsen Norman Group
• 10 Usability Heuristics for User Interface Design, Nielsen Norman Group
• Understanding SC 1.4.3: Contrast (Minimum), W3C WCAG 2.2
• Figma pricing, Figma
• Hiring: Frequently asked questions, Doist handbook
• Careers, Todoist
• Typeform jobs board, Greenhouse
• CBN exchange rates, Central Bank of Nigeria