UIUXAnywhere

Remote UI/UX & product design jobs, worldwide.

Guides

HTML and CSS for designers: how much code remote design jobs expect

By the UIUXAnywhere team · Published November 8, 2026

Do designers need to code?

Most product designers do not write production code, and most remote design listings do not require it. But knowing how interfaces are built is increasingly valuable, and some roles do require real front-end skills.

On 8 November 2026, HTML/CSS was the second most named tool in remote design listings on UIUXAnywhere, after Figma: 13 of the 312 roles named it. Among the 153 listings with a full description, 49 mentioned front-end work, JavaScript, React or code in some form. Some titles make code central: "Product Design Engineer", "Staff Design Engineer - Cloud Networking UX", "Web Designer", "Product & Web Designer" and "Senior Product Designer (Webflow)".

Three levels of code knowledge

Level 1: understanding (useful for every designer)

You can read and reason about how a design will be built:

  • the box model: content, padding, border, margin;
  • layout: flexbox and grid, and how they map to Figma's auto layout;
  • responsive design: fluid widths, breakpoints, and content that reflows;
  • units: pixels, rems and percentages, and why text sizes in rems respect users' settings;
  • semantic HTML: headings, lists, buttons vs links, form labels, and why they matter for accessibility;
  • states: hover, focus, active, disabled, loading, and that every one must be designed.

At this level you will design things that are easier to build, spot implementation problems in review, and have faster conversations with engineers.

Level 2: building (web designers, marketing and content sites)

You can build and maintain real pages:

  • write semantic, accessible HTML and well-structured CSS;
  • use CSS custom properties (variables) for design tokens;
  • build responsive layouts that hold up across devices;
  • work in a site builder such as Webflow or a CMS, which many web designer roles use.

Roles at this level include web designers, marketing designers and designers at smaller companies who own the website.

Level 3: design engineering (prototyping and component work)

You design and build in code:

  • build components in a front-end framework (usually React) with TypeScript;
  • prototype interactions and motion in code for realism;
  • contribute to or maintain a component library and its documentation (often in Storybook);
  • work on design tokens that flow from design tools into code.

Design engineers sit between design and front-end engineering. They are especially valued in design systems teams and in companies building complex, interactive products.

Why it helps in remote teams

In a remote team, much of the design-engineering conversation happens asynchronously, in comments and pull requests. Designers who understand code:

  • annotate designs with what engineers actually need (spacing tokens, breakpoints, states, focus behaviour);
  • review implemented work precisely, with fewer rounds of back-and-forth across time zones;
  • propose solutions that fit the existing component library instead of new one-offs;
  • earn engineers' trust quickly, which matters when you rarely meet in person.

What to learn first

A practical sequence for a designer with no code background:

  1. HTML basics: structure a simple page with headings, lists, links, images and a form, using the right elements.
  2. CSS basics: typography, colour, spacing, and the box model.
  3. Flexbox, then grid: rebuild a layout you designed in Figma.
  4. Responsive design: make that layout work from phone to wide desktop.
  5. CSS custom properties: express your design tokens as variables, with a light and dark theme.
  6. Accessibility checks: keyboard navigation and a screen reader on your own page.
  7. Optional, for design engineering: JavaScript basics, then React components with props and state.

Rebuild something you have designed. It is the fastest way to see how your design decisions turn into code, and where they cause trouble.

Free ways to practise

You do not need a course to start. Rebuild a screen you designed using only HTML and CSS in a browser-based editor; inspect real websites with your browser's developer tools to see how layouts are built; and try changing the CSS of a page live to understand what each property does. Browser developer tools are also a designer's best friend during design review: you can check spacing, colours and fonts of the built product directly, instead of guessing from screenshots.

How to show it

  • In your portfolio: a case study where code knowledge changed the outcome, such as a design adjusted to fit the component library, a coded prototype that tested an interaction, or a token system you set up.
  • Your portfolio site itself: if you built it by hand, say so. Make sure it is fast, responsive and accessible; reviewers who check will notice.
  • On your CV: be honest about your level. "Comfortable with HTML, CSS and Flexbox; build prototypes in React" is credible; "full-stack designer" invites questions you may not want.

A small example: tokens in CSS

Design tokens become CSS custom properties, and components use the tokens rather than raw values. A button defined this way follows the theme automatically:

:root {
  --color-accent: #3b5bdb;
  --color-on-accent: #ffffff;
  --radius-md: 8px;
  --space-2: 0.5rem;
  --space-4: 1rem;
}

@media (prefers-color-scheme: dark) {
  :root {
    --color-accent: #91a7ff;
    --color-on-accent: #10172a;
  }
}

.button {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  min-height: 44px;
  padding: 0 var(--space-4);
  border-radius: var(--radius-md);
  background: var(--color-accent);
  color: var(--color-on-accent);
}

.button:focus-visible {
  outline: 3px solid var(--color-accent);
  outline-offset: 2px;
}

Notice how the code mirrors what a designer specifies in Figma: tokens for colour, spacing and radius, a comfortable minimum height, a gap matching auto layout, and a visible focus state. When your Figma variables use the same names, handoff becomes much simpler.

Try changing one token, such as the accent colour, and watch every button update. That is exactly the benefit a design system brings at scale, and seeing it in a few lines of CSS makes it easier to explain to stakeholders why consistent naming between design and code matters.

Design engineering as a career

If you enjoy both sides, design engineering is a growing specialism. It suits people who care about interaction quality, motion and systems, and who like seeing designs work in a real browser. Roles are mostly senior and often sit in design systems or platform teams; see design systems roles.

The roles below are open now and name HTML/CSS. Each one shows where you can work from.

Open remote UI/UX roles that use HTML/CSS

  1. Product Designer, Docs & LearningTailscale · Remote (United States)
  2. Front-End Engineer, UX/UIBeyondTrust · Remote Canada
  3. Visual DesignerDatabento · Remote / San Francisco / New York / Salt Lake City
  4. Web DesignerCUNY Central Office · Remote
  5. Visual Designer IIAffirm · Remote Canada

More guides