Remote UI/UX designer interview questions and answers

Remote UI/UX designer interviews, whether with an agency, a startup or a freelance client, focus on your portfolio, your process and your craft. Expect questions about how you go from brief to final screens, how you organise Figma files and design systems, usability and accessibility, and how you handle feedback and deadlines with people you've never met in person.

Agencies and freelance clients care a lot about communication and reliability. In-house teams add questions about working with developers and product managers.

Updated October 2026 by the WorkRemote careers team

On this page
  1. About the role and your experience
  2. Technical questions
  3. Behavioural questions
  4. Situational questions
  5. Remote work questions
  6. Remote interview tips
  7. FAQs

About the role and your experience

Openers that check you understand the job and have done the work.

  1. Walk me through your design process on a recent project.

    Why they ask

    They want to see a structured, flexible process, not a textbook list of stages.

    How to answer

    Use one real project. Go from the brief and questions you asked, to flows and wireframes, testing, visual design and handoff. Say where you adapted the process to the budget and deadline.

    Show a sample answer

    A clinic in Abuja wanted patients to book appointments online. I started by asking the front desk what calls they got most, then mapped the booking flow and wireframed it in a day. I tested the wireframes with four patients in the waiting room, which showed that people wanted to see the doctor's name before choosing a time. Then I designed the UI with a small component library and handed it to the developer with every state documented.

  2. What is the difference between UI and UX design?

    Why they ask

    A basic question, but a clear answer shows you understand both halves of the job.

    How to answer

    UX is how the product works and feels to use: flows, structure, content and usability. UI is the visual and interactive layer: layout, typography, colour, components and states. Say that they depend on each other.

    Show a sample answer

    UX is whether a user can book an appointment in three easy steps without getting lost. UI is how those steps look and respond: the buttons, the type, the colours, the date picker. A beautiful UI on a confusing flow still fails, and a good flow with poor UI feels untrustworthy.

  3. How do you design for users with slow internet and low-end phones?

    Why they ask

    Relevant for African and emerging-market products, and a sign of real-world experience that foreign clients value.

    How to answer

    Mention lightweight pages and images, offline and error states, saving progress, clear loading feedback, large tap targets and testing on a real low-end Android device.

    Show a sample answer

    I keep images small and avoid heavy animations, design clear loading and offline states, and save form progress so a dropped connection doesn't wipe everything. I test on a cheap Android phone on mobile data, because that's what many users in Nigeria have. Those habits also make products better for users anywhere.

Technical questions

