UIUXAnywhere

Remote UI/UX & product design jobs, worldwide.

Guides

Figma and the other tools remote design jobs ask for

By the UIUXAnywhere team · Published November 8, 2026

Figma is the standard; almost everything else is a niche

On 8 November 2026, UIUXAnywhere listed 312 remote UI/UX and product design roles. The design tools they named:

  • Figma: 52 roles
  • HTML/CSS: 13
  • Sketch and After Effects: 4 each
  • Adobe XD: 3
  • Photoshop, Illustrator, ProtoPie and Framer: 2 each
  • Storybook and Webflow: 1 each

The October hiring report, over 325 roles, showed the same picture: Figma in 74, every other tool in single digits or low teens.

Two conclusions follow. First, Figma is assumed. If you design interfaces professionally, you need to be fluent in it, not just familiar. Second, most listings do not name a tool at all, because they care more about what you do with it. That is what most of this guide is about.

What "knows Figma" means to an employer

Being able to draw screens in Figma is the minimum. Remote teams live in shared Figma files, so they look for people who work in them cleanly and in a way others can build on. In practice that means:

  • Auto layout everywhere it makes sense, so frames resize properly and engineers can read the spacing.
  • Components and variants, built so that one change updates every instance, with sensible properties instead of dozens of near-duplicates.
  • Variables and styles for colour, type and spacing, including light and dark modes, so the file matches the code's design tokens.
  • Organised files. Clear page structure, named layers, a cover page, and a place where final designs are separated from explorations.
  • Prototyping. Interactive flows good enough to test with users and to explain behaviour to engineers.
  • Dev Mode and hand-off. Annotating designs, marking sections ready for development, and checking that what engineers inspect is accurate.
  • Comments and branching. Giving and resolving feedback in the file, and working on a branch rather than over someone else's work.

If your files would confuse a colleague opening them for the first time, that is the skill to improve before any new tool.

The skills around the tool matter more

Look at what the 52 Figma roles asked for besides Figma:

  • design systems: 39
  • a portfolio: 37
  • prototyping: 35
  • accessibility: 23
  • user research: 20
  • motion: 16
  • HTML/CSS: 11

Design systems

Design systems came up in three quarters of the Figma roles. Employers want designers who can use an existing system well (and know when to break from it), contribute new components properly, and document them so engineers and other designers use them correctly. If you have worked on a system, show it in your portfolio: the component, its variants and states, and the usage guidance you wrote.

Prototyping and motion

Prototyping appeared in two thirds of Figma roles. Figma's own prototyping covers most needs. For complex interactions or micro-animations, tools such as ProtoPie or After Effects appear occasionally, and Framer for interactive, code-like prototypes. Learn them when a role you want asks for them, not before.

Accessibility

Almost half of the Figma roles mentioned accessibility. In Figma, that means checking colour contrast, designing visible focus states, specifying focus order and screen reader labels in your annotations, and making sure touch targets are large enough. Plugins can check contrast, but the decisions are yours.

Front-end literacy

HTML/CSS was the second most named "tool". You do not need to be a developer, but understanding how layouts, flexbox, responsive breakpoints and components work in code makes your designs easier to build, and makes conversations with engineers much faster. Storybook, which appeared once, is where many teams document coded components; knowing how to read it helps you check that design and code match.

What about Sketch and Adobe XD?

Sketch (4 roles) still has loyal teams, mostly on macOS, and its concepts (symbols, libraries) map closely to Figma's components, so switching either way is quick. Adobe XD (3 roles) is no longer actively developed by Adobe, so it is not worth learning for new work; if a listing names it, the team is likely to be migrating.

Photoshop and Illustrator (2 each) appear mostly in roles that mix product design with marketing or brand work. They are useful for image editing and illustration, but they are not interface design tools for most teams.

Research and collaboration tools

Listings rarely name them, but remote design work also runs on whiteboard tools (FigJam, Miro) for workshops, research repositories for interview notes and insights, and unmoderated testing tools for usability studies. You do not need all of them; you need to be comfortable running a remote workshop and a remote usability test with whatever the team uses.

A practical learning order

If you are building or refreshing your skills for remote roles, this order follows what the listings ask for:

  1. Figma fundamentals done properly: auto layout, components with variants, variables and styles. Rebuild a screen from an app you use daily until the file is clean enough to hand to an engineer.
  2. A small design system: buttons, inputs, cards and a few patterns, each with states, documented usage and accessibility notes.
  3. Prototyping: an interactive flow you can put in front of a user, with realistic content rather than placeholder text.
  4. Accessibility checks: contrast, focus order, labels and touch target sizes, written into your annotations.
  5. Basic HTML and CSS: enough to understand how your layouts will be built and to read what engineers send back.
  6. Specialist tools only when needed: motion or advanced prototyping tools when a role you want names them.

Each step should end in something you can show: a file, a short video, a page in your portfolio.

How to show your tool skills

  • In your portfolio, include one case study that shows the file behind the screens: components, variables, annotations for engineers. Many designers show only the final pixels.
  • In interviews, be ready to share your screen and walk through a real (sanitised) file. How you organise work is part of what is being assessed.
  • On your CV, list Figma with specifics ("built and maintained a 120-component library with variables for light and dark themes") rather than a bare tool name.

For how to structure the case studies themselves, see what to put in a remote product design portfolio. The roles below are open now and name Figma; each one shows where you can work from.

Open remote UI/UX roles that use Figma

  1. Senior Product Designer (Remote)SeekOut · Remote
  2. Head of DesignLedgy · Remote
  3. Lead Product DesignerFlying Bisons · Poland
  4. UI Designer - Casual Games (Freelance Remote)SOFTGAMES · Remote job
  5. Product DesignerCare Access · USA Remote

More guides