What you know and how you'd do the work, often with a live task or test.

  1. How do you set up a Figma file and components for a new project?

    Why they ask

    Organised files save teams and clients time. This tests real Figma craft.

    How to answer

    Mention pages for different stages, foundations as variables or styles (colour, type, spacing), components with variants and properties, auto layout throughout, clear naming, and a cover page and changelog for handoff.

    Show a sample answer

    I set up pages for flows, wireframes, final UI and components. Colours, type and spacing go into variables and styles first, with light and dark modes if needed. Buttons, inputs and cards are components with variants for size and state, all built with auto layout so they resize properly. I name layers clearly so developers in Dev Mode can find everything.

  2. How do you build a type scale and spacing system?

    Why they ask

    Consistency in type and spacing separates professional UI from amateur work.

    How to answer

    Explain choosing a base size (often 16px for body text on web), a ratio or set of steps for headings, line heights for readability, and a spacing scale based on multiples of 4 or 8. Mention applying them consistently through styles or variables.

    Show a sample answer

    I start with a 16px body size and a line height around 1.5 for readability. Headings step up in a fixed scale, for example 20, 24, 32 and 40. Spacing uses multiples of 8 (8, 16, 24, 32), with 4 for tight spots. Everything is saved as styles or variables so I never type a random value.

  3. Name a few of Nielsen's usability heuristics and give an example of one being broken.

    Why they ask

    The heuristics are a shared vocabulary for discussing usability problems.

    How to answer

    Name two or three correctly (for example visibility of system status, error prevention, recognition rather than recall) and give a concrete example from an app.

    Show a sample answer

    Visibility of system status, error prevention and recognition rather than recall are three. A common break of the first is a payment that shows a spinner forever with no message, so people pay twice. For error prevention, a good example is asking the user to confirm the account name before a bank transfer goes through.

  4. When would you use a modal, and when would you avoid one?

    Why they ask

    Tests interaction design judgement on a common pattern that's often misused.

    How to answer

    Modals suit short, focused tasks or confirmations that need attention before continuing, like confirming deletion. Avoid them for long forms, content people need to compare with the page behind, or anything shown on load that interrupts users. On mobile, consider bottom sheets or full screens.

    Show a sample answer

    I'd use a modal to confirm deleting a saved card, because it's short and needs a decision. I'd avoid modals for a long checkout form or for popping up a newsletter sign-up the moment someone lands. On mobile, a bottom sheet is usually easier to use than a centred modal.

  5. How do you make sure your UI is accessible?

    Why they ask

    Accessibility is expected by serious clients, and required by law for many UK and EU products.

    How to answer

    Give specifics: WCAG 2.2 contrast of 4.5:1 for normal text and 3:1 for large text, visible focus states, labels on inputs, not relying on colour alone, and touch targets that meet platform guidance (Apple recommends at least 44 by 44 points, Material Design 48 by 48 dp; WCAG 2.2 AA sets a 24 by 24 CSS pixel minimum).

    Show a sample answer

    I check contrast with a plugin as I design and keep body text at 4.5 to 1 or better. Errors use text and an icon, not just red. Every input has a visible label, not only placeholder text, and tap targets follow Apple's 44-point and Material's 48-dp guidance. I also annotate focus order and headings for developers.

  6. How do you design for different screen sizes?

    Why they ask

    Responsive design is basic for web projects, and many clients' users are mostly on mobile.

    How to answer

    Explain designing mobile first for most consumer products, defining breakpoints, using grids and auto layout so components adapt, and showing developers how layouts change rather than designing every possible width.

    Show a sample answer

    For most consumer projects I start with mobile, since most users are on phones, then design tablet and desktop layouts at the main breakpoints. I use a 4-column grid on mobile and 12 on desktop, and build components with auto layout so they stretch properly. I document what changes at each breakpoint, like navigation collapsing into a menu.

  7. How do you test a design when the client has no budget for research?

    Why they ask

    Most freelance and agency projects have little research budget. They want practical methods.

    How to answer

    Mention quick tests with five or so people from the target audience, hallway or remote tests with a prototype, using analytics or support emails if they exist, and comparing with competitors. Be honest that it's lightweight.

    Show a sample answer

    I'll test a clickable prototype with five people who match the users, often over a 20-minute video call each, asking them to complete two or three tasks while thinking aloud. It takes a couple of days and catches the biggest problems. If the client has support emails or analytics, I read those first.

  8. How do you hand off designs to developers, including ones who don't use Figma much?

    Why they ask

    Many freelance projects go to WordPress, Webflow or junior developers. Clear handoff protects the final result.

    How to answer

    Mention a tidy file, Dev Mode or inspect access, exported assets, a short spec or Loom video covering interactions and states, and checking the build before launch.

    Show a sample answer

    I organise the final file with only approved screens, give the developer Dev Mode or view access, and export icons and images in the right formats. I record a short Loom explaining interactions and each state, and I review the staging site before launch with a list of fixes, not a vague "it looks off".

Behavioural questions

Past situations. Answer with a real example: what happened, what you did, what changed.

  1. Tell me about feedback that changed how you design.

    Why they ask

    Shows openness to critique and growth.

    How to answer

    Pick specific feedback, explain how you reacted, what you changed and the result.

    Show a sample answer

    A senior designer told me my screens looked busy because I used too many font sizes and random spacing. I counted, and one screen had seven text sizes. I built a proper type scale and spacing system, and my next client said the new designs felt calmer and more professional. I still check every file for stray values.

  2. Tell me about a project that didn't go well.

    Why they ask

    They want honesty and evidence that you learn from problems.

    How to answer

    Choose a real project, explain what went wrong (often scope, communication or assumptions), and what you do differently now.

    Show a sample answer

    An early freelance project with a US startup went three weeks over because we never agreed what "done" meant, and they kept adding screens. I lost money on it. Since then I write a one-page scope with the number of screens, revision rounds and timeline, and both sides agree before I start.

Situational questions

Hypotheticals about problems you'd meet in the job.

  1. A client insists on a change you think hurts the design, like a much bigger logo. How do you handle it?

    Why they ask

    Client management is half the job for agency and freelance designers.

    How to answer

    Find the concern behind the request, explain the trade-off simply, offer options (including their version), and respect that it's their product once they've heard you.

    Show a sample answer

    I'd ask what they're hoping the bigger logo will do; often they want the brand to feel more established. Then I'd show two options: their version, and one where the brand comes through with colour and a stronger header without pushing the booking button off screen. If they still prefer theirs, it's their product, and I'd make it look as good as possible.

  2. A client keeps asking for revisions beyond what you agreed. What do you do?

    Why they ask

    Scope creep is the most common freelance problem. They want to see professionalism, not resentment.

    How to answer

    Refer back to the written scope politely, separate small fixes from new requests, offer to quote the extra work, and keep the relationship positive.

    Show a sample answer

    I'd thank them for the feedback and point out that we've used the two revision rounds in our agreement. Small fixes I'll just do. For the new pages they want, I'd send a short quote and timeline. Most clients accept that when it's explained calmly and the scope was clear from the start.

  3. You have two client deadlines on the same day and one project is running late. How do you manage it?

    Why they ask

    Remote freelancers and agency designers juggle several projects. Reliability matters most.

    How to answer

    Explain prioritising by impact and agreements, telling the affected client early with a new date, and what you'd change in planning next time.

    Show a sample answer

    I'd tell the client whose project is late as soon as I know, not on the deadline, and give them a realistic new date and what they'll get today. Then I'd deliver the other project on time. Afterwards I'd add a buffer day to my estimates, because surprises always come.

Remote work questions

How you'll work from Nigeria with a team elsewhere: hours, power, internet, communication.

  1. How do you communicate with clients in different time zones?

    Why they ask

    Remote clients need to trust you're working and reachable without daily calls.

    How to answer

    Mention set update times, written summaries, Loom walkthroughs, agreed response times and keeping calls for decisions.

    Show a sample answer

    I agree a rhythm at the start, usually two short updates a week with a Loom video of progress. UK clients share my working hours, so we can talk live easily. For US clients, I schedule calls in my evening twice a week and reply to messages within a few hours during their working day.

  2. What is your remote working setup?

    Why they ask

    Clients and employers need confidence that calls and deadlines won't be disrupted.

    How to answer

    Be specific about your laptop, power backup, two internet sources and a quiet place for calls.

    Show a sample answer

    I work on a laptop with 16GB of RAM, which handles big Figma files. I have an inverter with batteries for outages, a fibre connection with a MiFi on another network as backup, and a quiet room with a headset for client calls.

Remote interview tips

Present, don't just share a link. Walk through one or two projects on screen share, telling the story from brief to result. Keep each to about 10 to 15 minutes unless they ask for more.

Have your Figma file ready to open. Interviewers often ask to see your components, auto layout and file structure. Clean up the file you'll show beforehand.

For freelance clients, the first call is the interview. Ask about their goals, users, deadline and budget, then summarise what you heard in writing. That summary often wins the job.

Agree take-home scope. For design tests, ask how long it should take and how it'll be judged; a few hours is reasonable, several days isn't.

Write both time zones. "3pm GMT / 4pm WAT" or "9am ET / 2pm WAT". Double-check around the March and October clock changes.

Questions people ask

What should a UI/UX portfolio include for interviews?

Three or four projects with the brief, your role, flows or wireframes, final UI, any testing and the result. Include at least one project with real constraints or a real client. Keep it easy to scan.

Do UI/UX interviews include a design test?

Often. It may be a short live exercise, such as improving a screen in an hour, or a take-home of a few hours. Agencies sometimes skip tests and judge your portfolio and a trial project instead.

What Figma questions are asked in interviews?

Expect questions about auto layout, components and variants, variables and styles, prototyping and how you organise files for handoff. Some interviewers ask you to share your screen and show a file.

How do freelance clients interview UI/UX designers?

Usually with a short video call about their project, a look at your portfolio and sometimes a small paid trial task. They're judging communication, reliability and whether your past work matches what they need.

Updated October 2026 by the WorkRemote careers team

Share or discuss this guide